See what your agent actually reads.
Pick a task below and watch the same job run twice: once by an agent reading your files, once by the same agent asking Archis. The token count on each side is the whole argument.
Everything on this page runs in your browser. Nothing is uploaded, no repository is read, and no API is called — which is the same promise the product makes, honoured by the page that makes it. Check the product's claims yourself →
One task, two agents
Archis serves context in escalating levels: facts about your code first, then compact views of the relevant symbols inside a budget you set, and exact source only when the job genuinely needs it. Turn the budget down and you can watch the trade-off appear.
Same task, two agents
Left: an agent reading files. Right: the same agent asking through Archis under a budget you set. Illustrative step costs; the measured corpus result is quoted underneath.
Running…
Measured: across 20 paired tasks per repository on 20 real repositories in 8 languages, the full policy shows the agent 89.4% to 95.0% less context than a full-source agent doing the same task, 92.0% on average. That is context shown, not the bill. In real Claude Code sessions, where the agent also pays for its reasoning and its answer, the saving is smaller: 22% of tokens in a typical session.
Want to see more?
Three more interactive examples: the full call path from question to answer, what it costs to index a real repository, and exactly what crosses the boundary between your machine and us.
Everything semantic stays on your machine
Indexing, retrieval and the dashboard are local. Only the commercial side — sign-in, billing, licence issuance, update checks — talks to us. That split is not a preference; it is the product's central claim, and it holds because there is no endpoint that could receive source code.
Verified offline, every time
The licence is a signed payload the CLI checks locally on every protected command. Every deadline inside it is clamped to when access actually ends, so an offline grace window can never outlive the subscription that granted it.
Leaks made unrepresentable
Telemetry is opt-in and off until you enable it. Paths, symbols, queries and error text cannot be attached to an event even by mistake, and numbers travel only as coarse buckets. The server validates against its own allowlist regardless.
The honest consequence
Because indexing is local, we cannot pre-warm your repository on a fleet of servers or share an index between teammates through us. The first index runs on your hardware. That is the cost of the guarantee, and it is the trade we chose.
Run it on your own repository
chi measure ./src reproduces the reduction on your code in about a minute, on Archis Free.