PHASE · 01
Deploy anything — native pipelines for every stack.
Node.js and Docker deploy natively today — Openship auto-detects them, builds them, and runs them with zero config. Every other stack — Go, Rust, Python, Ruby, PHP, Java & Kotlin, .NET, Elixir — already ships through the universal pipeline: bring your install, build, and start commands (or a Dockerfile) and deploy. Next, we're promoting each language to first-class, auto-detected native support — one stack at a time, and faster with your help.
Native builders: Node.js & Docker
Auto-detected build + run for the two heaviest cases — the full JavaScript/TypeScript framework family and any Dockerfile or Compose file. No commands to write, no images to pick: link the repo and ship.
First-class detection for every language
Go, Rust, Python, Ruby, PHP, Java/Kotlin, .NET and Elixir become auto-detected natives — sensible build image, install, build, and start inferred for you. Until each lands, the universal pipeline already deploys them with your own commands, so nothing is blocked in the meantime.
PHASE · 02
Scale out — one deploy target, many machines.
Clustering & multi-node
Group your servers into a cluster and ship to it as one. Add a node from the dashboard and Openship spreads containers across the fleet, health-checks them, and reschedules failures automatically — no control plane to babysit, no YAML to hand-write.
Shared volumes across nodes
A volume that follows your app across the fleet — one shared, replicated folder any node can read and write. Uploads, caches, and stateful data stop being pinned to a single machine, so a container can reschedule anywhere without leaving its files behind.
Database clustering & replicas
Turn a managed database into a cluster: read replicas to spread query load, streaming replication across nodes, and automatic failover so losing a machine doesn't mean downtime. One click from the dashboard, no manual pg_basebackup.
Docker Swarm
Prefer Swarm? Point Openship at a Swarm cluster and deploy services, scale replicas, and roll updates across the swarm from the same dashboard — your orchestrator of choice, our interface.
Load balancing
Traffic distributed across healthy nodes out of the box, with a slider for weights and automatic connection draining on every deploy. Zero-downtime rollouts become the default, not a weekend project.
PHASE · 03
Automate — jobs that react, at any scale.
Event & webhook triggers
Fire a deploy or a job from an inbound webhook — per-hook URLs with their own token or HMAC auth — or from a git push. Chaining those triggers into self-running pipelines with platform events (finished deploy, failed health check) is what comes next.
Queue & advanced runners
A durable queue behind every job: concurrency limits, backoff, distributed workers, and crash-safe re-drive so an interrupted run never disappears. Same jobs you already write — production-grade underneath.
PHASE · 04
Route & protect — your edge, your rules.
Advanced route rules & WAF
Per-route rules — rate limits, geo and user-agent filters, bans, hotlink protection — are live on self-hosted, edited from the dashboard and applied instantly with no reloads or config files. Next: composing them into a managed WAF and bringing the same rules to cloud.
Self-hosted CDN
Once the cluster is in place, turn it into your own CDN: cache and serve static assets from every node, close to your users. No third party, no per-gigabyte bill — just your fleet, doing more.
PHASE · 05
Make it yours — your brand, your look.
White-label & branding
Put your name on it. Swap the logo, colors, product name, and login screen so the dashboard your team — or your clients — see is unmistakably yours. Built for agencies and resellers.
Custom CSS
Drop in your own CSS to restyle anything, from a single accent to a full reskin. Pairs with white-label so the whole surface can match your brand down to the pixel.
PHASE · 06
★ FlagshipCommand the cloud — AWS & Azure, finally pleasant.
AWS and Azure are extraordinarily powerful — and extraordinarily complex. Hundreds of services, a maze of consoles, and a bill you need a degree to read. If you don't want all that — if you just need to see what's running, spin something up, and get on with your day — Openship becomes a clean, opinionated layer over both: the 20% you actually use, without the 80% you don't. Connect your account and manage it from the same place you deploy.
AWS console & control
Connect your AWS account and run it from Openship — EC2, S3, RDS, IAM and more — through an interface that's actually fast and clean. A better console for the services you touch every day, right next to your deploys.
Azure console & control
The same for Azure: connect a subscription and manage VMs, storage, databases, and networking from one calm surface — no more hunting through the portal to get one thing done.
PHASE · 07
Integrate — connect the rest of your stack.
GitLab integration
First-class GitLab alongside GitHub — repositories, branches, merge-request preview environments, and push-to-deploy, wired exactly the same way you already know.
Cloudflare integration
Manage Cloudflare DNS, proxying, and origin certificates straight from Openship, so your domains and edge stay in sync with every deploy — no tab-hopping to keep records straight.
Amazon SES & SMTP mail
Beyond self-hosted mail: connect Amazon SES or any SMTP relay and manage senders, domains, and deliverability from Openship — pick the mail engine that fits the job, hosted or your own. Live today.
LATER
Beyond the browser — in your pocket.
Mobile app
Control your fleet from your pocket — deploys, live logs, and alerts pushed to your phone the moment something happens. End-to-end connected to your own self-hosted instance, with no cloud middleman in between.
Shape it with us.
Everything here is built in the open. Open an issue, upvote what matters to you, or send a pull request — the roadmap follows the community.