Overview
infra defines a self-hosted application platform: the place the operator’s own capabilities run by default, so that none of them depends on a vendor’s hosting product.
- It’s rebuilt, not repaired. The platform can be stood up from nothing, from this repository, in at most 60 minutes.
- It’s self-hosted, not self-owned. It spans a public cloud and the home lab. “Self-hosted” means the operator controls it end to end, not that every part runs on hardware the operator owns.
- It’s run by one operator, in at most 2 hours a week. A designated successor holds sealed credentials and uses them only if the operator can’t.
- Its tenants are the operator’s capabilities. Their end users reach the tenants, never the platform.
The platform is being rebuilt from scratch, as the charter sets out.
Reading order
The site reads in the order its readers need it: the operator first, then a successor who has to take over, then a capability owner bringing a tenant.
- Getting started: standing the platform up from nothing, first as a drill and then live.
- Fundamentals: the ideas every part of the platform builds on.
- The platform: one page per part, in the order a rebuild stands them up.
- Operating: running the platform day to day, handing it to a successor, and recovering it.
- Hosting a tenant: what a capability owner needs to run a tenant on the platform.
Start with Getting started.