The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Atlas listing page.
Atlas is the company facts your AI agents can trust: every one carries its source, its date, and the name of the person who approved it. Open source, runs in your VPC.
The hosted service is shut down. I ran Atlas as a hosted service at useatlas.dev until September 2026 and have now turned it off, along with the hosted demo and docs.useatlas.dev. Atlas continues as open source: everything below runs on your own machine or in your own VPC. The docs live in
apps/docs/content.
Point Claude Desktop, Cursor or Continue at a local Atlas with one command. With no datasource configured it uses the bundled NovaMart demo data:
Restart the client and ask it a question about NovaMart's orders. (Claude Code, VS Code and other clients: the same command with --client generic prints a block to paste. On WSL2, write bun x instead of bunx.)
Three kinds of thing live in the Atlas, and every answer says which it is drawing on:
Surveyed outranks Attested wherever they overlap, so a recollection never overwrites the data. Nothing becomes Attested without a person approving it, and there is no setting that turns that off. Contradictions are shown with both claims and both sources; Atlas does not pick a winner. Where nobody has surveyed, the coverage page says so instead of guessing.
bunx @useatlas/mcp init --local against a local Atlas, or bunx @useatlas/mcp init --hosted --api-url <your Atlas> against a self-hosted one with managed auth. MCP guide.This README used to inventory the whole product. Each section now lives on one docs page, in the docs source:
orders.yml — Semantic layerbun create atlas-agent) — Self-host quick start.env.exampleatlas init, atlas diff, and the rest) — CLI referenceAtlas was inspired by Abhi Sivasailam's work on Vercel's internal data agent d0 and the open-source vercel-labs/oss-data-analyst template. The core insight — invest in a rich semantic layer, trust the model, and keep the tool surface minimal — came from that work.
The server and core packages are AGPL-3.0: if you modify the server and serve it to users, you share those modifications. The client libraries (@useatlas/sdk, @useatlas/react, @useatlas/types, @useatlas/plugin-sdk, @useatlas/mcp) and all plugins are MIT. The ee/ directory is source-available under a commercial license; nothing that makes the Atlas work is behind it — only governance, convenience and scale. Full inventory: Enterprise boundary.