Stacks¶
A stack is a container of related capabilities, delivered by modules — the smallest deployable units in TAPPaaS (see the Capabilities overview and the Meta Model for how this is modeled).
| Stack | What it delivers |
|---|---|
| Foundation | The platform itself: cluster, network, identity, backup, logging, automation |
| AI | Private AI: model serving, gateway, chat UI |
| Productivity | Files, collaboration, passwords, office |
| Home | Home automation and (planned) home media |
| IoT | Device gateways, isolated in their own zones |
| DevOps | Development and test capabilities (planned) |
Each stack page links the module catalog entries (the modules' own READMEs, always current with the source). How modules depend on each other is computed from the modules themselves: see the module dependency graph.
Modules that serve every stack rather than one: NetBird Client (mesh connectivity) and Windows Server (run Windows workloads as managed modules).
Module deployment pattern¶
Every module follows the same deployment pattern — one json contract, the platform scripts, a VM provisioned via cluster:vm, exposure via network:proxy, protection via backup:vm:
