To: The Krea Management Team

From: The Undersigned Krea Subscribers, Creative Professionals, and Educators

To Whom It May Concern,

We are writing to you as dedicated members of the Krea community—many of whom have supported the platform since its earliest stages due to your groundbreaking real-time canvas.

The recent retirement of the Realtime tool has severely disrupted our professional and educational production environments. For many of us, this feature was not a hobby; it was the foundation of our daily workflows, client delivery timelines, and active curricula (including professional AI art classes). While we appreciate the future release of Krea 3 LoRAs, it does not currently serve as a substitute for the fluid, immediate creative iteration that Realtime provided.

We fully understand and respect the operational and financial hurdles your team faces:

1. High Compute Costs: Running a heavy model like flux.schnell in a low-latency environment is incredibly resource-intensive, especially with continuous canvas rendering.

2. Business Sustainability: Providing tens of thousands of real-time generations per month for a low subscription baseline is not a viable or sustainable long-term business model.

However, completely removing the feature leaves your core user base without a replacement and breaks the live workflows we paid upfront to use. Instead of retiring the model entirely, we respectfully propose the following compromises to balance your infrastructure costs with our professional needs:

1. Adjust the Credit/Generation Cost: Increase the credit weight of Realtime generation. Nobody needs 30,000 images a month. Charging a higher credit rate per generation (such as 3 credits, aligning with your pricing logic for tools like Krea.Turbo) would limit excessive resource drain while preserving utility. This would provide basic subscribers with roughly 55 high-value generations and premium subscribers with over 220 generations.

2. Eliminate the Automatic Refresh Feature: Remove the resource-heavy "spontaneous refresh" mechanism. Continuous rendering often overwrites high-quality results before a user can evaluate them. Replacing it strictly with a "Manual / On-Click" generation trigger would drastically slash your server load while improving user control.

3. Introduce Model-Tier Pricing Structure: Restructure your real-time ecosystem by charging varied rates based on compute intensity. It is completely reasonable to charge a premium for high-compute models (like Flux Realtime, HD Realtime or Real-time Video) while keeping legacy modes (CGI, Anime, etc.) at a lower tier.

4. Offer a Fair Transition Window and Restitution: If a sustainable model framework cannot be reached, Krea must issue formal announcements ahead of time and provide a straightforward path to pro-rata refunds for users whose annual or monthly workflows have been rendered non-functional.

We love Krea and want to see the platform thrive financially. We urge you to consider these community-led solutions so that we can continue to build our businesses and teach our classes using the tools we trust.

Sincerely,