Self-hosted PaaS
Kuberfy is the lightest self-hosted platform for shipping applications from your own servers — a single compiled binary, an embedded database, and Traefik for HTTPS. No Postgres to babysit, no Redis to justify.
$ curl -sSL https://kuberfy.pages.dev/install.sh | sudo shOne command, one Linux server, root access. That's the whole install.
Most self-hosted platforms bundle a database server, a cache, and a full interpreted runtime just to manage a handful of containers. Kuberfy's control plane is a single compiled process reading a single SQLite file.
These numbers come from real Multipass VMs, not a spec sheet — steady-state usage captured with docker stats, and the install itself verified end-to-end on the smallest instance size that still worked.
23 MB
Kuberfy control plane, steady-state RAM
14 MB
Traefik, steady-state RAM
1 vCPU / 1 GB
Confirmed minimum — installs and runs with no OOM
~5 MB
Base image, before your application
The rest of a server's memory goes to dockerd, containerd, and buildkit — not to Kuberfy itself.
The core deploy loop, done well — not a platform trying to be everything at once.
Point Kuberfy at a repository and Dockerfile, or an existing image. It builds or pulls, then runs it.
Every application gets a routed domain and a signed certificate the moment it's attached — no manual config.
Group related services under a project, each with its own applications, domains, and deploy history.
Every build and run is recorded with its status and complete output, so a failure is never a mystery.
Email and password auth with an admin role, so you can hand out access without handing out root.
A single script provisions Docker, Swarm, Traefik, and Kuberfy itself on a bare server.
Traefik terminates TLS at the edge. Kuberfy holds the state and talks to the Docker socket. Docker runs your containers. That's the entire runtime footprint.