Show HN: OpensourceDB Tamper-evident,checksum-backed decision and session replay Zizka-ai released ZizkaDB, an open-source, self-hosted audit trail for AI agents that logs each agent step with a parent_id so teams can trace a tool call or response back to its root cause. The stack ships via a Docker-based quickstart and includes Python and TypeScript SDKs plus integrations for LangChain, CrewAI, LiveKit voice agents, and MCP, with a managed Pro/Team cloud hosted at db.zizka.ai. The operator admin console and VPC deploy remain in the private zizkadb-cloud repository. When your agent misbehaves, see why. Self-hosted audit trail for AI agents — one command or one dashboard click from any step back to root cause. This repository is the open-source self-host stack API, tenant dashboard, SDKs, MCP . Operator admin console and VPC deploy live in private zizkadb-cloud https://github.com/Zizka-ai/zizkadb-cloud — see docs/REPO SPLIT.md https://github.com/ZIZKA-AI-SL/ZizkaDB/blob/main/docs/REPO SPLIT.md . Requires Docker https://docs.docker.com/get-docker/ . First image pull may take 5–10 minutes. curl -fsSL https://raw.githubusercontent.com/Zizka-ai/ZizkaDB/main/scripts/quickstart-remote.sh | bash You should see: tool call · lookup order · ORD-8842 └── llm response · gpt-4o └── user message · Why was my order delayed? Run again anytime: pip install zizkadb-sdk && zizkadb demo git clone https://github.com/Zizka-ai/ZizkaDB.git && cd ZizkaDB bash scripts/setup-local.sh | Service | URL | |---|---| | API | http://localhost:8000 http://localhost:8000 | | Dashboard | http://localhost:3001/login http://localhost:3001/login | | Swagger | http://localhost:8000/swagger http://localhost:8000/swagger | Full guide: DEVELOPMENT.md https://github.com/ZIZKA-AI-SL/ZizkaDB/blob/main/DEVELOPMENT.md · Troubleshooting: wiki/Troubleshooting.md https://github.com/ZIZKA-AI-SL/ZizkaDB/blob/main/wiki/Troubleshooting.md Every agent team asks: Why did it say that? Why did it call that tool? 1. Log agent steps with parent id each step links to the one that caused it . 2. Ask why — terminal: zizkadb why