Settings

Everything on this page lives in Settings in the dashboard. This page walks through each card in the order it appears, says what it is for, and tells you what to type or pick.

One Save button. The button at the top right, Save Changes, writes everything on this page. Most cards have no Save of their own. If a value looks like it did not stick, press Save first.

Runtime Storage

Shows where your data lives and lets you move it in and out.

Two buttons:

• Download Backup — saves your dashboard data as a .json file. You will be asked for your password first.
• Import Backup — restores from that file. Accepts .json or .zip.

A backup is a copy of your dashboard data, not a byte-for-byte copy of the live database file. It restores your settings, connections, and keys — it is not a substitute for backing up the SQLite file itself. See Database.

Security & Password

Who can open the dashboard, and for how long.

The default password on a fresh install is 123456. Change it before exposing the dashboard to anything but your own machine.

Single Sign-On (SSO)

Replaces the password login with your organisation's identity provider.

The login button text is set by the mode you pick, so a user sees "Sign in with OIDC" or "Sign in with SAML SSO" rather than a password field.

Default Routing Strategy

How the gateway chooses between your connections when you have not set up a combo. See Architecture for the details.

Connection Fallback Strategy

If you pick Sticky Round-Robin, one more field appears: Sticky Request Limit — how many requests go to the same connection before rotating (1–100).

Combo Routing Mode

Force Fallback

When every account of a provider is cooling down, send the request through whichever account frees up first instead of failing outright. Upstream can still reject it — this buys a chance, not a guarantee.

Observability & Storage Retention

Controls what the gateway records about your traffic, and for how long. Turning recording off entirely is the Zero-Trace / Headless option.

Observability

Storage numbers

Four figures, read live:

If the numbers show —, the stats read failed — the card says so and offers a Retry button rather than hiding the actions.

Three buttons

Pruning usage history is permanent, but it is not lossy for your budgets: the tokens are carried over into per-key budgets, so a key that already spent its quota is not given a fresh one by the cleanup. The confirmation tells you how many tokens will be carried.

Global System Prompt & Anti-Poisoning

Instructions added to every request, regardless of which model or combo serves it. This is the broadest of the three prompt-injection surfaces — the other two are Persona (per model) and Token Saver (style only).

It applies to OpenAI Chat, Claude Messages, and Responses bodies alike.

This applies to every request, with no way to pick models. If you only need it on some models, use Persona instead — that one binds a prompt to the models you choose.

Which to use for what: put identity rules in the prefix — who the assistant is, what it must never claim. Put non-negotiable constraints in the suffix, because the suffix is the last thing the model reads before your content, and later instructions tend to outweigh earlier ones.

Load Anti-Poisoning Preset fills the prefix with a rule that forbids the model from renaming or aliasing provider names — useful if you have seen a model write opencode-go as opencode in code or docs.

White-label branding

Rename the product for anyone you share the dashboard with.

Uploading means an operator with no public web host still gets a branded sidebar — the image is served by the gateway itself.

Display

How the dashboard looks. These are your preferences, and they apply immediately.

Currency

Every cost is measured in USD and shown in the currency you choose here.

The line under the grid shows the current rate for your selected currency, so you can see what you are about to save before saving it.

Sidebar

Folded behind Advanced settings. Decides which entries appear in the sidebar and in what order.

Presets

A preset fills the visibility switches and leaves the arrangement alone — because "what is on the sidebar" and "in which order" are two different questions.

Arranging entries

Each row has a drag handle and two arrows. Drag a row onto another to place it above or below; the arrows do the same thing from the keyboard.

A row dropped into a different container is refused rather than misplaced: a media sub-entry has no place among the main entries, so the arrangement comes back unchanged.

Reset order puts every entry back to the order this build declares.

Settings can never be hidden — the panel you are reading lives behind it.

Usage dashboard

Folded behind Advanced settings, next to the Sidebar card. Controls which panels appear on the Usage page and in what order, per section — Overview, Details, Cache Analytics, and Compression Analytics each have their own list.

Same controls as the Sidebar: presets, per-panel switches, drag or arrows to reorder. One Save covers both cards.

Failover Health Cache Reset

Also on the Settings page, below the main grid. When a provider's credential hit a 429 and was placed in cooldown, this clears the lockout without waiting for the timer.

1. Pick the provider from the dropdown.
2. Click Reset Cooldown.

Use this when a provider has recovered but the gateway is still holding the account out. It does not touch the provider's own state — only what this gateway remembers.

Model Health

The last card. Shows what the automatic model-health loop found, and lets you re-enable a model it disabled. See Usage & Analytics for how the loop decides.