Brand and Readiness

Brand and readiness features determine when customer-facing capabilities can safely go live.

Tenant color safety

Motornauts stores a validated tenant brand color, not arbitrary CSS. The platform derives a versioned light and dark customer-signal palette from that seed, chooses a readable foreground for each mode, and checks normal-text contrast before exposing the palette. If a complete safe pair cannot be produced, customer surfaces use the Motornauts Ignition signal color and the settings experience explains the fallback. A tenant color never changes semantic status meanings, destructive styling, focus visibility, typography, spacing, navigation, or staff-workspace action colors.

The raw supporting color remains a limited identity input. It is not a second unrestricted theme slot. Logos, custom domains, emails, PDFs, and portals still follow their separate asset, verification, privacy, and readiness rules.

Tenant Admins can review the derived result in the Brand and support workspace. Stone and Carbon are shown side by side even when the current app theme is different. An adjustment notice means the seed was bounded for readable output; a fallback notice means customer surfaces use the safe Ignition signal until a valid complete pair is saved. The preview is authoritative for these customer signal slots, while document, email, and portal adoption still follows each surface’s rollout and readiness.

Logo uploads accept PNG, JPEG, and WebP and are cropped to a 2:1 preview before upload. Motornauts verifies and re-encodes an upload before making it current. SVG and arbitrary embedded styling are not accepted. Signed upload/view links are temporary implementation details and should never be copied into public documentation or support notes.

Readiness concepts

Safe routing rule

Unknown, inactive, or unverified hostnames should fail closed. They should not reveal another tenant’s data or silently route to the wrong tenant.