Platform · White-Label Studio
The whole workforce, under your brand.
White-Label Studio puts your name, domain, and colors on the products you license — while the parts a customer must be able to trust stay unbrandable.
Executive overview
A tenant branding profile drives colors, logo, custom domain, email identity, and customer-facing product names. Configure it once and every surface a licensed product renders follows it.
Two things are deliberately outside the editable layer: platform chrome and maturity labels. A partner can rename a product; they cannot re-label its readiness. The shipped surface today is the branding editor; the broader white-label center — partner-managed theming workflows around it — is specified and in design, and is described that way.
Core capabilities
Branding profile
Colors, logo, and product naming set per tenant, applied everywhere at once.
Custom domain
Licensed products run on your domain, not ours.
Email identity
Outbound identity follows the brand the customer knows.
Locked trust layer
Maturity labels and platform chrome are structurally unbrandable.
Why enterprises care
Your brand equity
The customer relationship stays yours — your domain, your name on every surface they touch.
Launch without a rebuild
Branding is configuration, not a fork. No parallel codebase to maintain, no upgrade tax.
Trust that protects you
Because readiness labels can't be re-branded, a partner can never be accused of dressing one up.
How it governs the workforce
Whatever the brand on top, the governance underneath is identical: same audit trail, same maturity gates, same kill switches. White-labeling changes the name on the door, never the rules of employment.
- Per-tenant
- Custom domain
- Trust layer locked
Across the ecosystem
See it run a workforce.
A demo walks the module on live platform data — no slide deck.