Give every developer's Claude Code or Cursor an index of your company's repositories, with Archis seats from your identity provider and every Archis administrative change in your SIEM.
Your engineers already want coding agents on the company's code. Archis gives each one an index of your repositories on the developer's machine, Archis seats from your identity provider, and the Archis audit log (seats, members, devices, sign-in settings) streamed to your SIEM. Archis does not see or audit what the agents do, and never receives a line of source. Your agents still send their prompts, and the code they read, to their model provider; Archis cuts how much of it, not where it goes.
Developers sign in through your identity provider, and their agents are set up on clone from defaults committed in the repository. SCIM adds and removes seats, the workspace sets how many devices each member may use and how long a machine works offline, and every administrative change lands in the audit log.
What reaches Archis, and what never does.
Indexing, the graph and every answer your agent gets from Archis are computed on the developer's machine. Archis's servers handle licensing and team administration, and no endpoint accepts source. With federation, the registry and the CAVS DB Server are yours as well: repository names, server addresses and whatever you publish to the server never reach Archis.
What crosses, and what cannot
Everything semantic happens on your machine; everything commercial happens in the cloud. The third packet is the one worth watching.
Press play to trace what actually crosses the boundary.
Every request the CLI makes, and what each one sends →
What never reaches Archis:
- Raw source code, Git commit history, and diffs
- Local Tree-sitter AST nodes & symbol declaration tables
- Local SQLite call graphs, blast radius maps & test logs
- Developer prompts, MCP tool queries & agent interactions
- Repository names and URLs, and what your CAVS DB Server holds
Your coding agent still sends its prompts, and the code it chooses to read, to its model provider. Archis reduces how much of your repository that is; it does not change where it goes.
What connects to Archis cloud:
- Cryptographically signed Ed25519 offline seat leases
- SAML 2.0 SSO identity tokens (Okta, Azure AD, Google)
- Optional aggregate telemetry metrics (coarse counts only)
- SIEM audit event forwarder (e.g. seat activation, policy change)
- Your CAVS DB Server's licence check, when its network allows one
What Enterprise adds, and where each part is documented.
Identity for IT, your repositories as one system on a server you run, a licence that keeps working when the network or the contract does not, and an audit trail for your SOC.
SAML SSO, SCIM and Domain Capture
Sign-in follows your SAML or OIDC identity provider, and seats follow Okta or Microsoft Entra ID over SCIM.
- Single sign-on: SAML or OIDC through your identity provider, and it can be required: a session signed in any other way is refused.
- SCIM 2.0 provisioning: Tested with Okta and Microsoft Entra ID. Deactivating someone releases their seat and revokes their devices and sign-in tokens. A laptop that stays offline keeps its current lease until it runs out: at most four days, less if you shorten the offline grace. A sign-in to your CAVS DB Server lasts seven days and Archis cannot revoke it, so a removed member keeps reading what the server holds until it expires, unless you run cavsdb-server user block.
- Domain capture: Prove your domain with a DNS record, and anyone signing in under it joins your workspace instead of starting their own.
- Devices and machine tokens: Revoke a lost laptop from the portal and restore it later. CI runners, Codespaces and containers get their own expiring tokens.
Your Repositories as One System, on Your Server
Register your repositories once and work across them as one, on a CAVS DB Server you run on your own infrastructure.
- Federation: A workspace pins every repository to an exact state, and a lock file reproduces that state on another machine. A feature is followed across repositories through squash merges and rebases, and
chi repo impactlists who consumes a repository. - Self-hosted CAVS DB Server: Download it for Linux or Windows and generate its licence in the portal. It checks the licence without a network connection, members sign in with their Archis account, and the rules for who reaches what stay on the server.
- Releases, environments and incidents: A release is a locked composition; an environment can require approvals before it takes one.
chi env diffcompares two environments across every repository, andchi env replayshows what was live at the moment of an incident and what changed since the deployment before. - Retention holds and compliance exports: A hold keeps a state from being collected until it is lifted.
chi registry exportwrites a deterministic compliance export to a file, andchi registry verify-exportchecks it. - What the server holds: Each repository’s ledger (paths, hashes and commits) and the compositions built on it. How much source goes with it is your choice per repository: in
metadatamode a member with no checkout lists paths and never reads bytes, reported aswithout_content;hybrid, the default, andfullpublish file content so it can be searched without a checkout. None of it reaches Archis.
A Licence That Keeps Working
What keeps working when the network, the server licence or the subscription goes away.
- Offline: A signed lease keeps licensed commands working for up to four days without a connection: valid for 24 hours, then a 72-hour grace.
- Air-gapped: Enterprise issues an offline licence file, signed for the machine and valid for a set period. It cannot be revoked, so it runs until it expires.
- Server read-only, never deleted: An expired or revoked server licence makes the CAVS DB Server read-only: reads, compositions and locks keep working, publishing stops, and nothing is deleted.
- When a subscription ends: Local indexes stay on every machine and the account drops to Free. The commands that clean up federation (
chi repo remove,chi workspace gc,evictandlift,chi registry tenant --clear) still run without a licence.
SIEM Streaming & Audit Logging
Every administrative action, streamed to your SIEM.
- SIEM streaming: Each audit event is posted as JSON to Splunk HEC, Datadog, or any collector that accepts it over HTTPS.
- Append-only audit log: Seats, members, devices, SSO, SCIM, domain and server-licence changes, with who made them and CSV export.
- What your agents read stays on the machine: Query history is kept on each developer’s machine and never sent to Archis. Archis cannot tell you what your agents read, so nobody can get it from Archis either.
- Usage dashboard: Organization-wide counts from developers who opted in to telemetry. Every figure is a floor.
Enterprise Agreements & Direct Support
Direct onboarding from the people who build the engine, and commercial terms your procurement team expects.
- Founder-led architecture review: Technical consultation and deployment guidance with the core team.
- Direct engineering support: Answered by the engineers who build Archis. No response-time SLA is offered yet.
- DPA on request: Our data processing agreement is in counsel review; ask for the current draft.
- Annual invoicing and PO terms: Corporate procurement via ACH, wire transfer, or Net 30 terms.
Calculate your engineering organization's annual token ROI.
Coding agents spend much of each session re-reading files. In our latest benchmark, Archis cut the tokens of a typical Claude Code session by 22%, and by 50.6% on tasks both runs solved. The calculator applies that to the part of your bill that is repository work.
Assumes 50% of the agent bill is repository work, and that a typical session there uses 22% fewer tokens (51% on tasks both arms solved): the per-session token saving measured with Claude Code on Sonnet 5 (Archis after 0.49.0, 20 paired sessions, Oct 2026) — an early measurement, priced at the average token. Seat price is an estimate; your contract sets the real one. A pilot measures it on your repositories. How this was measured →
Start a 14-day pilot on your own repositories.
A pilot is a governed rollout of the agents your engineers already want, on your own repositories. Meet the founding engineering team to arrange the security review, connect your identity provider, and agree what the pilot measures.
What happens next:
- 30-Minute Architecture Review: Your coding agents, your repositories, and your identity requirements, directly with the founders.
- 14-day pilot: A group of your engineers work with and without Archis, and the pilot measures the tokens of each session. Reporting pull requests returned for rework, reverts and review minutes is in development.
- With several repositories: A second track on your CAVS DB Server: register the repositories, compose a workspace, lock it on two machines, and replay an incident.
- Security & Procurement Package: Our data processing agreement on request (in counsel review), security questionnaire answers, and annual invoice onboarding.
Frequently asked enterprise & InfoSec questions.
Where is our source code stored and processed?
Nowhere on Archis infrastructure. All source code parsing, Tree-sitter AST compilation, and SQLite knowledge graph queries execute strictly on the developer’s local laptop or within your private CI runners. Archis cloud servers only handle licence verification and team administration.
Do you use our source code to train AI models?
Never. Archis is a local semantic context compiler, not an LLM vendor. There is literally no backend endpoint designed to receive source code or AST tokens.
Does Archis handle large monorepos?
Indexing runs on each machine: angular’s 10,513 files index in about 18 seconds on one laptop, and afterwards only changed files are re-indexed. A shared, pre-built index for very large monorepos is not shipped, and the CAVS DB Server does not provide one: it holds ledgers and compositions, so it scopes an agent to the repositories a change touches rather than shortening the first index. Tell us your repository size and we will say where it stands.
What happens if an employee is terminated or a laptop is lost?
Deactivating someone in your identity provider reaches Archis over SCIM 2.0: their seat is released and their devices and sign-in tokens are revoked. An admin can also revoke a device from the portal. A laptop that stays offline keeps its current lease until it runs out, at most four days, or less if you shorten the workspace’s offline grace. An offline licence file cannot be revoked and runs until it expires. On your CAVS DB Server, a sign-in lasts seven days and Archis cannot revoke it: a removed member can keep reading what the server holds until it expires, unless you run cavsdb-server user block, which refuses them at once. What their machine already fetched stays on it, like a clone.
Can Archis operate in air-gapped, VPN, or zero-connectivity environments?
Offline, yes: a signed lease keeps licensed commands working for up to four days without a connection (valid for 24 hours, then a 72-hour grace), and local data is never deleted when it runs out. For networks that never connect, Enterprise issues an offline licence file, signed for the machine and valid for a set period.
Does the CAVS DB Server see our source code?
It is your server, on your infrastructure, and nothing on it reaches Archis. It always holds each repository’s ledger (paths, hashes, commits) and the compositions over them. Whether file content goes with it is set per repository: in metadata mode a member without a checkout lists paths and never reads bytes; hybrid, the default, publishes text files up to 1 MiB and full publishes every file, so members without a checkout can search them.
What happens if our licence or subscription lapses?
Nothing on your machines is deleted. The account drops to Free, local indexes stay, and the commands that clean up federation still run. A CAVS DB Server whose licence expires or is revoked turns read-only: reads, compositions and locks keep working, and publishing stops until it is renewed.
How does enterprise invoicing and procurement work?
Annual contract billing with corporate invoice terms (Net 30, ACH or wire transfer). Our data processing agreement is in counsel review, and we send the current draft on request. There is no response-time SLA yet.
Roll out coding agents on your company's code with the controls already in place.
Start with a pilot on your own repositories. Today it measures tokens per session; rework and review time are in development.