Self-hostable deployment platform

Deploy to your own server, without touching a terminal

One install script turns a fresh VPS into a portal that builds and runs Dockerised web applications behind an automatic TLS reverse proxy, with server and container monitoring. Push to your branch and it ships itself.

What it does

• Deploy from Git or a ZIP

  Point it at a repository and it clones, builds, runs, and health-gates the result. A push to the deployed branch ships itself through a signed webhook. Upload a ZIP instead if you would rather not connect anything.

• Your compose file, judged before it runs

  The file you wrote is never run as written. It is parsed, checked against a reject list — privileged containers, host namespaces, host networking, added capabilities, weakened confinement, bind mounts outside your own files — and only the rewritten copy reaches Docker.

• HTTPS that arrives on its own

  Add a hostname, point the record it shows you, and the platform verifies the DNS resolves to your server before it attaches a router. Certificates are issued over HTTP-01, which needs no API token from your DNS provider.

• Configuration that never touches the disk

  Environment variables are encrypted at rest under a key that lives outside the database, returned by no endpoint, scrubbed out of build logs, and handed to Docker through the environment of one process rather than written into any file.

• Monitoring that describes the machine

  CPU, memory, disk, network, and per-container usage — including steal time, which is how you find out a slow application is a noisy neighbour rather than your code. Metrics are pre-aggregated so a year of history stays a few megabytes.

• Alerts you can act on

  Disk pressure, sustained memory pressure, container restart loops, failing health checks, expiring certificates, and failed deployments — in the portal, by email, and by signed webhook. Every rule both opens and resolves, so the list stays worth reading.

• Databases without a second bill

  One-click PostgreSQL, Redis, and MinIO with scheduled backups to local disk or S3. A managed service publishes no port: your applications reach it by name on a shared network.

• Rollback in one click

  Every deployment records the image it produced and the commit that caused it. Rolling back re-applies a previous image with no rebuild, and the history keeps both entries.

Or let us run the control plane

The hosted version manages servers you already own. You run one command on your VPS and a small agent dials out to us — no inbound firewall rule, no port to open, and no SSH key handed over. Stop the process and the connection is gone.

• Your machine, your data, your Docker daemon. We hold no credential to it beyond a token you can rotate.
• The same platform as the self-hosted edition, configured differently rather than built differently.
• Self-hosting stays free and unlimited. Nothing here is held back from it.

Questions

Does the hosted version need access to my server?

It needs an agent running on it. The agent dials out to the control plane over one outbound connection, so you open no port and write no firewall rule. It authenticates with a token you can rotate or revoke from the portal at any time.

What happens to my applications if I stop paying?

They keep running. They are containers on your machine, started by Docker Compose files the platform wrote to your disk — nothing about them depends on the control plane staying reachable. You lose the portal, not the workloads.

Can I move from hosted to self-hosted?

Yes. It is the same platform; the difference is where the control plane runs. Install it on a machine of your own and point it at the same servers.

What is not included?

Kubernetes, Swarm, multi-node scheduling, autoscaling, per-pull-request preview environments, a bundled Prometheus or Grafana, serverless functions, and a CDN. Each is a rabbit hole a 2 vCPU box cannot afford, and pretending otherwise would make the rest worse.