# OpenShip vs Fly.io

URL: https://openship.io/compare/fly-io

Put your application stack, data and operations in one workspace.

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

## Why choose OpenShip

Choose OpenShip when you want a project-level workflow for containers, Compose, domains and backups across your own servers or managed Cloud. The platform exposes the same operations through its dashboard, CLI, API and MCP. For your own multi-node infrastructure, self-hosted and desktop controllers also support k3s and connected Swarm.

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

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

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

## The practical differences

| What matters | OpenShip | Fly.io |
| --- | --- | --- |
| 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. | Fly Machines configured through Fly Launch or the Machines API. |
| 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 Fly.io fits

Fly.io provides Machines: virtual machines with controls for lifecycle, resources and region placement. It suits applications designed around Fly's regional infrastructure and APIs.

## Plan your move

Repository and data migration

Translate fly.toml settings, secrets and process groups. Plan volume and database exports, and replace Fly-specific networking. Re-test regional latency; this is not a Machines API import.

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

## Check the details

Reviewed on 2026-11-16

- [Fly Machines](https://docs.fly.io/machines/overview)

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