Dokploy License Change to Apache 2.0 Plus Source-Available Enterprise on — what do I need to change?
Re-evaluate Dokploy adoption after its January 2026 licensing cleanup and source-available enterprise track changed the open-core risk profile.
Blockers
- Licensing cleanup placed all current features and the entire current codebase under Apache 2.0.
- Lock-in via vendor/dokploy
Who this is for
- cost-sensitive
- enterprise
- small-team
- compliance
Candidates
Adopt Dokploy standard edition under Apache 2.0
As of 2026-03-20, Dokploy states that all current features and the entire current codebase are now under the standard Apache License 2.0 after the 2026-01-21 licensing cleanup. The company also states it will not remove existing open-source features or move current open-source code into the paid track. Official docs say all instances run in the standard edition by default, so the licensing ambiguity around the prior adapted license is materially reduced. Dokploy did not expose a clearly verifiable current release number in the official pages reviewed here, so check official docs or releases for the exact version.
When to choose
Use this when you are cost-sensitive or a small team and your blocker was license ambiguity rather than missing enterprise controls. The decisive factor is that current functionality is now explicitly Apache 2.0, with a public commitment not to reclassify existing open-source features as paid.
Tradeoffs
The licensing position is much clearer than before and avoids immediate paid lock-in for current functionality. The tradeoff is that future advanced features for larger organizations may still land outside Apache 2.0 in proprietary directories.
Cautions
This is not a return to a fully open future roadmap. As of 2026-03-20, Dokploy says future complex features for larger organizations may be published as source-available components rather than Apache 2.0.
Adopt Dokploy Enterprise only if you need org-grade controls
As of 2026-03-20, Dokploy Enterprise is the paid track for features such as SSO, whitelabeling, custom roles, and audit logs. Dokploy describes these enterprise capabilities as source-available, but its January 21, 2026 policy says production use of that future paid functionality requires a paid license. Official pricing pages list Enterprise for both cloud and self-hosted deployments, but no public price is shown; buyers must contact sales. Enterprise also includes licensing mechanics that are not present in standard Apache-only use.
When to choose
Use this when you need compliance or enterprise constraints such as SSO, audit logs, or granular role control and are comfortable with commercial dependence. The decisive factor is whether those controls are hard requirements today, because they are outside the default standard edition path.
Tradeoffs
You get the administrative and compliance features that larger organizations usually need. The tradeoff is proprietary production licensing, opaque pricing, and tighter vendor dependence than the Apache 2.0 standard edition.
Cautions
Official docs say Enterprise licenses are validated daily against Dokploy servers using the server IP address, so self-hosted buyers should review this operational dependency before committing. Public pages reviewed here do not provide a fixed Enterprise price or a verifiable current release number.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Dokploy License Change to Apache 2.0 Plus Source-Available Enterprise on — what do I need to change?"