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 |
| Collaboration | Files, office documents and calls |
| Home | Home automation, its device gateways, and (planned) home media |
| Security | Secrets and secure access |
| Miscellaneous | Modules with no natural stack yet |
| DevOps | Development and test capabilities — planned, no modules yet (see below) |
Each stack page is the stack's own README in the source, followed by its module catalog entries (the modules' own READMEs) — always current with the source. How to install a stack is under Install → Add Workloads. How modules depend on each other is computed from the modules themselves: see the module dependency graph.
Every module declares exactly one stack, in its own JSON — the list lives in schemas/module-fields.json and this page follows it. A module with no natural stack yet is misc — a waiting room, not a description.
DevOps (planned). The capabilities needed to develop, test and deploy software on TAPPaaS. The platform's own automation (the TAPPaaS CICD mothership) covers module lifecycle today; developer-facing modules (forge, CI runners, registries) are on the roadmap. The stack gets its page once it has a module.
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:
