Skip to content
Nairon Docs

Headless guide

The headless product is for integrators embedding Nairon inside their own product, provisioning one Nairon setup per end-customer (“tenant”) from a shared template. An organization becomes a headless-type organization (see Organizations & Projects) after applying and being approved, and its members then see headless.v2.nairon.xyz.

  • Templates — authoring a reusable flow (+ configuration) with placeholders.
  • {{fields}} — the placeholder mechanism templates are built on.
  • Instances — materializing a template into a tenant organization.
  • Versioning — publishing new template versions and upgrading existing instances.
  • Per-tenant model — how tenant organizations, access, and billing overrides work.

Everything here is available both from the headless. dashboard and programmatically via service-api — instance creation from either path goes through the same materialization logic, so scripting instance rollout is a first-class path, not a workaround.