Docs home

Choose the right path

Top-level sections now have their own routes, breadcrumbs, and sidebar placement so product pages can link to the exact destination.

Current status

Implemented surface and public boundaries

Public docs reflect the implemented backend while keeping preview and roadmap boundaries explicit.

Area Status Public boundary
Authorization Code + PKCE GA Default interactive client path.
OAuth Device Authorization GA when enabled Requires an enabled endpoint and a provisioned device-flow client.
mTLS certificate-bound clients GA backend contract Requires safe trusted-proxy or direct mTLS deployment configuration.
Device activation and offline leases GA Seat-bound activation, approval, heartbeat, renew, transfer, revoke, and audit diagnostics.
IoT zero-touch bootstrap Preview Default-off preview routes; no FDO or BRSKI GA claim.
Security and trust

Diligence material that stays public-safe

The docs summarize the implemented platform without linking readers to private engineering notes. Use them for deployment posture, key handling, tenant isolation, audit visibility, and production-readiness expectations.

Logical tenant isolation inside one deployed instance.
Durable signing and data-protection material for production deployments.
Audit coverage across identity, tenancy, applications, authorization, licensing, device trust, and platform operations.
Dedicated tenant deployments, region pinning, and customer-managed key commitments remain guided commercial review unless contracted.

Authoring model

Docs remain in Razor Pages for now because the site already ships that stack and the current content is componentized around shared partials. New deep-dive content can slot into route-level pages or extracted partials; a markdown docs stack is worth revisiting only when non-engineering authors need regular direct edits.