# OpenShip vs Heroku

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

Bring your processes and data together, with ownership built in.

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

## Why choose OpenShip

Run web apps, workers and backing services as a portable project on your servers or managed Cloud. OpenShip combines deployments, service backups, domains and mail administration under an Apache 2.0 codebase. Move each process and data service deliberately, then keep operating them through one platform.

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

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

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

## The practical differences

| What matters | OpenShip | Heroku |
| --- | --- | --- |
| Where your apps run | Managed OpenShip Cloud, or your own servers. | Provider-managed infrastructure. |
| Deployment model | Git, images, native Compose, static sites and workers; connected Swarm and k3s from self-hosted or desktop controllers. | Web, worker and one-off dynos, with backing services and add-ons. |
| Control plane | Always-on self-hosted web dashboard, managed Cloud or optional Desktop. Dashboard, CLI, API, SDK and MCP access. | The provider hosts and operates the control plane. |
| Build resources | Choose controller or destination builds on supported paths; retain reusable caches with storage-aware cleanup. | Builds and deployment artifacts use the provider's supported pipeline. |
| Operating responsibility | Cloud infrastructure is managed. On your servers, you retain server responsibility. | The provider operates the platform; you configure your applications. |

## 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 Heroku fits

Heroku runs applications in managed dynos, with web, worker and one-off process types. It fits teams that value its established application and add-on ecosystem.

## Plan your move

Repository and data migration

Map Procfile entries to services and transfer config variables. Export databases and review each add-on separately. Test release commands and scheduled jobs before cutover.

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

## Check the details

Reviewed on 2026-11-16

- [Heroku dynos](https://devcenter.heroku.com/articles/dynos)

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