Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
Published DS package · System Layer · Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Themes apply tenant and vertical identity on top of the shared token contract, so the same UI can feel like Platform, BitHire, or Evnto without forking components.
Brand signal, emphasis hierarchy, surface treatment, and motion tone.
Bad use of themes
Business rules, permission logic, workflow branching, or route-level product behavior.
Tenant comparison
Same engine, all first-party tenants
Live providersThree tenant presets
Engines
Icons
Primitives93 documented routes
Display
Inputs
Feedback
Layout
Navigation
Overlay
Patterns49 documented routes
Data
Forms
Visualization
Communication
Feedback
Workflow
Navigation
Commerce
Customization
Identity
Shell
Structures24 documented routes
Headers
Workspace
Shell
Record
Dashboard
Feedback
Surfaces36 documented routes
Admin
Data
Experience
Forms
Operations
Workspace
Verticals3 documented routes
Platform
Bit Hire
Evnto
Playground1 documented routes
Playground
Developers2 documented routes
Developers
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
roundedtop bar · solid dividers
Themes
Themes
Active profilePlatform Flagship
Runtime postureRottay / modern
Tenant visual identities and how they reshape the same component system.
Runtime controls
TenantRottay
EngineModern
Real side-by-side tenant previews
Each card below renders the same DS primitives under a different tenant preset. Use this section to compare brand signal, surface chemistry, and action posture without relying on showroom-local styling.
Brand signalPrimary emphasis, semantic bias, and accent energy should all move with the tenant.
Surface chemistryCards, neutrals, and contrast rhythm should shift without changing the component API.
Operational postureThe same controls should feel more enterprise, recruiting, or event-driven by runtime alone.
What themes should change
Scope guardrails
Themes should shift brand, not behaviorUse them to move tone, emphasis, and surface chemistry. Keep product logic, permissions, and routing outside the theme layer.
Palette
Surface chemistry
Motion tone
Component chrome
Brand signalPalette, emphasis moments, hero accents, semantic tone bias.
Surface chemistryCard styling, gradients, translucency, borders, and elevation flavor.
Interaction detailsMotion softness, focus treatment, and component-specific chrome variables.
Not business logicThemes should not encode product rules, permissions, or workflow branching.
Theme providerToken-aware snippet from the active showroom runtime.