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:
bunx @useatlas/mcp init --local --writeRestart 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 — read straight from your company's own data through a semantic layer you author. True by construction: the query re-reads live rows, nobody interpreted anything, and it cannot go stale between readings. SELECT-only, single statement, table-whitelisted, validated seven ways before it runs.
- Attested — extracted from something someone wrote, then approved by a named person in your company. That person is on the record, and the fact carries its source and its date.
- On the record — the raw source material itself, unedited. Trustworthy as testimony, not as fact.
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.
- Self-hosted — the complete Atlas under AGPL, in your VPC, free; Docker, Railway or Vercel. Self-host quick start.
- From your AI agent —
bunx @useatlas/mcp init --localagainst a local Atlas, orbunx @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:
- The four context surfaces (semantic layer, Knowledge Base, learned patterns, the Company Atlas) and where answers show up — Introduction
- The YAML semantic layer and a worked
orders.yml— Semantic layer - The NovaMart dataset and the canonical questions — Demo datasets
- The local scaffold (
bun create atlas-agent) — Self-host quick start - The embeddable widget and React component — Embedding widget
- How Atlas compares to Genie, Cortex Analyst, Hyper, Glean and the text-to-SQL peers — Comparisons
- Deploy buttons, starters and Docker Compose — Deploy
- The SQL validation pipeline and sandbox threat model — SQL validation, Sandbox architecture
- Environment variables — Reference and
.env.example - Plugins, datasources, chat platforms and connectors — Plugin authoring, Integrations
- Supported databases and LLM providers — Connect your data, Model routing
- The Knowledge Base, dashboards, and bringing your own frontend — Knowledge Base, Dashboards, Frameworks
- The CLI (
atlas init,atlas diff, and the rest) — CLI reference - The monorepo layout and dev setup — CONTRIBUTING.md
- What is open source and what is commercial — Enterprise boundary
Atlas 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.