Start from a repo
Point Orchard at a repository. It finds each app inside, works out the framework, the commands and the port, and gives the app an HTTPS URL. The dashboard is simple enough for your first deploy, or you can ask an AI agent to do the whole thing.
| Feature | Orchard | Coolify | Dokploy | Kubero | Dokku | CapRover |
|---|---|---|---|---|---|---|
| Web dashboard | Yes | Yes | Yes | Yes | Paid add-on | Yes |
| License | AGPL-3.0 | Apache-2.0 | Apache-2.0, some parts source-available | GPL-3.0 | MIT | Apache-2.0 with terms for paid features |
| Several load-balanced copies of an app | Yes, one control | One per server | Yes | Yes, with autoscaling | Yes | Stateless apps |
| Point-in-time restore | To any second in 30 days, with backup storage | Not documented | Not documented | Not documented | Not documented | Not documented |
| Postgres failover and read replicas | Yes, with synchronous replication | Not documented | Not documented | Through a third-party add-on | Not documented | Not documented |
| Network isolation between apps by default | Yes, default-deny | Shared Docker network | Shared Docker network | Not documented | Shared Docker network | Shared Docker network |
| Single sign-on | OIDC, SAML and SCIM, free | OIDC | Enterprise plan | OAuth2 | No user accounts | No user accounts |
| CPU and memory quotas per organization | Yes | Not documented | Not documented | Not documented | Not documented | Not documented |
| Built-in MCP server | Yes | Yes | Separate package | Not documented | Not documented | Not documented |
Deploy and scale
Orchard runs every app on Kubernetes. Add copies of an app and traffic spreads across them, and a new version takes traffic only once it passes its health checks.
| Feature | Orchard | Coolify | Dokploy | Kubero | Dokku | CapRover |
|---|---|---|---|---|---|---|
| Several load-balanced copies of an app | Yes, one control | One per server | Yes | Yes, with autoscaling | Yes | Stateless apps |
| Apps move off a server that fails | Multi-node clusters, apps without node-local volumes | Not automatic | Through Docker Swarm | Yes | With the k3s scheduler | Stateless apps |
| Deploys without downtime | Rolling or blue/green, apps without volumes | Rolling, not for Compose apps | Yes | Rolling, through Kubernetes | Yes | Apps without volumes |
| Blue/green deploys | Yes | Not documented | Not documented | Not documented | Not documented | Not documented |
| Apps stay up while a server drains | Apps with more than one replica | Not documented | Not documented | Not documented | Not documented | Not documented |
| Rollback restores the database too | With backup storage | No | Not documented | Not documented | Not documented | Not documented |
| Builds without a Dockerfile | Yes | Yes | Yes | Yes | Yes | Needs a captain-definition file |
| Private apps on Tailscale | Built in | Not documented | Manual guide | Not documented | Not documented | Not documented |
Databases
Orchard runs Postgres with CloudNativePG. Backups stream all day instead of once a night, and a standby takes over if the primary fails.
| Feature | Orchard | Coolify | Dokploy | Kubero | Dokku | CapRover |
|---|---|---|---|---|---|---|
| Postgres backups | Continuous, to S3 | Scheduled dumps | Scheduled dumps | Through an add-on | Scheduled dumps, through a plugin | Instance settings only |
| Point-in-time restore | To any second in 30 days, with backup storage | Not documented | Not documented | Not documented | Not documented | Not documented |
| Postgres failover and read replicas | Yes, with synchronous replication | Not documented | Not documented | Through a third-party add-on | Not documented | Not documented |
| Database forks | Yes | Not documented | Not documented | Not documented | Through a plugin | Not documented |
| Connection pooler | Yes | Not documented | Not documented | Not documented | Not documented | Not documented |
| Postgres major upgrades | After a rehearsal on a copy | Not documented | Not documented | Not documented | Not documented | Not documented |
| Automatic restore tests | Weekly, with backup storage | Not documented | Not documented | Not documented | Not documented | Not documented |
Isolation and security
Apps cannot reach each other or the platform over the network by default. They share the host kernel until you turn on a sandbox, so set one up before you let people you do not trust deploy code.
| Feature | Orchard | Coolify | Dokploy | Kubero | Dokku | CapRover |
|---|---|---|---|---|---|---|
| Network isolation between apps by default | Yes, default-deny | Shared Docker network | Shared Docker network | Not documented | Shared Docker network | Shared Docker network |
| Builds kept apart from the host | Rootless BuildKit per project | Uses the host Docker socket | Uses the host Docker socket | Privileged build pod | Uses the host Docker daemon | Uses the host Docker socket |
| Kernel sandbox for untrusted apps | gVisor or Kata, optional | Not documented | Not documented | Not documented | Not documented | Not documented |
| Sign-in or password in front of any app | Sign-in or password, free | Password; sign-in set up by hand | Password; sign-in on Enterprise plan | Password | Password, through a plugin | Password |
| Request analytics and attack signals | Both, with Traefik or HAProxy | Requests | Requests | Response times | Not documented | Not documented |
| Image vulnerability scanning | Yes | Yes, opt-in | Not documented | Yes | Not documented | Not documented |
Teams and identity
Each organization brings its own sign-in, and people arrive with the right role. All of it is in the free, open-source project.
| Feature | Orchard | Coolify | Dokploy | Kubero | Dokku | CapRover |
|---|---|---|---|---|---|---|
| Each organization brings its own SSO | Yes | No, one for the instance | Enterprise plan | No, one for the instance | No user accounts | No user accounts |
| Single sign-on | OIDC, SAML and SCIM, free | OIDC | Enterprise plan | OAuth2 | No user accounts | No user accounts |
| Verified domains and required SSO | Yes | Not documented | Required SSO on Enterprise plan | Not documented | No user accounts | No user accounts |
| Accounts created on first sign-in | Into any organization, by group | Into the root team only | Not documented | With one default role | No user accounts | No user accounts |
| SCIM provisioning | Free, per organization or instance | Not documented | Enterprise plan | Not documented | No user accounts | No user accounts |
| Provider groups set roles | Yes | No | Not documented | No | No user accounts | No user accounts |
| LDAP and Active Directory | Through Dex or Keycloak | Not documented | Not documented | Not documented | Not documented | Not documented |
| Audit log | Yes | Yes | Enterprise plan | Yes | Not documented | Not documented |
| CPU and memory quotas per organization | Yes | Not documented | Not documented | Not documented | Not documented | Not documented |
Interfaces
Use the dashboard, the CLI, an AI agent or infrastructure as code, and extend Orchard with grafts.
| Feature | Orchard | Coolify | Dokploy | Kubero | Dokku | CapRover |
|---|---|---|---|---|---|---|
| Web dashboard | Yes | Yes | Yes | Yes | Paid add-on | Yes |
| Official CLI | Yes | Yes | Yes | Yes | Yes | Yes |
| Built-in MCP server | Yes | Yes | Separate package | Not documented | Not documented | Not documented |
| Terraform provider | Official | Community | Not documented | Not documented | Community | Not documented |
| Extensions with their own pages and APIs | Yes | Not documented | Not documented | Not documented | CLI plugins | Not documented |
| License | AGPL-3.0 | Apache-2.0 | Apache-2.0, some parts source-available | GPL-3.0 | MIT | Apache-2.0 with terms for paid features |
Checked in November 2026 against Coolify 4.7.5, Dokploy 0.31.2, Kubero 3.1.1 and CapRover 1.16.0, and the current Dokku release. Each answer links to its source. A dash means the project's documentation does not mention the feature.
Something out of date? Open an issue and we will fix it. Or install Orchard and try it.