Infrastructure
The layer every module runs on — auth, data access, migrations, storage, configuration, caching, hosting and operations.
Infrastructure is what a module depends on and never the reverse. Each page describes one layer as a builder meets it: what it guarantees, what it asks of a module, and where its edges are.
Three layers: the proxy's redirect, the verified session, and row-level security.
Tiers, roles, the two drivers, tokens and keyset pagination.
How one schema change reaches every tenant database, and how that is verified.
Per-tenant object storage, key shape, presigned uploads and public URLs.
Copy, settings, theme, and the browser layer beneath them.
Cached reads tagged per tenant, invalidated by the mutation that changes them.
The three hosting tiers, the database roles, where secrets live, and the control plane.
Provisioning, fleet jobs, and the operator's tools.