# Every team, their own tools. One set of facts

NOAN for Enterprise. You will never standardize everyone onto one AI product, and you do not have to. NOAN sits underneath the tools your teams already use as the fact layer they all read, over the API and MCP. Change a fact once and every team, tool, and app is current at the same moment.

Web page: https://www.getnoan.com/use-cases/enterprise

## The enterprise context problem

Nobody is wrong on purpose. The copies just drift.

- **Truth is scattered:** Knowledge lives across decks, wikis, drives, and individual heads. Every team quietly maintains its own version of the messaging, the pricing, the product story.
- **One owner per domain:** In NOAN, marketing owns messaging. Finance owns pricing. Product owns what the product does. Each domain of truth is maintained once, by the function that knows it, with full version history.
- **Everyone reads the source:** Claude, ChatGPT, internal tools, whatever a team prefers or adopts next year, all read the same facts over the API and MCP. There are no copies left to drift.

## Keep the tools. Centralize the truth

NOAN does not replace your teams' tools and does not ask anyone to switch. It sits underneath them as the layer of record that everything reads from.

- **One brain, every surface:** Claude and ChatGPT connect over MCP. Internal apps, sites, and agents connect over plain REST. Different tools, different teams, the same verified facts.
- **Build without permission:** Anyone in the organization can build an app, agent, or workflow for their own use case, on whatever stack they like, without re-litigating what is true. Unlimited API keys on every paid plan.
- **Change once, everything updates:** Update the positioning or a price in NOAN and every app anyone has built, in every corner of the company, reads the new version immediately. No rollout, no chasing collateral.
- **Governed and auditable:** Every fact is versioned with an owner and full history, and every API key is scoped to the stacks and actions it needs. Compliance can trace any answer back to the fact it came from and when it was true.

## NOAN for Enterprise

Video: https://vimeo.com/1230720085/af526d7c8d

## What teams build on it

When truth is a service, every function ships its own tools instead of filing a ticket.

- **Sales enablement:** A proposal and deck generator any rep can use, always on current pricing and positioning.
- **Support answers:** A service-desk assistant grounded in current product facts, not last quarter's manual.
- **Brand and compliance checks:** Materials checked against the current standards and approved claims before they ship.
- **Internal Q&A:** Ask the company anything from Claude or ChatGPT and get the owned answer, not folklore.
- **Onboarding:** New hires learn from the company brain instead of tribal knowledge and a folder of stale decks.
- **Reporting:** Board and stakeholder updates assembled from live facts, so the number in the deck is the number in the graph.

## One graph under a thousand tools

Domains of truth, each owned by the function that knows it best, connected in one graph and served to every team over one API.

- **No re-litigating truth:** A fact is settled once, by its owner. Every team builds on it instead of debating it in every deck.
- **Tool churn without truth churn:** Teams adopt new tools every year. The facts underneath do not move, so nothing has to be migrated or re-taught.
- **Drift becomes impossible:** There are no copies. Every surface reads the source, so the answer is the same in every tool, for every team.

## Your company on any date. Every change on the record

The company graph is versioned end to end. Pick a date and see your facts, contacts, and relationships exactly as they stood that day, then trace any change to who made it and when.

- **Rewind the graph:** Time Travel shows the state of your business on any specific day: the facts, the contacts, the assets, and how they connected at that moment.
- **Who, what, when:** Every fact carries its owner and full version history. When audit or compliance asks, the answer is a lookup, not an investigation.
- **Decisions in context:** See what the company believed when a decision was made and compare it with today. Pivots and mistakes stop being folklore.
- **Humans and agents, one record:** People and agents write to the same versioned graph, so every update traces back to its source, whoever or whatever made it.

## Everyone reads the truth. Not everyone reads all of it

Roles and fact permissions decide what each person can see and touch, and every API key acts as the person who created it, narrowed further by its own scopes and allowed stacks.

- **Roles at the account level:** Account roles set what each user can interact with, managed in settings by your admins, not in code.
- **Fact permissions per domain:** Sensitive domains of truth stay with the people who own them, visible and editable only where you decide.
- **Keys scoped below their owner:** A personal API key authenticates as its creator, is capped by their permissions, and can be narrowed further to read or write per resource and a list of allowed stacks. An agent or app never reads more than its owner could.
- **Blast radius by design:** You decide what a tool or agent can touch before you point it at anything. Handing over a key never hands over the company.

## Connect your agent to verified facts

- MCP: https://mcp.getnoan.com/mcp. Sign in over OAuth or send a NOAN API key. Install steps for Claude, ChatGPT, Cursor and Codex: https://www.getnoan.com/mcp
- REST: https://api.getnoan.com/v1 with a bearer key. OpenAPI spec: https://api.getnoan.com/openapi.json
- Or tell any agent: "Read https://www.getnoan.com/setup.md and follow it."

## Put one fact layer under your enterprise

Start with a pilot: pick one domain of truth and one owner, and let every team read it.

Talk to sales: mailto:hello@getnoan.com?subject=NOAN%20Enterprise