Two ways to run ZizkaDB
Explore the dashboard your team gets — self-host the OSS stack or use managed cloud with Fleet.
Docker Compose on your infra. Activity, Behavior, Reports, and Suggestions out of the box.
Why ZizkaDB
Production agents need operational data — not just logs. ZizkaDB monitors behavior so your team can correct it.
Same incident. Without ZizkaDB you guess. With it you see the exact decision trail.
For teams building with agents
Log from Python, TypeScript, MCP, or REST. One API key per agent — no heavy infra project.
Python SDK, TypeScript SDK, MCP, or REST. Self-host with Docker or use managed cloud.
Prompt change broke behavior? Replay the full session, trace the decision chain, find root cause.
Single-tenant VPC deployment with Fleet dashboard, workshops, and dedicated support.
Trust and security
Pricing
Full monitoring and session replay on every plan.
Compare
Vector DBs store embeddings. Traces show spans. ZizkaDB stores agent decisions, lineage, and drift.
| Capability | LangSmith | Mem0 | Pinecone | ZizkaDB |
|---|---|---|---|---|
| Agent event logging | ✓ | ✗ | ✗ | ✓ |
| Causal lineage | ~ | ✗ | ✗ | ✓ |
| Time travel (state at T) | ✗ | ✗ | ✗ | ✓ |
| Semantic search on history | ✗ | ✓ | ✓ | ✓ |
| Behavioral baseline / drift | ✗ | ✗ | ✗ | ✓ |
| Cross-agent fleet queries | ✗ | ✗ | ✗ | ✓ |
| Self-host free | ✓ | ✓ | ✗ | ✓ |
~ = partial support. Verify competitor docs before external debates.