Capper
Single-binary cloud control plane.
Infrastructure
Capper is a self-hosted, multi-tenant cloud control plane that ships as a single Go binary. It pulls compute, networking, storage, identity, serverless functions, and observability under one roof — so you can run your own small cloud without standing up a dozen services first.
Workloads run as .cap capsules on top of Bubblewrap, chroot, crun, or runc, so isolation stays close to the metal instead of hidden behind a heavy platform. Multi-tenancy is real — organizations, accounts, projects, and IAM — and everything is reachable four consistent ways: a CLI, a REST API, a Go SDK, and the CapperWeb UI.
It handles the boring-but-critical parts too: VPC-style virtual networking with public IPs, object storage and block volumes, Lambda-style functions, audit and observability, and automatic TLS via ACME / Let's Encrypt. A capper-agent daemon manages the fleet. State lives in embedded SQLite by default, with an optional networked CapDB backend when you outgrow a single node.
github.com/rickcollette/Capper · CapperOS.org · CapperVM.com