> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/plan-and-deploy/reference-architectures.md).

# Reference architectures

- [Edge cluster deployments](https://docs.verge.io/plan-and-deploy/reference-architectures/edge.md): Reference architecture for deploying VergeOS edge clusters at branch offices and remote locations using low-power, small form factor hardware.
- [Multi-tenant deployments](https://docs.verge.io/plan-and-deploy/reference-architectures/csp.md): Reference architecture for Cloud Service Providers deploying VergeOS as a multi-tenant IaaS platform with tenant isolation, resource allocation, and scalable infrastructure.
- [High-performance cluster deployments](https://docs.verge.io/plan-and-deploy/reference-architectures/data-science.md): Reference architecture for deploying VergeOS high-performance clusters for data science, machine learning, and analytics workloads with GPU acceleration and scalable storage.
- [VergeOS homelab reference architecture](https://docs.verge.io/plan-and-deploy/reference-architectures/homelab.md): Reference architecture for deploying VergeOS in homelab environments, covering single-node, two-node cluster, and production-grade configurations with multi-tiered storage.


---

# 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.verge.io/plan-and-deploy/reference-architectures.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.