Skip to content

Stardeck

Stardeck is the Next.js customer dashboard — the "ship's command deck." It ships from starform/stardeck and runs in the infra cluster (or a CDN). Mission Control is the bird's-eye observability view inside Stardeck.

A deliberately thin tab

The PRD has no dedicated Stardeck section — it appears as cross-references from the component map (§1), the binaries table (§3), label consumers (§24), RBAC UI implications (§15.9), and the dashboard reads in the observability pipeline (§35). This page gathers those threads; it will grow into Mission Control and UI/RBAC sub-pages as the frontend is documented in depth.

What Stardeck renders

  • Logs — runtime logs with live tail (ClickHouse), scoped per-tenant; build logs relay live from the build stream and replay from the DO Spaces archive (§16.6).
  • The seven customer metrics — latency, RPS, throughput, error rate, CPU, memory, network — read from the regional ClickHouse via the Starbase telemetry-query broker (SQL over request rows
  • cAdvisor meters, v2 Read & query). Every query is scoped by a server-side tenant filter the client cannot override (FR-065), so one tenant's dashboard can never read another's rows. Worker/cron services show CPU · memory · network only (no L7 request source); default windows are 1h / 24h / 7d with a p50/p95/p99 toggle on latency (§39.1 #13).
  • Service controls — the starform.io/service-type label (web / worker / cron) tells the UI which icon and controls to render (§24.2). At create the UI picks web / worker / cron; a web service adds a Public / Private toggle (public) — visibility is a sub-choice of web, not a peer type (Services › Networking).
  • Autoscaling controls — enable + Min / Max replicas + Target CPU % (target memory % is an advanced field); CPU-based at MVP, not request/traffic-based (that needs the deferred adapter, §39.1 #9). The replicas control is hidden while autoscaling is on — the HPA owns it (§20.3).
  • Connect panel — each service's env page shows its internal address http://<service-name>-<environment>:<port> (public web also shows the public URL; workers/cron show none) plus a Connections control to link services so their URLs auto-inject (Services › Networking).

Mission Control

The bird's-eye view across a workspace's projects and environments — health, deploys, and the metric rollups above. What each role sees is governed by the two-tier RBAC model (§15.9): Owner/Admin/Billing/Member at the workspace, Admin/Developer/Viewer at the project.

What each role sees

How the two-tier RBAC model gates each UI surface — the Projects view, Mission Control (lock icons on protected environments, the deferred "Request Admin approval" CTA), and Workspace/Project Settings — is owned by RBAC › §15.9 UI Implications. Stardeck renders those role gates; it does not redefine them.

Cross-references

The two-tier RBAC model and permission helpers → §15 · the seven customer metrics it displays → v2 Read & query · the server-side tenant filter → v2 Read & query / FR-065 · the service-type label that drives UI controls → §24.2. Canonical map: Canonical Sources.