# OpenShip vs CapRover

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

Move beyond individual app deployments to a connected project workflow.

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

## Why choose OpenShip

Bring application code, Compose services, domains and data operations into one project. OpenShip connects that workflow to a web dashboard, CLI, SDK and MCP, with dedicated k3s and connected-Swarm paths on your infrastructure. Choose a self-hosted controller or managed Cloud as your needs change.

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

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

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

## The practical differences

| What matters | OpenShip | CapRover |
| --- | --- | --- |
| 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. | Container applications and one-click app definitions. |
| 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. | Build infrastructure and resource allocation are yours to configure. |
| 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 CapRover fits

CapRover runs on your server and offers application deployment, one-click apps, domains and cluster management. It fits teams already using its server and application model.

## Plan your move

Repository and data migration

Bring the source repository or image, recreate environment variables and export persistent data. CapRover app definitions and cluster settings are not imported automatically.

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

## Check the details

Reviewed on 2026-11-16

- [CapRover](https://caprover.com/docs/get-started.html)

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