Cube Sandbox

English

简体中文

English

简体中文

Appearance

WebUI Dashboard ​

The Cube Sandbox Dashboard is a built-in web console that lets you see what's running, manage sandboxes, build templates, and inspect cluster health — all from your browser, no CLI required.

⏱ Takes ~3 minutes to read. After that you can drive a cluster from a laptop.

1. Where do I open it? ​

The Dashboard is a static frontend served by an nginx container on the control node.

ScenarioURLNotes
One-click / multi-node deployhttp://<control-node-ip>:12088Default port, change via WEB_UI_HOST_PORT
Bare-metal deployhttp://<server-ip>:12088Same port
Local developmenthttp://localhost:5173Vite dev server, proxies /cubeapi to 127.0.0.1:3000

Port 12088 vs CubeOps :3010

Port 12088 is the human-facing Dashboard (nginx). Behind it, CubeOps (the ops/admin service) listens on :3010. The Dashboard talks to CubeOps under two same-origin prefixes:

  • /opsapi/* → CubeOps /api/* (admin endpoints, restricted to localhost and Docker bridge networks)
  • /cubeapi/v1/* → CubeOps /api/v1/sdk/* (E2B-compatible SDK endpoints, JWT-authenticated, public)

You only ever need to open 12088 from your browser. Do not expose :3010 directly to the public internet.

If you don't know your control-node IP, run ip -4 addr on the server, or check http://<hostname>:12088 on the same LAN.

2. The sidebar at a glance ​

Everything lives behind the 11 icons in the left rail. Hover any icon to see its name.

#IconPageWhat it's for
1📊OverviewCluster KPIs: running sandboxes, CPU/memory usage, healthy nodes
2📦SandboxesLive list of every micro-VM, with pause / resume / kill actions
3🧩TemplatesCatalog of reusable sandbox snapshots; create new ones from OCI images
4🖥️NodesFleet health: per-host CPU, memory, slot capacity
5🧬VersionsComponent version matrix across nodes (kernel, agent, guest image)
6🌐NetworkAPI gateway config and per-node rate limits
7📈ObservabilityRuntime status, sandbox health, template build overview
8🔑API KeysSDK API key management (JWT-based since v0.6.0)
9🏪Template StoreInstall official preset images to bootstrap templates
10🤖AgentHubRecruit and manage AI agent instances running on Cube Sandbox
11⚙️SettingsTheme, language, cluster info, keyboard shortcuts

New user? Start with Overview.

It shows everything important in one screen and refreshes automatically.

3. Three things you'll do first ​

3.1 Check that the cluster is healthy ​

Open Overview (/). You should see four green-ish KPI cards:

  • Running Sandboxes — how many micro-VMs are live
  • CPU / Memory Utilization — cluster-wide pressure
  • Healthy Nodes — N/M nodes reporting Ready

If any number is red, click into Nodes to see which host is unhappy.

3.2 Create a sandbox ​

  1. Click Sandboxes in the left rail, then + New sandbox (top-right).
  2. Pick a template from the grid. Prefer a READY template. A STALE badge only means the node's current component versions differ from those recorded on the template — creation is still allowed; make sure the node already has the component versions the template needs.
  3. (Optional) Add a few meta key/value pairs as labels.
  4. Click Create. Within a couple of seconds you'll be redirected to the sandbox's detail page, where you can watch its logs stream in real time.

To stop a sandbox, go to Sandboxes, find the row, and click the pause / kill button on the right.

3.3 Log in (JWT authentication) ​

The Dashboard uses JWT-based authentication (since v0.6.0, replacing the old X-API-Key scheme). On first visit you'll be redirected to the login page.

  1. Enter your credentials. The default All-in-One account is admin / admin — change this immediately in production via Settings → Change Password.
  2. On success you receive an access token (short-lived) and a refresh token (7 days). Tokens are stored in localStorage and sent as Authorization: Bearer <jwt>.
  3. The admin endpoints (/opsapi/*) are restricted to localhost and Docker bridge networks at the nginx layer, so even with weak default credentials they are not reachable from the public internet. SDK endpoints (/cubeapi/v1/*) require a valid JWT.
Token lifecycle
  • Access token: 15 min TTL, token_type=access, audience cubeops:access.
  • Refresh token: 7 day TTL, token_type=refresh, audience cubeops:refresh. Refresh tokens cannot be used as access tokens (enforced by typ + aud claims).
  • Login is rate-limited: 5 failed attempts per minute per IP.

4. Keyboard shortcuts ​

The Dashboard is keyboard-friendly. The big three:

KeyAction
⌘ K / Ctrl KOpen the Command Palette — type a page name to jump there
?Open Settings → Shortcuts (this list, but in-app)
RRefetch every visible data panel
EscClose any open modal or the Command Palette

5. Personalize it ​

Open Settings in the left rail:

  • Appearance → Theme — Light, Dark, or follow your OS
  • Appearance → Language — English or 简体中文
  • Cluster — Read-only view of the CubeAPI endpoint, sandbox domain, default instance type, rate limit, and whether auth is on

The Command Palette's ⌘K input box and the topbar have quick toggles for the same.

6. FAQ ​

Why a separate Dashboard, not just curl? Most operations (create-from-image, version matrix, node triage) are easier to discover and visualize in a UI. For automation, the Dashboard is just a thin client — every page is a call to /cubeapi/v1/*, which is the same E2B-compatible REST API you can hit with curl or the E2B SDK.

Does the Dashboard store my data? It stores only one thing in your browser: the API key under localStorage.cube.apiKey. All other state (templates, sandboxes, logs) lives on the cluster.

Can I change the port? Yes — set WEB_UI_HOST_PORT in .env before running install.sh. The change applies on next start of cube-sandbox-webui.service.

Can I disable the Dashboard? Yes — set WEB_UI_ENABLE=0 (or unset) in .env. The cluster keeps running; you just won't have the web UI. The E2B-compatible API on port 3000 is unaffected.

Is the Dashboard open source? Can I run my own build? Yes — it lives in web/ of the repo, built with Vite + React + TypeScript + Tailwind. See Self-Build Deployment and the web/README.md for details.

7. Next steps ​