Editions: Community, Enterprise and Cloud¶
Didacta is one product with three editions. The code is the same; what changes is who operates it and which cross-cutting capabilities are active.
| Edition | Who it is for | What it includes |
|---|---|---|
| Community | Teams that deploy and operate the platform themselves. | The full source code and every module, with no user limit. Free, self-hosted, under the Sustainable Use License. |
| Enterprise | Organisations that need an SLA, custom integrations and a certified partner. | Community + cross-cutting core capabilities (SAML/OIDC SSO, SCIM, white-label…), unlocked with a signed license. |
| Cloud | Anyone who wants to get started in minutes, with no infrastructure. | Hosting managed by VA360 LABS with hands-off upgrades. Coming soon. |
Pricing and sales: didacta.io.
Where the line is drawn¶
The line separating Community from Enterprise is deliberately simple:
- Modules are always Community. No module — courses, certificates, gamification, Fundae, virtual classroom… — is ever locked behind a license. What a self-hoster installs is the complete product.
- The only paid features are cross-cutting core capabilities: a closed list of platform features (identity federation, provisioning, white-label…) aimed at large organisations. The full list is in Enterprise capabilities.
What gating looks like in the product¶
In Didacta nothing is hidden.
- Every Enterprise screen always exists in the menu and loads with its title and description; if there is no license, the panel shows an upsell notice instead of the content.
- In the API, Enterprise endpoints respond with HTTP 402 (
Payment Required) when the capability is not active. - A Community installation works in full without a license: there are no trial periods and no degraded behaviour.
How Enterprise is activated¶
With a JWT license signed by VA360 LABS, pasted into Administration → License or pinned in the DIDACTA_LICENSE_KEY variable. The details are in Enterprise license.