【SelfHost License Question】Does it mean NO NEED further license even for commercial use? ( enterprise feature is not activated)

[samuel-gehealth]

I hope to make sure the commercial usage about Dokploy:

Portions of this software are licensed as follows:

All content that resides under a "/proprietary" directory of this repository, if that directory exists, is licensed under the license defined in "LICENSE_PROPRIETARY".
Content outside of the above mentioned directories or restrictions above is available under the "Apache License 2.0" license as defined below.

-- As You can see, Above text is copied from LICENSE.MD, It's not quite clear how to tell which function is under "/proprietary" directory ?

One common situation, when I install Doploy through the "curl -sSL https://dokploy.com/install.sh | sh" script. With No Enterprise Feature Opened, Does it mean it can be applied to Apache2.0 License for commercial usage?

Pls help to confirm whether a commercial license is required for this situation ? ( selfhost deploy + no enterprise feature opened + commercial usage).
Below is the self-host screenshot, which enterprise feature is locked.

[ashik4339]

Short answer: no additional license is needed for your scenario.

Here's why, based on how the repo is actually structured:

• The Apache 2.0 license covers everything in the repo except the /proprietary folder — concretely, that's apps/dokploy/components/proprietary/ (audit logs, SSO/SAML/OIDC/SCIM, custom RBAC roles, license-key handling, and the GitHub/Google sign-in components).
• The Dokploy Source Available License (DSAL) only restricts that specific folder — you can view/modify it for dev & testing freely, but using it in production requires a commercial agreement.
• If you self-host via the install script with no enterprise features activated, you're not running any code from /proprietary in a licensed way — you're just using the Apache 2.0-covered core. That's fully free for commercial use, no license or agreement required.
• You'd only need to talk to the Dokploy team if you actually want to turn on enterprise features (SSO, audit logs, custom roles, etc.) — at which point you need a license key from them anyway, which is a separate gate before that code even activates.

One caveat since this touches licensing: I'm going off the literal LICENSE.md / LICENSE_PROPRIETARY.md text and repo structure, not legal advice — if you need something binding for compliance/procurement purposes, worth a quick confirmation email to the Dokploy team, but functionally this is how the license is designed to work.

Source: LICENSE.md + LICENSE_PROPRIETARY.md (DSAL v1.0) text, and the actual repo tree showing what lives under apps/dokploy/components/proprietary/.