A local-first workbench for auditable datasets
Review sample evidence, deliver verifiable versions, and trace business metrics back to their source.
简体中文 · Quick start · Dataset delivery · Guided tour · Documentation · Changelog
Install uv and run these commands from a checkout. The demo starts the API and worker, serves the bundled web UI, and seeds generated samples in local SQLite. Model calls use the bundled offline provider.
uv sync --locked
uv run datakeel demo
# Web UI: http://127.0.0.1:8765
# API docs: http://127.0.0.1:8765/api/docs
# Ctrl+C stops both processes.Start with Evidence to inspect an image alongside its caption and annotations. In Ask data, try “What was retail revenue in East China last quarter?” with the demo reference date 2026-10-01. The guided tour uses the same generated samples. Guided tour
Run the demo and queries from the command line
uv run datakeel demo --once
uv run datakeel ask '上个季度华东区零售额是多少' --reference-instant 2026-10-01T00:00:00Z
uv run datakeel ask '退货率为什么上升' --reference-instant 2026-10-01T00:00:00Z
uv run datakeel ask '上个季度营业额是多少' --reference-instant 2026-10-01T00:00:00Z
uv run datakeel export --format openlineage --output events.json
uv run datakeel export --format croissant --output croissant.jsonThe demo includes four generated collections for file processing, paired image evidence, enterprise metrics, and knowledge graphs. The evidence collection has 1,000 sample images with known annotation conflicts, missing sidecars, and corrupted files.
| Workflow | What you can verify | Guide |
|---|---|---|
| Import and review an image folder | Preview sample and sidecar pairing, inspect images that match across partitions, and exclude a confirmed sample in a corrected version. | Dataset delivery review |
| Review samples | Follow a candidate issue to a caption, annotation, image, or source event. Evidence distinguishes present, absent, and unknown. | Evidence review |
| Prepare training data | Compare immutable versions, inspect split leakage, and export training sets in COCO, YOLO, Hugging Face, or JSONL formats as applicable. | Training sets |
| Deliver a dataset | Sign a frozen release plan, download a reproducible package, and verify its manifest with datakeel reconcile. |
Dataset releases |
| Explain a business metric | Inspect its definition version, source fields, parameterized SQL, and time range. Ask for a breakdown or follow the metric to its lineage. | Ask data |
| Review an Agent proposal | Inspect the affected objects, outbound scope, and cost. The Web UI and CLI handle approval and execution. | Controlled actions · MCP |
The bilingual UI includes a keyboard-driven evidence review panel, global search with ⌘K / Ctrl+K, and a contextual Copilot with ⌘J / Ctrl+J. UI design
For labeling production, audio and video processing, LLM dataset checks, knowledge graphs, and semantic catalog imports, use the documentation hub.
Datakeel runs an API and a fenced worker over SQLite or PostgreSQL and local or S3-compatible storage. File versions have immutable SHA-256 manifests. Lineage rebuilds from append-only events, and external or irreversible actions require a person to approve the exact prepared plan. Architecture · Persistence schema · API reference
The MCP server exposes audited reads and plan preparation. It can run over local stdio or loopback SSE. Use the same DATAKEEL_HOME as the Web UI to work on the same datasets. Controlled actions
MCP client configurations
For a local stdio client such as Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json), replace the absolute paths:
{
"mcpServers": {
"datakeel": {
"command": "/absolute/path/to/uv",
"args": [
"--directory",
"/absolute/path/to/datakeel",
"run",
"datakeel",
"mcp"
],
"env": {
"DATAKEEL_HOME": "/absolute/path/to/datakeel/.datakeel"
}
}
}
}For an isolated loopback SSE server, run uv run datakeel mcp --transport sse --host 127.0.0.1 --port 8766:
{
"mcpServers": {
"datakeel": {
"url": "http://127.0.0.1:8766/sse"
}
}
}Optional real providers use DATAKEEL_OPENAI_API_KEY or DATAKEEL_ANTHROPIC_API_KEY, with optional DATAKEEL_OPENAI_BASE_URL or DATAKEEL_ANTHROPIC_BASE_URL. Keep secrets outside the repository and register provider model prices in the price catalog.
Export sanitized OTLP/HTTP spans to a collector, Phoenix, or Langfuse with uv run datakeel export-traces [--conversation-id <id>]. Trace export reference
GitHub Releases carry the wheel, locked requirements, license notices, and SHA-256 checksums. For a shared installation, use the small-team deployment guide for the authenticated reverse proxy and PostgreSQL options. Release files · Deployment guide · SQLite maintenance
Run separate processes or build local artifacts
uv run datakeel db upgrade
uv run datakeel api --port 8765
# In a second terminal with the same storage and database environment:
uv run datakeel workerA source build uses Python 3.12, uv, Node.js 22, and Rust 1.96. The build commands produce local artifacts.
make build-wheel
make build-image
docker run --rm -p 127.0.0.1:8765:8765 -v datakeel-data:/data datakeel:localAfter building the image, Docker Compose can run the API, worker, migration job, and PostgreSQL on a loopback-only binding.
docker compose up -d
docker compose run --rm api demo --onceRun the repository quality gates
uv sync --locked
(cd web && npm ci)
uv run pre-commit install
make check
uv run python scripts/check_readme.py
bash scripts/ci-check.shCI runs gates, tests, and mutation checks on SQLite and PostgreSQL. For test inputs and guardrails, see Verification and Code standards.
Contributing · Support · Private security reports · Code of conduct · Citation
Datakeel is licensed under Apache-2.0. Dependency and bundled font terms are recorded in Third-party notices and Frontend notices.
