What Cubeship is
A PaaS you run on your own server — one VPS, or a cluster when one stops being enough.
Cubeship is a PaaS you run on your own server. docker push, and the app
is live — with HTTPS, a database beside it, backups, and a second
machine when one stops being enough. Everything it does is an HTTP API,
so the dashboard, the CLI and an agent over MCP are three doors into the
same building.
What you get
One command on a fresh VPS, and the box is running:
| A dashboard | at your instance's address, over HTTPS |
| A registry | docker push to it and the app deploys |
| Zero-downtime deploys | the new container has to look healthy before the old one goes |
| Certificates | Let's Encrypt, renewed for you, nothing to configure |
| Databases | Postgres, MySQL, MariaDB, Redis, MongoDB — one click, wired into the app's environment |
| Object storage | a SeaweedFS on the box, or your own S3 bucket |
| Backups | every database dumped on a schedule into a bucket off the machine, and restored from the same screen |
| Builds | from a Dockerfile, or from a repository with no Dockerfile at all |
| More machines | add a second server and apps spread across both |
| Charts | what every container is using, and what the machine underneath is doing |
| A shell | a terminal inside any app's container, or as root on any server — in the browser or from the CLI, with no SSH port open |
| An API, a CLI and MCP | everything the dashboard does, scriptable — and an endpoint an agent drives directly |
Everything Cubeship runs is a container, the daemon included: Postgres, the registry, the proxy, the builder and every app of yours are its siblings, with administrative services on a separate network from apps. Nothing else is installed on the host.