> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/deploy/installation/production-setup.md).

# Production Setup

This guide walks you through a step-by-step process for installing DIGIT HCM . Installation involves provisioning and configuring the hardware and network, as well as installing HCM services such as PostgreSQL, Elasticsearch, Apache Kafka, and DIGIT HCM services like API Gateway and User Service. DIGIT HCM can be installed on public clouds, such as AWS or Azure, or on a Private Cloud. Installing DIGIT on personal computers is not recommended.

Follow the steps outlined in the sections below to install HCM in the production environment.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Infrastructure Setup</strong></mark></td><td><a href="/health/deploy/installation/production-setup/setup-infrastructure.md">Setup Infrastructure</a></td></tr><tr><td><mark style="color:blue;"><strong>Deploy HCM</strong></mark></td><td><a href="/health/deploy/installation/production-setup/deploy-hcm.md">Deploy HCM</a></td></tr><tr><td><mark style="color:blue;"><strong>Install Monitoring Stack</strong></mark></td><td><a href="/health/deploy/installation/production-setup/install-monitoring-stack.md">Install Monitoring Stack</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/health/deploy/installation/production-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.