Skip to content

Dashboard

Thibaut Rey edited this page Sep 7, 2026 · 1 revision

🖥️ Dashboard

The React dashboard is served by the proxy and supports light, dark, and system themes.

Tab Current capabilities
Overview Account/model health, request and token totals, cache-aware and no-cache cost estimates, latency, speed, quota summaries, and exposed models
Accounts Provider onboarding, OAuth/reauthentication, quotas, account priority/location/capacity, unblock/reset actions, and default passthrough selection
Aliases Guided redirect/fallback/local-cloud policies, advanced schema-v2 editing, simulation, live capacity inspection, and image-model override
API keys Dynamic application keys, deferred-job fairness weights, and signed result webhooks
Tracing Paginated requests, payload diagnostics, project attribution, cost/token/latency views, time ranges, and ZIP export
Plugins Install, pin, enable, update, disable, and remove trusted lifecycle modules
API reference Endpoint documentation, generated examples, model selection, and a live request console
Current dashboard previews — Activity and API workspace

Captured from the current UI on September 7, 2026, using the fictional demo dataset.

Activity — performance

Current Activity dashboard with fictional latency measurements

API workspace

Current API workspace connected to the local demo API

Try the current UI with sample data

Run a separate, read-only demo instance of the current dashboard:

npm --prefix web ci
npm run demo

Open http://localhost:4173. The demo includes fictional provider accounts, quota windows, model policies, application keys, and two weeks of request activity. Filters, time ranges, pagination, and trace details work with the sample data. A visible Demo data label distinguishes it from a live installation.

The demo serves mock API responses inside the Vite development server. It needs no provider credentials, does not start the gateway or discover real runtimes, and does not read or write account storage. Provider connections, configuration changes, exports, and inference calls are unavailable. Refreshing preserves the fixture set; restarting generates its timestamps relative to the new start time. Normal development and production builds do not enable the mock API.

See the demo guide for screenshot instructions.

Clone this wiki locally