> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/reference/what-is-decision-os.md).

# Enterprise · Decision OS

Decision OS is the enterprise version of Audience Loop — the same always-on decisioning, built for scale, governance, and your own infrastructure.

Where Audience Loop runs on our platform, Decision OS runs a bespoke decisioning engine in your own warehouse with zero data egress. It adds cookieless identity, custom agents, and premium data partners, computes next best action for every customer and audience, and gives you a full attribution and decision audit log — with enterprise controls like SSO, custom terms, a dedicated forward-deployed engineer, and bring-your-own cloud, model, and keys.

Same loop, same thesis — you can't grade your own homework — at enterprise scale.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aloop.icustomer.ai/reference/what-is-decision-os.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.