Custom Branding

Customize the ElasticClaw Server web UI name and logo from hub.yaml.

Overview

ElasticClaw Server supports lightweight white-label branding through the branding block in hub.yaml. Branding is loaded by the web UI from the server and affects the product name shown in the page title and sidebar, plus the logo used in the agent conversation view.

The branding endpoint is public so the login screen and embedded web UI can render the correct name before a user authenticates. It only returns the configured display fields.

Configure hub.yaml

Add a branding block to the same hub.yaml file that configures your server providers, auth, and model keys:

yaml
url: https://claw.example.com
public_url: https://claw.example.com
token: ${ELASTICCLAW_TOKEN}
claw_token: ${ELASTICCLAW_CLAW_TOKEN}

branding:
  app_name: Acme Agent Hub
  logo_url: https://assets.example.com/acme-agent-logo.png

app_name replaces the default ElasticClaw label in the browser title and web UI navigation.

logo_url should point to an externally hosted image that the browser can load. It replaces the default ElasticClaw mascot in the conversation empty state.

Apply changes

After changing hub.yaml, restart ElasticClaw Server so it reloads the file. For a server installed with the ElasticClaw installer, restart the service on the host:

bash
sudo systemctl restart elasticclaw

Then reload the web UI. The browser may keep the previous branding for the current page lifetime, so a normal page refresh is enough after the server restarts.

Image guidance

  • Use an HTTPS URL that is reachable by users' browsers.
  • Use PNG, SVG, or WebP for predictable browser rendering.
  • Prefer a square or near-square image with transparent background.
  • Keep the file small enough to load quickly on the login page.
The server stores the logo URL, not the image bytes. Host the image in your own static asset bucket, CDN, or application asset host.