Server and Client Boundaries in AITracer
How the dashboard separates local agent UI from server-side trace storage.

Agent Lab pages (run, chat, coach, training) are mostly client-driven: they call /api/local/* and /api/coach/* and show results immediately.
Trace persistence, auth, and ingest APIs stay on the server.
Server responsibilities
- session auth and API keys
- writing traces to Postgres (
/api/local/run,/api/traces, coach ingest) - optional policy evaluation and verification on ingest (advanced)
Client responsibilities
- Ollama model picker, prompts, coach comparison UI
- training export downloads and model build actions
Keeping inference on your Ollama instance (or your provider keys for coach) means the server stores records — it does not run your models for you unless you configure cloud provider execution separately.
More Articles
When you need an audit trail beyond traces
Advanced governance and audit workflows for production AI ingest — optional beyond Agent Lab.
January 2, 2026
Deploying AITracer for Production Workloads
A practical deployment checklist for self-hosted AITracer with Agent Lab and optional API ingest.
January 5, 2026