# Compare OpenShip with other deployment platforms

URL: https://openship.io/compare

OpenShip is an Apache 2.0 deployment platform for applications, databases and infrastructure. Run an always-on self-hosted web dashboard, use managed OpenShip Cloud, or choose the optional desktop app. Deploy through the dashboard, CLI, API, TypeScript SDK or MCP.

## 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)

## Your infrastructure. Your control plane.

Choose managed Cloud, an always-on self-hosted dashboard or optional Desktop. Keep the same deployment workflow as your infrastructure changes.

[Explore this capability](https://openship.io/features/deploy-anywhere)

## 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)

## Spend compute on your apps

Choose the build location on supported deployment paths and reuse build caches. A build on the controller can keep compilation work off a small production server; Desktop is one way to run that controller.

[Explore this capability](https://openship.io/features/build-performance)

## A direct path to your application

OpenResty serves traffic without routing requests through the OpenShip API or database. Edge analytics aggregate in memory, and static sites can be served as files without a persistent application process.

[Explore this capability](https://openship.io/features/traffic-analytics)

## 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)

## Recovery is part of the platform

Schedule service backups, choose external storage and retention, and restore through a reviewed workflow. Kubernetes deployments also have dedicated PostgreSQL, Redis and shared-volume operations.

[Explore this capability](https://openship.io/features/backups-restore)

## 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)

## Apache 2.0. A practical exit path.

The OpenShip codebase is Apache 2.0 licensed. Deploy on servers you control, import supported Docker workloads and use transfer workflows to move applications and persistent data.

[Explore this capability](https://openship.io/features/migration-import)

## All comparisons

- [OpenShip vs Vercel](https://openship.io/compare/vercel.md): Bring your frontend, backend and data onto infrastructure you control.
- [OpenShip vs Railway](https://openship.io/compare/railway.md): Keep the service workflow. Gain the freedom to run it on your servers.
- [OpenShip vs Coolify](https://openship.io/compare/coolify.md): Go from a deployment panel to a platform for infrastructure, data and automation.
- [OpenShip vs Dokploy](https://openship.io/compare/dokploy.md): Keep Compose and Swarm. Add Kubernetes, integrated mail and a choice of control plane.
- [OpenShip vs Dokku](https://openship.io/compare/dokku.md): Give your Git-push workflow a complete operations workspace.
- [OpenShip vs CapRover](https://openship.io/compare/caprover.md): Move beyond individual app deployments to a connected project workflow.
- [OpenShip vs Render](https://openship.io/compare/render.md): Keep managed convenience, with a route to infrastructure ownership.
- [OpenShip vs Fly.io](https://openship.io/compare/fly-io.md): Put your application stack, data and operations in one workspace.
- [OpenShip vs Heroku](https://openship.io/compare/heroku.md): Bring your processes and data together, with ownership built in.
- [OpenShip vs Netlify](https://openship.io/compare/netlify.md): Give your site and its supporting services the same home.
- [OpenShip vs DigitalOcean App Platform](https://openship.io/compare/digitalocean-app-platform.md): Choose your hosting provider without giving up a deployment platform.
- [OpenShip vs Self-managed VPS](https://openship.io/compare/self-managed-vps.md): Keep your server. Replace repeated setup with repeatable operations.
