Build

White Label

Deliver IIOS as your own product. Partners layer brand tokens, custom domains, and configuration over a shared engine — every tenant looks and feels native while running on one governed platform.

ForPartnersDevelopersEnterprise architects

Composition model

White labeling is additive. The IIOS core engine stays shared; each partner supplies a brand layer (theme, logo, domain) that is applied per tenant at request time. Upgrades to the core reach every partner instance without a rebuild.

White-label composition

One shared engine; brand and domain layers resolve per tenant.

What you can customize

Surface	Customizable	Mechanism
Visual theme	Colors, radius, typography, logo	CSS design tokens
Domain	Custom domain + TLS	Managed domain mapping
Email & notifications	Sender identity and templates	Brand config
Terminology	Product name and labels	i18n / string overrides
Core engine	Graph, reasoning, security	Shared — not forked

Configuring a brand

A brand is a small, versioned configuration. Theme values are design tokens, so styling stays consistent and accessible without shipping custom CSS per partner.

brand/partner-a.ts

// brand/partner-a.ts — a partner's white-label configuration
export default defineBrand({
  name: "NorthPeak Ops",
  domain: "ops.northpeak.com",
  theme: {
    "--primary": "oklch(0.55 0.16 250)",
    "--radius": "0.5rem",
    logo: "/brands/northpeak/logo.svg",
  },
  emailFrom: "no-reply@northpeak.com",
})

Tokens, not stylesheets

Brands override design tokens rather than arbitrary CSS. This keeps every white-label instance on the same accessible, maintainable component system.

Isolation guarantees

Each partner tenant is isolated at the data and identity layers.
Brand configuration never affects another tenant or the shared engine.
Custom domains terminate TLS per partner with managed certificates.