The four surfaces

Nairon v2 is one Next.js application (management-ui) exposed on four subdomains under v2.nairon.xyz. Which subdomain you land on determines which mount of the app you see; a request’s Host header is rewritten internally to a path prefix (platform. → /platform, headless. → /headless), while app. and partners. serve their own top-level routes directly.

app.v2.nairon.xyz — the default surface

Every account starts here. This is where you create an organization, create projects, build flows, manage phone numbers and knowledge bases, and view call history and analytics. If a project is created with type = platform, clicking into it from app. redirects you straight to the platform. mount for that project — hotline-only navigation (flows, phone numbers) simply doesn’t apply to a platform project, so there is no stub UI for it on app..

partners.v2.nairon.xyz — the partner portal

Organizations of type partner see their referral/reseller console here: commission tracking, managed customer organizations, and (for partner tiers above affiliate) reusable flow templates. See the Partner guide.

platform.v2.nairon.xyz — the platform console

For projects with type = platform. This is the control surface for consuming Nairon programmatically: mint and revoke API keys, view usage broken down by service, and see an invoice preview. It has no flow editor or phone number management — those concepts don’t exist for a platform-type project, whose “product” is the OpenAI-compatible API and the REST/MCP control plane. See the Developer guide.

headless.v2.nairon.xyz — the headless integrator portal

For organizations of type headless. Integrators author templates (flows with {{field}} placeholders), publish versions, and spin up instances of a template into their own tenant organizations — each instance is a materialized, independently editable copy that can later be upgraded to a newer template version. See the Headless guide.

Shared session, one sign-in

Authentication is a single Supabase session shared across all four subdomains — the auth cookie is scoped to .v2.nairon.xyz, so signing in on app. also authenticates you on platform. and headless. without a second login. partners. and headless. each have their own protected-route lists and access checks (an organization must be the right type, or must be a managed org under a partner/headless integrator, to see the corresponding portal) but they all resolve through the same session.

What’s not here

docs.v2.nairon.xyz (this site) and the API hosts (api.v2.nairon.xyz for platform-api, service.v2.nairon.xyz for service-api) are separate services, not additional mounts of management-ui. See API Reference for those.