Dashboard overview

The web UI for your workspace: what each page is for

The Levers AI Lab dashboard is at levers9-app.uselevers.com. Sign in with your Google account: the first person from a company domain gets a fresh workspace, and colleagues with the same domain land in it. It works on a phone as well as a desktop; on small screens the navigation is behind the menu button in the top bar.

The navigation stays in place while a page scrolls. A section heading (Data lab, Compute lab, Storage lab, Settings) folds that section’s links away: the fold is remembered in your browser, and the page you are on stays listed.

The pages

section	page	what it is for
Data Lab	Datasets	import, pre-label, annotate and share datasets
Data Lab	Notebooks	JupyterLab on the cluster, with a native notebook editor
Data Lab	RL Arena	listen to calls, teach the agent, ship a better version
Compute Lab	Apps	your functions and deployments, their calls, logs and timelines
Compute Lab	Endpoints	open-weights models served with vLLM from a catalog
Compute Lab	Containers	what is running now, with live output
Compute Lab	Workers	the worker processes on each node and their load
Storage Lab	Storage	volumes with a file browser
Settings	Secrets	API keys injected into containers

The RL Arena and its Engines and Decide pages are listed only in a workspace that has the Arena. In any other workspace they’re left out of the sidebar, and opening one says which workspace to switch to.

The top bar

• Workspace / environment on the left is a menu: switch workspace, switch or create an environment, invite members. See Workspaces and environments.
• Live containers · active tasks counts what is running this second.
• Workspace metrics opens CPU, memory and GPU in use across all workers, with 24 hours of history.
• The Live badge shows the event stream is connected; Reconnecting means the dashboard lost it and is retrying.
• CLI x.y.z → a.b.c appears when a CLI that used this workspace is older than the current release. Every SDK call names its version and the controlplane remembers the last one per token; the pill carries the upgrade command. A job’s page also shows which SDK made each run.
• Your account, and sign out.

What is live

The dashboard API follows the controlplane’s REST and gRPC APIs every two seconds and pushes one snapshot to every open tab over server-sent events, so counts, container lists and sparklines move without a refresh. Container output streams directly from the container while it runs and is kept in a log spool afterwards, so a finished task still shows its logs. Metrics are recorded per minute for 24 hours.

Stories

Each page has a two-minute picture book behind it: what the thing is, the problem it came from, and the button that does it. The first time you open a page that has one, it pops up; skip it or read it and it does not come back. Stories in the top bar lists all sixteen and opens any of them again, and “Forget which ones I’ve seen” makes them all new.

pops up at	story
first sign-in	the founding story: the data owner, the people who use it, and the system
Workers	what a GPU is: cards, workers, pools, and why a job waits
Apps	how a job runs: the decorator, the task, .map()
a job asking for several cards	one card, many cards, many runs (and what DDP is)
Endpoints, Containers, Storage, Secrets, Notebooks	one each
Datasets	the whole pipeline: import, diarisation, pre-labelling, anonymization, annotation, sharing
RL Arena	the seven missions, calls in to champion
Insights, Clusters, Agents, the workspace menu, the first levers9 login	one each

Your choices are remembered in the browser and on your member record, so a new browser inherits them. Three of the stories are also on the landing page.

Running it yourself

The dashboard is two services: a FastAPI backend that wraps the controlplane’s APIs, and a Next.js frontend.

cd dashboard/api && uv run uvicorn app.main:app --port 8100     # reads ~/.levers9/config for the token
cd dashboard/web && npm run dev                                 # http://localhost:3000

Sign-in settings for the backend are on Sign-in. On EKS both services run from deploy/eks/dashboard.yaml behind the same load balancer as the controlplane.