OpenShip
OpenShip CloudFrom $12/month

Deploy anything.Own everything.

Run your apps, databases, and workflows from one place. Start on OpenShip Cloud or connect your own servers.

Start on Cloud Self-host for free

Designed for your favorite stack

Next.js
Node
Python
Go
Rust
Docker
Postgres
Redis
Ruby on Rails
Laravel
Django
Bun
OpenShip dashboard

Apps, data, and automation.
Run it all from OpenShip.

Deploy code, run services, and manage the infrastructure behind them. Use OpenShip Cloud or connect your own servers.

Explore all 45 features

Deploy your stack

Applications, databases, and public endpoints in the same project.

Compose & multi-service

Ship a whole stack — app, worker, db — as one project.

Databases & service connections

Database templates, private wiring, and supported cluster operations.

Domains & SSL

Connect domains, verify DNS, and manage HTTPS certificates.

Automate the work

Build delivery pipelines, schedule tasks, and connect your AI tools.

Actions & CI

GitHub-compatible workflows with visual editing and live execution.

Scheduled jobs & automation

Cron-like jobs and webhook-triggered actions with live logs.

AI & MCP

Drive deploys from Claude, Cursor, or any MCP client.

Stay in control

Follow service health, protect your data, and recover a previous release.

Logs, metrics & incidents

Streaming logs and real-time metrics across every service.

Backups & restore

Scheduled recovery points with your destinations and retention.

Release history & rollbacks

Restore a retained application image from deployment history.

Your workflow, your interface.Dashboard, desktop & CLIAPI & SDKAI & MCP

How it works

From git push to live,
on your infrastructure.

Connect your code, choose a destination, and follow every deployment from build logs to a healthy app.

  1. Connect

    Start with your code.

    Link a repository, choose a branch, and pick OpenShip Cloud or a connected server. Review the detected framework and settings before you deploy.

    Read the guide
    Choose a repository

  2. Build

    Follow every build.

    Build on your machine, a connected server, or Cloud. Follow the output as it happens, see the current phase, and keep the deployment history with your project.

    Read the guide
    Build progress and logs

  3. Ship

    From image to running app.

    Deploy the built image to your chosen destination. Track startup and health checks in the same deployment view, then open the app when it’s ready.

    Read the guide
    A deployment, ready to serve

  4. Route

    Give it a home on the web.

    Add your domain, review the route, and let OpenShip manage HTTPS. Your domain and port settings stay with the project.

    Read the guide
    Domains and routing

  5. Operate

    Keep production in view.

    Watch resource usage and service health, inspect logs, and redeploy or roll back from the same dashboard. The tools you need stay with your app after launch.

    Read the guide
    Resources and monitoring
Choose a repository

Where it runs

Cloud, self-hosted,
or both.

Same platform, three deployment shapes - and you can switch any day.

View pricing
01Managed

OpenShip Cloud

A shared CPU, RAM and storage pool for your projects. Deploy apps, databases, and workers within your plan’s capacity.

  • Resources shared across projects and builds
  • 99% monthly uptime guarantee
  • Email and in-app support included
From $12/moMonthly or annual billingStart on Cloud
02Self-hosted

Your servers

Run the entire platform on machines you own. Any Linux box, any provider, any region. Add nodes as you grow.

  • Connect any VPS - Hetzner, DO, AWS, bare metal
  • Multi-server fan-out across regions
  • No agent or dashboard on your boxes
Free & open-sourceApache-2.0 — self-host today, no billingStart self-hosting
03Hybrid

Mix and match

Cloud for the burst, your servers for sensitive data. One control plane. Move workloads without rebuilding.

  • Apps on your servers, services on the cloud
  • Or production locally, previews managed
  • One billing, one team, one dashboard
Cloud plan + your serversOne Cloud subscription, unlimited self-hosted boxesExplore hybrid
Migrate any day

Cloud self-hosted.
One click, any time.

Your apps are plain containers and your services are standard images. Move workloads between OpenShip Cloud and your own servers without rebuilding, rewriting, or paying an exit tax. Click, confirm, done.

The app catalog

Your next app.
Already assembled.

A backend for your next project. A database for your data. The tools your team uses every day. Explore ready-to-deploy apps, then choose where they live.

Browse all apps

52 available templates · Cloud and connected servers

BackendsDatabasesContent & publishingAutomationAnalyticsDeveloper tools

Supabase

Full self-hosted Supabase — Postgres, Auth, REST, Realtime, Storage, and Studio behind one API gateway.

Backends

n8n

Workflow automation — connect apps and APIs with a visual editor.

Automation

Ghost

Publishing for blogs, newsletters, and membership sites, with a focused editor and your own database.

Content & publishing

PostgreSQL + pgAdmin

A persistent PostgreSQL database with pgAdmin for browser-based administration and SQL queries.

Databases

Nextcloud

Private file sync and sharing with Nextcloud Admin, MariaDB, Redis file locking, and scheduled background jobs.

Developer tools

Gitea

Lightweight Git hosting with repositories, issues, and pull requests.

Developer tools

Umami

Privacy-friendly, cookie-free web analytics — a self-hosted alternative to Google Analytics. Add one script tag to your site and see traffic in a clean dashboard you own.

Analytics

MinIO

S3-compatible object storage with a web console — point any S3 client (aws-cli, SDKs) at it, or bind a bucket straight into another project's uploads.

Databases

NocoDB

An Airtable-style spreadsheet interface for working with SQL-backed data.

Databases
Find your next app in the catalog

OpenShip Mail

Your email.
Your control panel.

Team inboxes and transactional email on your own server. Manage accounts, delivery, and backups alongside your apps.

  • Domains & mailboxes
  • Delivery & DNS
  • Backups & recovery
Explore MailRead the guide

Mail server management for Desktop and self-hosted OpenShip.

OpenShip Mail control panel showing mailbox accounts, quotas, and administration tabs.Mail client showing an inbox and an open conversation.
Mail client & control panelYour domains. Your accounts. One place.

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.

Our privacy commitment

Your data.
Your business.

We don’t browse your private code, databases, or files. When you need help, support stays focused on the technical issue you ask us to investigate.

Read our privacy policy Terms of service

  • Support starts with your approval.

    Our team reviews technical details only when you ask for help or approve a review.

  • Technical details only.

    Relevant deployment metadata and sanitized failure diagnostics. Your code, database contents, files, and secret values stay out of support review.

  • A commitment in writing.

    Our Privacy Policy and Terms set out how we handle your data, alongside your rights under applicable data protection law.

Open source

Yours to run, fork,
and ship.

The dashboard, the CLI, the agents, the infrastructure adapters - all public, all readable, all auditable. Run it on a Raspberry Pi or a fleet. Contribute back when you want to.

Star on GitHubRead the source

Ready to ship?

Cloud or a server you own.
No lock-in, no configuration files.

Get startedView on GitHub
  • CLI, web & desktop
  • Cloud or self-hosted
  • No lock-in
  • Open source