Branding

SeeKi has an opinion about branding: it should be quiet. The operator opens the app to look at data, not to admire a logo. So the product gives you exactly two knobs — a title and a subtitle — and puts them in exactly one place: the wordmark in the topbar.

The two fields

The setup wizard collects these on step 3. They live in seeki.toml under [branding] and are loaded once at launch:

[branding]
title    = "Fleet Ops"
subtitle = "My Database"

Where they render

Grid below. The topbar is the only surface that says the customer’s name — the sidebar, toolbar, and grid stay neutral.

Title becomes the word, subtitle becomes the thin right-hand label. The brand mark is auto-derived from the title’s first letter.

What it does not change

Branding intentionally does not touch the colour palette, the fonts, the grid chrome, the status bar, or any semantic colours. Yes/No badges stay green and red; NULL cells stay hatched. This is deliberate — operators trust the visual language to stay constant across deployments.

title = "Fleet Ops"

F Fleet Ops Example Corp

title = "Orders DB"

O Orders DB finance ops

Defaults

If no [branding] block is supplied, the title falls back to SeeKi and the subtitle is omitted. If the wizard is used, its defaults are:

Field	Default	Notes
`title`	`SeeKi`	Rendered as seeKi with the accent on the second syllable when the title is the literal string `SeeKi`. Any other string renders plain.
`subtitle`	empty	If empty, the divider and subtitle label are suppressed entirely — the wordmark sits alone.

Changing it later

Edit the [branding] block in seeki.toml and reload the browser tab. No restart needed; the topbar re-reads on next API handshake. See Config locations for where seeki.toml lives on each platform.

Why no custom colours?

Semantic colour (accent for state, green for yes, red for no, hatched for null) carries meaning across every SeeKi instance. Re-tinting those per customer would make a shared visual vocabulary impossible. The wordmark is the right place for personality; the grid is the wrong place.

Setup wizard — the form that collects these fields.
Config reference — full seeki.toml schema.
Config locations — where the file lives per OS.