daari
Open-source local execution router — run cheaply on your machine, not in the cloud.
Status: v1.2.0 Learning, Trust & Clients — tracker · validation · release notes
Route dev agent work through local tiers (cache → IDE tools → local AI) instead of frontier APIs. Not a proxy — a cost optimizer you own.
Quick start
Full pickup guide (clone, venv, smoke test, pytest): docs/DEVELOPING.md
One-click demo (install, serve, smoke curl, stats):
./scripts/demo.sh
Manual steps:
python3.12 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
ollama pull llama3.2:3b
daari serve
curl http://127.0.0.1:11435/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{"model":"llama3.2:3b","messages":[{"role":"user","content":"Say hi"}]}'
Run the same curl twice — the second response should show "tier": "L0" in daari_meta.
Feature snapshot (v1.1.0)
- Local-first routing chain with cache/rules/tooling/model tiers (
L0,L1,CCS,L2,Lt,L3-L6) - OpenAI-compatible and Anthropic-compatible gateways with SSE streaming support
- MCP ingress with
tools/list+tools/call, schema-aware input validation, and structured errors - C3 integration providers: Sourcegraph, GitHub Enterprise, and GitLab self-hosted trigger routing
- Enterprise E1/E2/E3 runtime: org mode, shared-cache service, learning feedback/profile APIs, CLI stats/export
- Local stats dashboard:
daari web-ui serve(packages/web-ui/) - Setup and health tooling:
daari setup ...,daari doctor,daari install, demo + bench scripts
Docs
| Doc | Purpose |
|---|---|
docs/ARCHITECTURE.md |
Repo layout, request flow, implementation map |
docs/TRACKING.md |
Phase task tracker (A / A.1 / deferred) |
docs/DEVELOPING.md |
Dev pickup — clone, run, test |
docs/plans/phase-a.md |
Phase A implementation plan |
docs/prd/PRD.md |
Product requirements |
docs/setup/cursor.md |
Manual Cursor setup |
CONTEXT.md |
Agent handoff |
Principles
- Open source — Apache 2.0, you own the stack
- Local-first — on-device by default
- Cost-minimize — cheapest capable path for every task
- AI optional — many tasks use IDE/CLI tools, not models
Repo
1 maintainer
Metadata
1 maintainer
Release files for daari 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| daari-1.2.0.tar.gz | 324.2 kB | With provenance | Details for daari-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| daari-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for daari-1.2.0-py3-none-any.whl |
Total release size: 461.5 kB
Release files / daari-1.2.0.tar.gz
| Download URL | daari-1.2.0.tar.gz |
|---|---|
| Size | 324.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4799cf976e6fa2cf6500ba280a20a3bc8af32941537cd8ad7549b93564155400
|
|
BLAKE2b-256 checksum How to use checksums |
a6a9056619882e8c7131c94dba69ac012b3fde328346588ad48fe046c598f898
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logRelease files / daari-1.2.0-py3-none-any.whl
| Download URL | daari-1.2.0-py3-none-any.whl |
|---|---|
| Size | 137.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d6cf8b523a3426e4070ca474b4a9094ffe0c83b1194a116e716e39c4b3c9c20
|
|
BLAKE2b-256 checksum How to use checksums |
4e3764222a664746a6346ec53cada0765abce830cc4c4a0d6c3d8f98916e08e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logSecurity for daari 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for daari-1.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
