> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/~/changes/4UGStBVc3npNySIR4GYW/deploy-on-your-cloud/reference-architecture-diagrams.md).

# Reference Architecture Diagrams

Authgear Enterprise Plan offers self-managed options for customers to run the whole application on their private cloud or public cloud instances using our docker images. This is generally useful for regulated industries such as Financial, Insurance or Public Sectors which must retain the processing and storage of user data on-premises or in specific geographical area.

### Authgear Application Architecture Diagram

<figure><img src="/files/wefSgOTjIbAvfNFVEAca" alt=""><figcaption></figcaption></figure>

([Link](https://oursky.notion.site/Authgear-Reference-Architecture-Public-Page-099f15d621784f9299c86a6dcf55bade) to download original FigJam file)

### Deployment Options

* Depending on [Backend Integration](/~/changes/4UGStBVc3npNySIR4GYW/get-started/backend-api/backend-integration.md) approach, Authgear Resolvers is not needed if your backend self-validate user cookies or JWT.
* Supports custom SMS and email gateways.
* Redis is required to store user session, its recommended to use managed redis so session data can be persistent and users can keep their session in event of redis restart.
* Optional storage services:
  * Cloud storage is optional and only needed if allow user to upload profile image, which is disabled by default.
  * Elasticsearch is optional and only needed to support user search in the Authgear admin portal.
* Please refer to [Deploy with Helm chart](/~/changes/4UGStBVc3npNySIR4GYW/deploy-on-your-cloud/helm.md) for deployment options and details.


---

# 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.authgear.com/~/changes/4UGStBVc3npNySIR4GYW/deploy-on-your-cloud/reference-architecture-diagrams.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.