Tenant Lifecycle #

A tenant declared, built, admitted, operated and removed as code: through the Deevnet API and its Terraform provider, from the tenant’s own repository. Each tenant supplies its own IaC/CaC and can be rebuilt from scratch against the substrate.

Legend: ✅ Complete | 🔄 In Progress | ⏳ Planned

Value objectives: Fast tenant delivery, Rebuild from code, One part-time operator can run it

• ✅ The Deevnet API and its Terraform provider deployed; tenants built through them (CHG-0010) 2026-09-17
• ✅ The first tenant built end to end from its own repository: code, internet access and DNS 2026-09-03
• ✅ A reference tenant a newcomer can copy 2026-09-27
• ✅ Tenants log in to their own workloads and deploy their app (CHG-0028) 2026-09-27
• ✅ Tenants admitted and removed, and their Wi-Fi keys rotated, by make targets on the build server 2026-09-29
• ✅ A tenant that lost the keys to its own state gets back in with a new key from the operator (CHG-0060) 2026-11-09
• ⏳ A tenant rebuilt from its own code in a drill
• ✅ The boundary between tenants and the site’s infrastructure written as one specification 2026-11-01

Project plan: Tenant Lifecycle