Notploy

Feature support matrix

Which capabilities exist in which Notploy edition.

Purpose — Give a single view of how capabilities differ across editions. Every edition shares the same deployment engine; the differences are in governance, delivery and support — not in how applications are built and run.

Editions

Notploy comes in four editions: Self-Hosted (OSS), Cloud, Enterprise Self-Hosted, and Enterprise Cloud. See Editions & scope for what each one is.

Matrix

CapabilitySelf-Hosted (OSS)CloudEnterprise Self-HostedEnterprise Cloud
Core deployments (apps, databases, Compose, domains, TLS, templates)✅✅✅✅
Remote servers / build servers✅✅✅✅
Docker Swarm cluster✅✅✅✅
Backups & restore✅✅✅✅
Scheduled jobs✅✅✅✅
Concurrent builds✅Managed✅Managed
Basic roles (Owner, Admin, Member)✅✅✅✅
Custom roles (granular permissions)❌Plan-dependent✅✅
SSO (OIDC / SAML)❌❌✅✅
SCIM provisioning❌❌✅✅
Application Authentication (forward auth)❌❌✅✅
Audit logs❌❌✅✅
Whitelabeling❌❌✅❌
Advanced monitoring dashboardBasic✅Basic✅
Managed control plane (uptime & updates)❌✅❌✅
SupportCommunityEmail & ChatPriorityPriority + SLA

Concurrent builds are included in every self-hosted edition, no license required. Whitelabeling is available on Enterprise Self-Hosted only, because the Cloud control plane is shared infrastructure.

Status vocabulary

Each capability in the docs also carries a status:

  • Available — implemented and verified today.
  • Experimental — implemented but incomplete or subject to change.
  • Planned — on the roadmap; not available.
  • Unsupported — out of scope or edition-dependent (as marked in the matrix).

On this page