What kikstart is, the apps that make it up, and how a tenant is isolated.
kikstart is a multi-tenant platform for composing applications, web and mobile, from reusable, maintained modules. A customer signs up for a solution, a named bundle of modules for their kind of business, and gets an admin, a public site and, on the paid tier, a branded mobile app. The code is real and owned: one monorepo, one shared data layer, one set of design tokens, consumed by every surface.
A tenant is one business running on kikstart. Each tenant has its own Postgres database, its own auth instance and its own object storage, and is reached on its own host. Isolation is a connection, not a column: there is no tenant id anywhere in the schema, so a query cannot reach another tenant's rows by construction.
The tenant apps, the apex apps, and how a single-tenant deployment is the same tree on one host.
One database per tenant, the platform directory that finds it, and the customer model above it.
How a host becomes a tenant, a language and a mode before the app sees the request.
What a customer buys, what a project switches on, and how modules group for a human.