# OpenShip vs Dokploy

URL: https://openship.io/compare/dokploy

Keep Compose and Swarm. Add Kubernetes, integrated mail and a choice of control plane.

[Migrate to OpenShip](https://openship.io/migrate/from-coolify-dokploy)

## Why choose OpenShip

OpenShip combines Docker and Compose deployments with connected Swarm, k3s clusters, scheduled backups and built-in mail administration. Run a self-hosted web dashboard, choose optional Desktop to keep the control plane private, or use managed Cloud. CLI, API, SDK and MCP share the same platform permissions, so automation grows with your operations.

### Compose, Swarm and Kubernetes

Run Compose stacks, deploy to connected Docker Swarm managers, or prepare k3s clusters with application replicas. Cluster management is available from self-hosted and desktop controllers.

[Explore this capability](https://openship.io/features/autoscaling-load-balancing)

### A mail server, built in

Operate domain mailboxes, webmail and mail DNS from OpenShip, with an external relay for outbound delivery. Keep email administration alongside your applications.

[Explore this capability](https://openship.io/features/mail)

### One platform for people and agents

Use the web dashboard, CLI, API, TypeScript SDK and MCP against the same resource permissions. Add CI workflows, scoped AI agents and chat integrations when you need them.

[Explore this capability](https://openship.io/features/ai-mcp)

## The practical differences

| What matters | OpenShip | Dokploy |
| --- | --- | --- |
| Where your apps run | Managed OpenShip Cloud, or your own servers. | Servers you provide and control. |
| Deployment model | Git, images, native Compose, static sites and workers; connected Swarm and k3s from self-hosted or desktop controllers. | Applications, databases, Docker Compose and Docker Stack. |
| Control plane | Always-on self-hosted web dashboard, managed Cloud or optional Desktop. Dashboard, CLI, API, SDK and MCP access. | A server-hosted dashboard manages your workloads. |
| Build resources | Choose controller or destination builds on supported paths; retain reusable caches with storage-aware cleanup. | Dedicated build servers are available for applications; that path does not cover Docker Compose builds. |
| Operating responsibility | Cloud infrastructure is managed. On your servers, you retain server responsibility. | You maintain the servers and the installed platform. |

## Three ways to run OpenShip

### Self-hosted web dashboard

Run OpenShip on your infrastructure for an always-on dashboard, team access, webhooks and automation. Deploy on the same server or manage connected servers.

[Get started](https://openship.io/docs/getting-started/installation)

### Managed OpenShip Cloud

Let OpenShip operate the platform and managed compute. Your projects share the CPU, memory and storage of their Cloud Space.

[Get started](https://openship.io/pricing)

### Optional desktop app

Keep the control plane on your Mac, Windows or Linux computer when you want to manage servers without exposing a public dashboard. Deployed workloads keep running when the app closes.

[Get started](https://openship.io/download)

## Where Dokploy fits

Dokploy provides application and database management with Docker and Traefik. It supports Docker Compose and Docker Stack workflows, including Swarm-based deployments.

## Plan your move

Review a Docker server import

Review discovered Docker workloads and persistent data. Existing Swarm stacks need a new OpenShip deployment; the import flow does not adopt them. Plan networking, storage and the cutover before switching traffic.

[Open migration guide](https://openship.io/migrate/from-coolify-dokploy)

## Check the details

Reviewed on 2026-11-16

- [Dokploy](https://docs.dokploy.com/docs/core)
- [Build servers](https://docs.dokploy.com/docs/core/remote-servers/build-server)
- [Docker Compose](https://docs.dokploy.com/docs/core/docker-compose)

[OpenShip documentation](https://openship.io/docs)
