Move to OpenShip

Bring your app.
Keep your stack.

Import from Railway, Vercel or an existing Docker server. Bring your repository or Compose stack. Move to OpenShip Cloud or manage your own infrastructure.

Talk through your migration

Move from your platform

See what transfers, how data moves and what to prepare.

Start with what you have

Choose the guide that matches how your app runs today.

Plan the move

Prepare the destination, verify the app, then switch traffic.

  1. Review your stack

    List your services, environment variables, data volumes, and domains. Check the destination has enough capacity.

  2. Prepare your data

    Take an application backup and choose how to transfer it. Plan a maintenance window for stateful services.

  3. Deploy and verify

    Check logs, service health, sign-in, and stored data. Make sure the app works at its destination before switching traffic.

  4. Switch your domains

    Update routing and verify HTTPS. Retire the old deployment after checking the new app and its backups.

Choose where it runs

The same deployment tools, with a hosting model that fits your team.

OpenShip Cloud

A managed resource pool for your projects. Apps, builds, and data share your plan’s capacity.

From $12/monthStart on Cloud

Your infrastructure

Connect your servers and manage deployments, data, and domains from OpenShip.

Free to self-hostSet up OpenShip

What changes

More of your stack in one place, with control over where it lives.

Before you move

The practical details, from compatibility to cutover.

Can I import from Railway or Vercel?

Yes. Choose your platform in New project → Import existing project and connect your account. Railway imports a selected project environment with its services and persistent volumes. Vercel imports supported GitHub source and settings, with options for external PostgreSQL. Review the platform guide for data requirements and features that need separate handling.

Do I need to rewrite my application?

Most container-ready applications can use their existing build and start commands. Review platform-specific APIs, storage, and environment settings before moving. Services tied to your current provider may need a replacement or configuration changes.

Can I import a running Docker application?

Yes. OpenShip scans the source and lets you review services, volumes, environment settings, and routes before importing. You can import into Cloud or a self-hosted installation. The migration guide covers access and destination requirements.

Will there be downtime?

Plan a maintenance window when moving data between servers: the source services stop while data transfers and the destination starts. Same-server adoption can reuse running containers, but changing the reverse proxy may briefly interrupt traffic. The duration depends on your app and transfer strategy.

How is OpenShip Cloud priced?

Cloud plans start at $12/month. Each plan provides a resource pool and project allowance. Apps, builds, and data share that capacity. Review the pricing page for plan limits and separately billed services such as managed proxy transfer and backups.

Can I keep my domain and DNS provider?

Yes. Add your custom domain in OpenShip and follow the routing instructions for the destination. Keep the old deployment until you have verified DNS, HTTPS, and the application.

Straight comparison

Where OpenShip is
genuinely different.

Git deploys, TLS, databases, backups, cron — every tool here has those, so they are not on this list. What is below is where the choice actually changes what you can do, and what it costs you to change your mind.

Feature
OpenShip
ManagedVercel · Netlify
Self-hostCoolify · Dokploy · Dokku

Where it runs, and what stays on

Who runs your workload
OpenShipOpenShip Cloud runs it, or self-host free on machines you own. One tool, one dashboard, and you can move either direction later.
ManagedThey run it, and run it well - but managed-only. There is no version you can host yourself.
Self-hostTheir cloud hosts only the control panel. You still bring, run and pay for every server.
What has to stay switched on
OpenShipA native Mac, Windows and Linux app. The control plane runs on your machine only while the app is open - no extra box to keep alive just to deploy.
ManagedNo desktop app. Everything runs in their cloud, all the time.
Self-hostNo desktop app, and a control-plane server that has to stay up around the clock.
Where your source code travels
OpenShipFrom the desktop app, your folder or repo goes straight to the machine that will run it. Nothing always-on sits in the middle holding your code.
ManagedUploaded to their cloud and built there.
Self-hostLands on a long-lived control-plane box first - even when that box is your own.

Included, not bolted on

Email from your own domain
OpenShipA real mail server, set up for you: mailboxes, webmail, the SPF/DKIM/DMARC chain, and sending through SES or your own SMTP.
ManagedNot included. Add SendGrid, Resend or Postmark and pay per message.
Self-hostNo managed mail server - you run the image and wire up the DNS chain yourself.
Traffic rules at the edge
OpenShipRate limits, country / IP / user-agent blocks and hotlink protection, set per route from the dashboard and applied without a reload.
ManagedFirewall and rate limiting exist, gated behind higher plans.
Self-hostPossible by hand-writing proxy config; no country rules out of the box.
Who is actually hitting your app
OpenShipPer-route traffic, country breakdown and a live request log, built in.
ManagedStrong analytics dashboards, capped or priced by plan.
Self-hostNot included - bolt on Grafana, Plausible or an ELK stack.
Access control and audit
OpenShipGrant access down to a single project, start teammates at zero permissions, and export a record of every change - on every plan.
ManagedBroad team roles; audit trail and SSO on enterprise plans.
Self-hostBroad team roles only, with little or no change history.

Fits the setup you already have

Servers with things already on them
OpenShipPoint it at a server and it picks up the containers already running there. Nothing is rebuilt, nothing is restarted.
ManagedNothing to pick up - you redeploy from source.
Self-hostCannot take on an app that is already running; you recreate each one by hand.
The proxy you already run
OpenShipCarries on with your existing Traefik, nginx or Caddy on :80 and :443, and the switch is reversible in one step.
ManagedNot applicable - their edge, their rules.
Self-hostClaims the proxy at install and expects to be the only thing on those ports.
Settings that live in your repo
OpenShipopenship.json describes build, env, domains, services and resources - reviewed in a pull request like the rest of your code.
Managedvercel.json and netlify.toml do the same thing.
Self-hostA Procfile or compose file, but domains, env and resources stay dashboard-only.

If you change your mind

Moving to a different server
OpenShipMove a running app with its volumes and certificates to another machine, then cut traffic over once it checks out.
ManagedNot applicable - you do not choose the machine.
Self-hostRedeploy on the new box and copy the volumes across by hand.
Leaving OpenShip
OpenShipOn your own servers, removing a project deletes our record and nothing else. Containers, data and config keep serving traffic, and OpenShip can pick them back up later.
ManagedNothing stays behind - the workload only ever existed in their cloud.
Self-hostDeleting tears the app down, and none of them can re-adopt a running app afterwards.

Compared against the shipping versions of each tool, July 2026. A dash means that tool genuinely matches OpenShip, or that the row does not apply to it. We would rather score a row even than invent a cross.