Openship: Stop letting your PaaS eat your VPS RAM

Running a self-hosted PaaS like Coolify or Dokku on a 4GB VPS is a gamble. The moment a Next.js build kicks in, the control plane spikes, starves your production containers, and your site goes offline. Your deployment tool effectively becomes a reliability risk for the app it's supposed to manage.

Openship takes a different architectural approach by decoupling the control plane from the production server. Instead of running the dashboard, build system, and database on your target box, Openship runs locally (or on a separate manager) and drives your servers via SSH.

Your Machine                Your Server
┌──────────────────────┐    ┌──────────────────────┐
│ Desktop / Web UI     │ SSH │                      │
│ Build pipeline       │────→│ Your apps. Only.     │
│ CLI / API            │    │                      │
└──────────────────────┘    └──────────────────────┘

This shift changes the math for small-scale deployments:

• Zero Resource Competition: Your VPS only runs the final container images. No build-time CPU spikes.
• Reduced Attack Surface: If you use the desktop version, there's no public dashboard port to harden.
• Faster Builds: Your laptop's CPU handles the heavy lifting, not a shared vCPU on a cheap instance.

The trade-off is that the dashboard is only active when your machine is on. If you need 24/7 push-to-deploy webhooks or team access, you'll have to host the control plane on a dedicated server.

Deep dive into the feature set

Openship isn't just a docker compose wrapper; it's a full-stack deployment suite. Here is the breakdown:

• CI/CD: Supports preview environments, staging/prod pipelines, and one-click rollbacks.
• Stack Support: Covers Node, Python, Go, Rust, PHP, Ruby, Java, .NET, and raw Docker.
• Infrastructure: Built-in Postgres, MySQL, MongoDB, Redis, and WebSocket support.
• Networking: Let's Encrypt automation via OpenResty/certbot, HTTP/3, and Brotli caching.
• SMTP: Includes a built-in mail server with DKIM/SPF/DMARC config, which is rare for this category of tool.
• Automation: Full REST API and MCP support, making it an ideal target for an LLM agent to manage your infra.

Technically, it's a TypeScript monorepo utilizing Electron for the desktop app and Next.js (React 19, Tailwind 4) for the dashboard. The behavior is toggled via the OPENSHIP_TARGET environment variable, switching between desktop and selfhosted modes.

For anyone building a real-world AI workflow or deploying lightweight microservices, this "remote-control" model is far more sustainable than the traditional "everything-on-one-box" PaaS.