# OpenShip vs Self-managed VPS

URL: https://openship.io/compare/self-managed-vps

Keep your server. Replace repeated setup with repeatable operations.

[Migrate to OpenShip](https://openship.io/docs/guides/server-to-server-migration)

## Why choose OpenShip

Keep the infrastructure you already pay for and bring deployments, HTTPS, monitoring, backups and mail into one platform. Manage targets over SSH from an always-on web dashboard or optional Desktop. Build on a supported controller path to keep compilation off production, and reuse warm caches when deploying again.

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

### 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 | Self-managed VPS |
| --- | --- | --- |
| 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. | Your choice of processes, containers, Compose and deployment scripts. |
| Control plane | Always-on self-hosted web dashboard, managed Cloud or optional Desktop. Dashboard, CLI, API, SDK and MCP access. | You choose and maintain your administration and automation tools. |
| 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 assemble deployments, TLS, monitoring and backups. |

## 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 Self-managed VPS fits

A self-managed VPS gives you direct control of the operating system and deployment tools. It fits teams that want to assemble and maintain their own operating workflow.

## Plan your move

Review a Docker server import

Discover existing Docker services or package non-container apps first. Inventory volumes, ports and proxy rules. Back up data and decide whether to reuse the server or move to another destination.

[Open migration guide](https://openship.io/docs/guides/server-to-server-migration)

## Check the details

Reviewed on 2026-11-16

- [Docker Compose](https://docs.docker.com/compose/intro/compose-application-model/)

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