Skip to main content

Dashboard — Getting Started

Get the governance dashboard running locally. Prerequisites to deployment: about 5 minutes.

Prerequisites

No Docker, no cloud accounts, no external services required.

Install

Option 1: From the TealTiger Monorepo

If you already have the TealTiger repository cloned:

Option 2: Standalone Clone


Database Setup

The dashboard uses SQLite — no database server needed. The database file is created automatically on first API startup. Location: dashboard/api/dashboard.db

Seed Demo Data (Optional)

To populate the dashboard with sample data for evaluation:
This creates:
  • 5 sample agents (researcher, writer, reviewer, coder, operator)
  • 200+ governance decisions across the agents
  • Cost records with realistic token counts
  • Module evaluations with various findings
  • Sample TEEC evidence envelopes

Run

Start both the API and frontend in separate terminal windows:

Terminal 1: API Server

The API starts at http://localhost:3001 with:
  • REST endpoints at /api/v1/
  • WebSocket for real-time updates
  • SQLite database at ./dashboard.db

Terminal 2: Frontend

The frontend starts at http://localhost:3000.

Access

Open your browser to:
You’ll see the Overview panel with:
  • Active agents count
  • Total cost (24h)
  • Decision breakdown
  • Recent event stream
If you seeded demo data, these panels will be populated. Otherwise, they’ll show zero state until your application starts writing governance events.

Connecting Your Application

The dashboard reads from the same SQLite database that TealTiger writes to. To connect your application:

1. Configure TealTiger to write to the dashboard DB

2. Events appear in real-time

Once your application makes requests through the governed client, events appear in the dashboard via WebSocket — no refresh needed.

Configuration

API Configuration

Create dashboard/api/.env (optional):

Frontend Configuration

Create dashboard/web/.env.local (optional):

Production Deployment

For production use, build and serve statically:
Or use a process manager like PM2:

Troubleshooting


Next Steps