The Enterprise Kit

The Enterprise Kit defines proposed B2B requirements for each commercial edition. The items below require acceptance at the exact product version; this page does not establish that every edition implements them or is approved for sale.

Identity & access

—Org accounts + SSO (OIDC/SAML), optional SCIM provisioning
—Role-based access control — admin / member / viewer at minimum

Multi-tenancy & white-label

—Isolated tenant per customer (data + config)
—Custom branding — logo, color, name — and custom domain per tenant
—Spin up a branded instance per customer, vertical, or region

Admin console

—Seat/user management, settings, feature flags, tenant overview

Audit & compliance

—Append-only audit log of sensitive actions
—Data export + retention controls; product-specific DPA review

API & integrations

—REST API with API keys, scoped tokens, webhooks, and rate limits

Billing & licensing

—Proposed seat/usage billing + license tiers
—Purchases and payments remain disabled until the product and payment setup are approved

Security

—Encryption at rest + in transit, secrets in a vault (never in code), least-privilege access

Reliability & support

—Uptime, logging, observability; a documented support tier per plan

The entity rule

—Preserve separate free/mission and commercial editions, deployments, and data; confirm access and licensing for each.
—One owner per shared core, licensed across the entity line.
—Any approved sensitive or child-safety offer covers the engine or infrastructure only — never real child, victim, or case data.