Most self-hosted deployment tools replace one form of complexity with another. You trade cloud bills for YAML sprawl, Dockerfiles, pipeline configs, and a weekend of docs hunting. Openship is trying to break that cycle.
What It Is
Openship is an open-source, self-hostable deployment platform. Think Heroku — but running on your own Linux server, under your control, with your data. It handles CI/CD, databases, SSL, domains, backups, and even a built-in mail server from one interface. You push code; it ships containers.
GitHub: oblien/openship · Website: openship.io
Why It's Worth Your Time
The "zero config files, zero pipelines, zero YAML" claim is what made me look twice.
Openship auto-detects your stack, configures builds, manages domains, provisions SSL via Let's Encrypt, and sets up DKIM/SPF/DMARC for email — without you touching a single config file. That's a real departure from how most self-hosted deployment tools work.
For anyone running a homelab or a VPS, the built-in mail server is the standout feature. No Mailgun account. No SendGrid API key. No third-party dependency for transactional email. It's all local, all yours.
The platform runs on anything: Hetzner, DigitalOcean, bare metal, your homelab server. Same interface regardless.
Hands On
Install the CLI:
npm i -g openship
# or if you prefer the install script:
curl -fsSL https://get.openship.io | sh
Bring it up as a background service (starts on boot, auto-restarts):
openship up
openship open # opens the web dashboard
Deploy a project:
cd your-project
openship init # links this directory to a project
openship deploy
If you're already comfortable with Docker Compose, there's a compose stack for the self-hosted install:
git clone https://github.com/oblien/openship.git && cd openship
cp .env.example .env
docker compose up -d
What happens next is where it gets interesting. Openship detects your stack, builds it, configures routing, provisions SSL, and gets your app live. No pipeline YAML. No Nginx config. No Certbot dance.
It supports every mainstream stack: Node, Python, Go, Rust, PHP, Ruby, Java, .NET, and existing Docker Compose files as-is. Databases — Postgres, MySQL, MongoDB, Redis — are managed from the same dashboard.
Honest Verdict
The docs are explicitly marked work-in-progress — the maintainers say so right in the README, which I respect. That honesty means you'll hit gaps. If your exact setup isn't covered, you're doing some inference.
Multi-node clusters and a load-balancing UI are listed as "coming next," so if you're running a distributed setup today, you're not there yet.
What exists right now is compelling for the 90% case: solo devs and small teams shipping side projects or internal tools on a VPS or homelab, who don't want to become DevOps engineers to do it. The abstraction is right. The zero-YAML promise holds up for standard stacks.
It's been gaining serious traction — 5,300+ stars and climbing fast. Something about this one has resonated with people who've been disappointed by the alternatives.
Go Try It
Start here:
npm i -g openship && openship up
Or clone the repo and use Docker Compose if that's your workflow. The official docs are thin in places but enough to get moving.