For the CKEditor 5 Forge components that only use the free / open‑source CKEditor 5 build and plugins:

1. Do you need a separate CKEditor license to use the basic features?
   No. When the component is built only with the CKEditor 5 open‑source (free) build and free plugins, you don’t need to purchase a separate CKEditor license just to use those basic features in OutSystems. This is similar to the TinyMCE component case, where the Forge component is explicitly designed for the free/open‑source editor and not for commercial (paid) licenses.Is it possible to use the paid version of TinyMCE through this component?

   In other words, as long as:

   • You are using the standard Forge CKEditor 5 component as-is, and
   • You are not plugging in CKEditor’s commercial add‑ons / SaaS services,

   then a separate commercial CKEditor license is typically not required.

2. Do you need a license/subscription to receive security updates and fixes?
   For applications that only use the basic (free) CKEditor 5 editor inside OutSystems:

   • Security fixes and feature updates for CKEditor 5 itself come from the CKEditor project and are available in the public releases of the free build.
   • When the Forge component maintainer updates the bundled CKEditor version (for bugfixes or security updates), you get those by simply updating the Forge component in your environment.
   • There is no additional license / subscription needed beyond:
     • Your existing OutSystems license, and
     • The component’s own (typically open-source) licensing.

   This is conceptually the same pattern as with other bundled JS libraries: you can extend or customize, but if you want to use commercial features of the vendor, that’s when you’d need a separate license (similar to the explanation given for Wijmo FlexGrid in Data Grid Web).[Data Grid Web] wijmo js licesen required in this case?

3. When would a separate CKEditor license be required?
   You’d typically need a separate license if you:

   • Use CKEditor’s commercial features or premium plugins not covered by the open-source license.
   • Integrate CKEditor Cloud services or other SaaS offerings that are not part of the free distribution.
   • Build your own CKEditor package under a commercial contract with CKSource and then integrate that paid build into OutSystems (similar to how you would directly integrate a paid TinyMCE build instead of using the free Forge wrapper).Is it possible to use the paid version of TinyMCE through this component?

Summary:

• Using the Forge CKEditor 5 component with only its basic/free features does not, by itself, require a separate CKEditor license.
• Security updates for those free features come via the standard CKEditor 5 releases, and you receive them when the Forge component is updated and you deploy the new version.
• A separate license is only needed if you intentionally use CKEditor’s commercial offerings or a paid build.