✨ Self-service for Premium Features coming soon!

[Witoso]

Hey everyone,

We're thrilled to share some exciting news with you!

Over the past few months, we’ve been working on a brand-new, streamlined way to access Premium Features for CKEditor 5, and it's almost ready for you to explore.

Note

The open-source version of CKEditor 5 licensed under GPL remains unchanged. The following updates apply exclusively to CKEditor 5 Premium Features, which have always been part of our commercial offerings.

Introducing subscriptions for CKEditor Premium Features 🎉

Our goal is to make it easy for you to access Premium Features with just a few clicks. We've created various pricing plans based on different feature needs, so you can choose the option that’s right for you (or start a free trial), and begin using your new features in your editor immediately.

But wait, there’s more!

• Usage-based billing: Each of our commercial plans will include a specified number of editor loads. If you exceed the limit, you’ll be charged additional, but can always upgrade to a larger plan.
• No credit card trial: Not ready to commit? No worries! Our 14-day free trial will still be available, and you don't need a credit card to test out all of our Premium Features. Dive in and explore to your heart's content.
• Simplified integration: Thanks to a new customer portal (coming soon!), getting started will be even easier. Just grab your license key, plug it into the editor, and you’re set.

We're also updating our documentation to give you all the details, so stay tuned!

When can you expect these changes?

We plan to launch these updates by the end of the year, and are working hard to make them available as soon as possible.

Thanks for your support!

—The CKEditor Team

PS. We're sharing this message ahead of the official launch because some necessary changes to the editor core are being made to enable the ability to subscribe to CKEditor Premium Features. To stay transparent and avoid confusion, we want to explain the reason for these changes and their purpose.

We’re using this public repository to maintain a unified codebase for both the open-source and commercial versions of the editor. This ensures consistent quality, with both free and paid versions relying on the same core. These changes will not impact anyone using the self-hosted, open-source version of the editor. And rest assured, the GPL license remains unchanged.

[Witoso]

We're happy to announce that the release of the subscription plans for CKEditor Premium Features is now live with the 44.0.0 release! You can read more details in our release blog post.

You can now explore the new way to access Premium Features, start a free trial without a credit card, and check out our self-service plans.

We're also introducing a new Customer Portal, which will make managing your subscription even easier. From the portal, you can view your plan details, manage your billing information, and quickly access your license key to integrate Premium Features seamlessly.

Thank you for your support!

[spacelist-ca]

Are you providing documentation for migrating/switching from Enterprise to this new self-service premium? Besides support services, what are the limitations of it vs what current Enterprise users access?

[Witoso]

Hey, the best way forward is to contact support or talk with your account manager. The main difference is the usage-component, accompanied by the Cloud (CDN) distribution.

[spacelist-ca]

Right so assuming we are within the usage tiers, which we are, what's the difference other than the Pagination license needing to be added in? As far as the technical installation goes, do you have documentation that shows the difference of our current method and cdn method? Is there a migration doc for example? That'd be super helpful as we think self service would be significantly less cost than our current setup and give us access to more features. Thanks Steven

…

On Tue, Dec 3, 2024, 3:05 a.m. 'Witek Socha' via Accounts < ***@***.***> wrote: Hey, the best way forward is to contact support <https://ckeditor.com/contact/> or talk with your account manager. The main difference is the usage-component <https://ckeditor.com/docs/ckeditor5/latest/getting-started/licensing/usage-based-billing.html>, accompanied by the Cloud (CDN) distribution. — Reply to this email directly, view it on GitHub <#17317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHPYD543HY7IBTXBB7HWQL32DWF7TAVCNFSM6AAAAABQQXYN26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJUGIZTINZRGE> . You are receiving this because you commented.Message ID: ***@***.***>

[Witoso]

For details regarding the deal possibilities, I would recommend contacting the support. As for the technical details, this section in the documentation should help.

[spacelist-ca]

Thanks. And in terms of custom plugins that are developed to work with the npm version, using the CDN method shouldn't make a difference, right?

…

On Tue, Dec 3, 2024 at 8:40 AM 'Witek Socha' via Accounts < ***@***.***> wrote: For details regarding the deal possibilities, I would recommend contacting the support. As for the technical details, this section in the documentation <https://ckeditor.com/docs/ckeditor5/latest/updating/migrations/vanilla-js.html> should help. — Reply to this email directly, view it on GitHub <#17317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHPYD5ZDNY4X23BULFSW6VT2DXNHNAVCNFSM6AAAAABQQXYN26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJVGA3DAMZQGI> . You are receiving this because you commented.Message ID: ***@***.***>

-- Steven Jaffe CEO / Founder Spacelist 855-387-8771 ***@***.*** Spacelist.ca <https://www.spacelist.ca/>

[Reinmar]

Thanks. And in terms of custom plugins that are developed to work with the npm version, using the CDN method shouldn't make a difference, right?

Yes, custom plugins can be developed in a way that they work with CDN and npm distributions.

It's a bit different story depending whether you're an integrator (you integrate CKE into your app and need some custom plugins) or an author of a 3rd party addon that you want to publish and have people using it in all distribution channels.

For the latter, use our Package generator. It offers a development environment for 3rd party addon authors. This environment allows publishing the package in a "universally consumable way".

If you're integrator and you need to think about just one of the distribution channels (CDN or npm), you can just build your addon with that channel in mind. You have quite the same capabilities in both situations, but the code (mainly: import statements) differ slightly.

[spacelist-ca]

And there is detailed documentation for all of this?

…

On Fri, Jan 10, 2025, 5:42 a.m. 'Piotrek Koszuliński' via Accounts < ***@***.***> wrote: Thanks. And in terms of custom plugins that are developed to work with the npm version, using the CDN method shouldn't make a difference, right? Yes, custom plugins can be developed in a way that they work with CDN and npm distributions. It's a bit different story depending whether you're an integrator (you integrate CKE into your app and need some custom plugins) or an author of a 3rd party addon that you want to publish and have people using it in all distribution channels. For the latter, use our Package generator <https://ckeditor.com/docs/ckeditor5/latest/framework/develpment-tools/package-generator/using-package-generator.html>. It offers a development environment for 3rd party addon authors. This environment allows publishing the package in a "universally consumable way". If you're integrator and you need to think about just one of the distribution channels (CDN or npm), you can just build your addon with that channel in mind. You have quite the same capabilities in both situations, but the code (mainly: import statements) differ slightly. — Reply to this email directly, view it on GitHub <#17317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHPYD57TCT3NCCD4SHG7OIT2J7E4VAVCNFSM6AAAAABQQXYN26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBSG42DANJVGQ> . You are receiving this because you commented.Message ID: ***@***.***>