Kuberfy is an ultra-lightweight self-hosted PaaS: a single compiled binary, an embedded SQLite database, and Traefik for automatic HTTPS. No PostgreSQL to babysit, no Redis to justify.
Confirmed on 1 vCPU / 1 GB RAM ($3–$5/mo VPS) • x86_64 & ARM64
Dashboard screenshot coming soon
These numbers come from docker stats on clean VMs — verified end-to-end through full installation on the smallest instance sizes available.
23 MB
Kuberfy Control Plane
API, web UI, and SQLite reader
14 MB
Traefik Edge Proxy
Automatic Let's Encrypt TLS termination
1 vCPU / 1 GB
Confirmed Minimum VPS
Installs and deploys with zero OOM errors
< 60s
One-Command Install
Provisions Docker, Swarm, Traefik & Kuberfy
The remaining memory on your server is completely free for your actual applications, not eaten up by the management dashboard.
Most self-hosted platforms bundle an entire PostgreSQL server, a Redis instance, and an interpreted runtime just to manage a handful of containers. Here is how Kuberfy compares directly with other popular self-hosted platforms:
| Architecture & Footprint | Typical PaaS (Coolify / Dokploy) | Kuberfy |
|---|---|---|
| Internal Database | PostgreSQL container (~150–300 MB idle RAM) requiring manual backups and migrations | Embedded SQLite: single file, zero server processes, zero RAM overhead |
| Control Plane Runtime | Interpreted Node.js / Python running continuously | Compiled static binary (via Bun) — instant boot, minimal memory footprint |
| Extra Services | Redis cache, queue daemons, WebSocket bridges (Soketi) | None — a single lightweight process handles API, UI, and database |
| Idle Memory Overhead | 500 MB – 1.5 GB RAM consumed before deploying any user apps | ~37 MB total (Kuberfy + Traefik combined) |
| Minimum Hardware | 2 GB RAM required; 4 GB strongly recommended | 1 GB RAM confirmed working under real workloads |
| TLS & Routing | Manual certbot scripts or complex reverse proxy stacks | Traefik with automated Let's Encrypt renewal out of the box |
A clean, reliable deployment loop built for production — without unnecessary bloat.
Point Kuberfy to a GitHub/GitLab repository with a Dockerfile, or pull pre-built images from Docker Hub and GHCR.
Deploy Gitea, Vaultwarden, n8n, and 33 other open-source apps with secrets generated and volumes wired up automatically.
Attach your custom domain and Traefik negotiates SSL certificates with Let's Encrypt automatically. Zero manual Nginx configuration.
Compiled into a single binary running alongside SQLite. Boot time is under a second and it leaves your server resources for your apps.
Watch build outputs and runtime container logs stream in real-time right from your dashboard. A failed build is never a mystery.
Group related services under isolated projects. Manage environment variables securely with encrypted storage.
Official multi-arch container images. Runs smoothly on Raspberry Pi, Hetzner ARM, AWS Graviton, and Oracle Cloud Free Tier.
No fragile interconnected microservices. Three distinct layers designed so your user applications never suffer downtime even if the management panel restarts.
Client HTTPS/HTTP requests enter via standard ports 80 and 443.
Terminates TLS, auto-renews Let's Encrypt certificates, and routes directly to app containers.
A ~23 MB compiled binary reading an embedded SQLite file. Communicates with the Docker socket.
Runs your application containers on isolated internal overlay networks.
🛡️ High availability principle: If Kuberfy is updated or restarted, Traefik continues routing traffic directly to your containers without dropped requests.
Run the single-line command on your Linux server. Kuberfy configures Docker, Swarm, Traefik, and starts the panel automatically.
$ curl -sSL https://kuberfy.pages.dev/install.sh | sudo shClear, straightforward answers about how Kuberfy works.
For a single-server deployment platform managing dozens or even hundreds of containers, SQLite provides sub-millisecond query times and zero RAM overhead. PostgreSQL would consume 150–300 MB of RAM just sitting idle. Backing up Kuberfy is as simple as copying a single `.sqlite` file.
No. Traefik and Docker Swarm maintain all application routing and container lifecycles independently. Kuberfy only orchestrates state — if the Kuberfy container stops, your applications continue serving incoming traffic seamlessly.
Yes! The official Kuberfy Docker image is built with multi-arch manifests supporting both amd64 (x86_64) and arm64. It works out-of-the-box on AWS Graviton, Hetzner ARM, Apple Silicon (dev), and Oracle Cloud ARM instances.
Yes, Kuberfy is open source and licensed under BUSL 1.1. You can freely inspect the code on GitHub, self-host it on your own servers, and use it for personal and commercial projects.
Install Kuberfy in under a minute and start deploying without platform bloat.
No credit card required. Free and open source.