Skip to main content
Branding is stored in the database and applied at runtime, so changes take effect immediately without rebuilding an image or redeploying the chart. Administrators set it from the admin settings page.

​
Available settings

​
string
default:"r5d.chat"
Shown in the interface and page titles. 1 to 60 characters.
​
string
default:"Your persistent AI agent workspace"
Short description on the login and setup screens. Up to 140 characters.
PNG, JPEG, WebP, or SVG, stored as a data URL up to roughly 300 KB. An SVG scales best across densities.
​
image
PNG, JPEG, WebP, SVG, or ICO, stored as a data URL up to roughly 300 KB.
​
string
default:"#6d5bd0"
Six-digit hex color used for primary buttons and accents.
​
string
default:"#ffffff"
Six-digit hex color for text and icons drawn on the primary color. Choose it for contrast against your primary color.
Aim for at least a 4.5:1 contrast ratio between the primary and primary foreground colors so button labels stay readable for everyone.

​
How the agent sees your brand

The product name is injected into the agent’s system prompt, so the assistant refers to itself by your product name rather than r5d.chat.

​
Reading the current branding

Branding is served by an unauthenticated endpoint, because the login and setup screens need it before a session exists:
This endpoint is public by design and returns only presentation and setup-state data. It never includes credentials or user information.

​
Notes for operators

  • Branding lives in the database, so it is covered by your database backup and survives chart upgrades.
  • Images are stored as data URLs rather than files, which keeps the deployment stateless but means very large images bloat every page load. Compress them.
  • The response is served with cache-control: no-store, so brand changes appear on the next page load without a cache purge.