> For the complete documentation index, see [llms.txt](https://docs.aquilax.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquilax.ai/products-and-services/services/deployment-options.md).

# Deployment Options

During both the PoV and regular operation, AquilaX offers three deployment modes to suit the specific needs of your organization:

### Multi tenant

A shared deployment, hosted and maintained by AquilaX (via <https://app.aquilax.ai>), where data separation is handled at the permission level. This option provides a quick, easy setup and offloads maintenance to the AquilaX team, offering a hassle-free solution.

### Single tenant

A dedicated, isolated instance of AquilaX services is deployed exclusively for your organization. This setup ensures full control and isolation while leveraging AquilaX’s capabilities.

### Private Cloud (On-Prem)

Similar to the Single-Tenant option, but deployed within your organization’s infrastructure, whether on-premises or in your own cloud environment. This setup allows for complete internal control and maintenance.


---

# 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.aquilax.ai/products-and-services/services/deployment-options.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.
