Skip to main content

Platform

The platform-level concepts: how Krios's hierarchy fits together, who can do what, and how multi-tenant isolation works.

Hierarchy​

Tenant (billing + user pool)
  └── Project (isolated content workspace)
        └── Environment (production / draft / named)
              └── Site (hostname + locales)

Every table except tenants carries tenantId; audit_logs carries tenantId too, but its projectId is optional (null for tenant-level actions). Most application tables also carry projectId. Content-bearing tables additionally carry environmentId. Cross-tenant queries are not expressible — the scoped Prisma client filters every query.

Sub-pages​