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 migrationMove 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.
A Git repository
Connect your code, review the detected build settings, and deploy your app.
A Compose stack
Bring your services together. Review variables, volumes, and domains before deploying.
An existing Docker server
Scan running services, review their data, and import them into OpenShip.
Includes apps running on Coolify, Dokploy, or DokkuAn OpenShip instance
Move your control plane from Desktop to an always-on host. Keep your workspaces together.
Plan the move
Prepare the destination, verify the app, then switch traffic.
Review your stack
List your services, environment variables, data volumes, and domains. Check the destination has enough capacity.
Prepare your data
Take an application backup and choose how to transfer it. Plan a maintenance window for stateful services.
Deploy and verify
Check logs, service health, sign-in, and stored data. Make sure the app works at its destination before switching traffic.
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 CloudYour infrastructure
Connect your servers and manage deployments, data, and domains from OpenShip.
Free to self-hostSet up OpenShipWhat changes
More of your stack in one place, with control over where it lives.
Capacity shared by your projects
Choose a Cloud plan with the CPU, memory, storage, and project allowance your work needs.
Usage-based services are billed separatelyYour runtime, in a container
Run your framework with its build and start commands, or bring a Dockerfile.
Services that belong together
Manage your app, workers, and database as one project with private service networking.
Room for background work
Run long-lived workers and scheduled jobs alongside your application, with logs in one place.
Keep your hosting options open
Use standard containers on OpenShip Cloud or your own infrastructure. The platform is open source.
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.
Where it runs, and what stays on
Included, not bolted on
Fits the setup you already have
If you change your mind
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.