Designed and built Reguant as a solo systems project: a Go control plane (~15–20MB), in-process SQLite via modernc.org/sqlite (~2–5MB), and an Nginx reverse proxy (~5–8MB) for a total idle footprint of roughly 25–35MB. Hybrid deployment modes (Docker isolation or native systemd processes with zero container overhead), WebSocket-streamed build logs and server stats, automatic Certbot HTTPS, S3/R2 offsite database replication, deployment history with commit-SHA rollback, a CI-success gate for webhook deploys, GitHub OAuth for the dashboard, and a single-line VPS installer.

Reguant — a PaaS on a RAM diet

Reguant is a self-hosted Platform-as-a-Service built in Go, SQLite, and Nginx. It deploys and manages applications with a total idle footprint under 40MB of RAM — significantly lighter than heavy alternatives like Coolify.

The RAM budget (idle)

Go control plane: ~15–20MB
SQLite (in-process): ~2–5MB
Nginx reverse proxy: ~5–8MB
Dashboard: 0MB (static, runs in your browser)
Total: ~25–35MB

Capability highlights

Hybrid deploys: Docker containers for isolation, or native systemd processes with zero container overhead for extremely low-RAM machines.
Zero-downtime lifecycle: stop/start/restart, 50-entry deployment history, and rollback to any commit SHA.
Automatic HTTPS: Certbot + Let’s Encrypt wired into Nginx vhosts in place.
Offsite backups: continuous SQLite replication to S3-compatible storage (R2, S3, B2).
CI gate: webhook deploys can require a green GitHub commit status first.
One-line install: curl -fsSL .../install.sh | bash provisions Go, Docker, Nginx, Certbot, and the systemd service.