Per-tenant model
Tenant organizations
Section titled “Tenant organizations”Each instance lives inside a tenant organization — a normal standard-type organization (see
Organizations & Projects) that carries a back-reference to
your headless-integrator organization (managingHeadlessIntegratorId). This is the same mechanism
partners use for managed organizations: the tenant org keeps its own type and billing identity,
while your integrator organization gets standing access to administer it. A tenant organization can
exist before it has any instances — create it first if you want to prepare a customer before their
first template instance is provisioned.
Access
Section titled “Access”Because access flows through the managingHeadlessIntegratorId back-reference rather than being
derived transitively through instances, your team’s access to a tenant organization doesn’t depend
on which (or how many) instances exist inside it.
Billing overrides
Section titled “Billing overrides”A headless integrator can have its own commercial terms layered on top of the standard rate card: a base monthly commitment and a per-tenant monthly rate, distinct from what an individual tenant would pay directly. This lets an integrator resell Nairon-powered functionality under its own pricing without every tenant needing its own direct billing relationship with Nairon. See Usage & billing for how usage rollups and rate cards work in general.
Status
Section titled “Status”A headless integrator organization itself has a status — applied (awaiting approval),
active, suspended, or rejected — set during the application/approval flow before any
templates or instances can be created.