Skip to Content
DashboardDashboard Overview

Dashboard Overview

The Curate-Me Dashboard is the operating surface for the platform. It is where teams onboard a workspace, manage gateway access, review approvals, inspect request logs, monitor runners, and coordinate production AI operations without dropping into raw infrastructure.

Production URL: https://dashboard.curate-me.ai 

What teams use it for

FeatureDescription
Onboarding and setupCreate org context, generate gateway keys, connect provider secrets, and verify traffic is flowing
Gateway operationsInspect request logs, governance denials, approval queues, cost headers, and provider health
Managed runner controlCreate runners, launch sessions, inspect artifacts, follow event streams, and enforce cost or egress controls
Approvals and governanceReview HITL requests, apply model or budget policy, and coordinate cross-functional sign-off
ObservabilityTrack spend, usage, health, anomalies, and activity across the platform from one place
Developer workflowsUse the workflow builder, traces, evaluations, and admin tools when teams want deeper control

Architecture

The dashboard talks to both the B2B API and the gateway surface. It provides the UI for the same systems the docs site describes: gateway governance, runner control plane, approvals, and usage reporting.

Dashboard (port 3001) ──────► B2B API (port 8001) │ │ ├─ JWT Authentication ├─ TenantIsolationMiddleware ├─ X-Org-ID Header ├─ Role-based access control └─ Organization context └─ Per-org data isolation └────────────────────────► Gateway API (port 8002) ├─ Gateway request logs and health ├─ Approval and governance metadata └─ Runner management endpoints

Every API request from the dashboard includes the organization context:

// apps/dashboard/lib/api.ts const headers = { 'Authorization': `Bearer ${token}`, 'X-Org-ID': organizationId, 'Content-Type': 'application/json', };

Core areas

AreaWhat you do there
OverviewSee system health, spend, quick actions, and current platform status
GatewayReview traffic, denials, provider routing, budgets, and logs
ApprovalsApprove or reject high-cost and sensitive requests
RunnersProvision and manage OpenClaw sessions, fleets, files, and compute
SettingsManage API keys, provider secrets, billing, and org configuration
Builder and ops toolsWorkflows, traces, evaluations, debugging, and internal operator tooling

Common operator flow

  1. Connect provider secrets and create a gateway key.
  2. Point an app or agent at the gateway.
  3. Watch live traffic and governance headers in the gateway views.
  4. Triage denials or pending approvals.
  5. Scale into managed runners, fleets, and richer observability as usage grows.

Tech Stack

LayerTechnology
FrameworkNext.js 15 with App Router
UIReact 19, Tailwind CSS
State ManagementZustand (client state), TanStack Query (server state)
Workflow CanvasReact Flow (@xyflow/react)
ChartsRecharts
Real-timeServer-Sent Events (SSE) via EventSource

Getting Started

# Start the dashboard npx turbo dev --filter=dashboard # B2B API cd services/backend poetry run uvicorn src.main_b2b:app --reload --port 8001 # Gateway API poetry run uvicorn src.main_gateway:app --reload --port 8002

The dashboard runs on http://localhost:3001 in development.