> For the complete documentation index, see [llms.txt](https://docs.securepass.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.securepass.me/documentation/getting-started/deployment-guide.md).

# Deployment guide

This guide covers what you need before you install SECUREpass, how to deploy it, and what to complete before you let users on. It is written for administrators and architects standing the platform up for the first time.

Sizing and prerequisites are drawn from the SECUREpass IDAM, PAM and Azure Private Cloud prerequisites documents. Where those documents disagree, this guide says so rather than picking one — confirm the correct figures with eMudhra for your deployment before you provision anything.

SECUREpass runs as a set of Java services behind a reverse proxy, backed by a relational database. There are three choices to make before you begin.

**Where it runs.** On-premises, or in a private cloud. Azure is documented in detail in section 7; VMware, AWS and GCP are supported for PAM deployments and follow the same pattern.

**How the services are delivered.** Either as WAR files on Apache Tomcat, or as containers under Docker Compose. Tomcat is what every prerequisites document describes and what the POC builds use. Containers are described in the master documentation but are not covered by any current prerequisites document — confirm availability with eMudhra before planning a container deployment.

**Whether this is a proof of concept or production.** Every requirement figure in this guide is a POC minimum for a single instance. Production adds high availability across zones, load balancing, disaster recovery, and capacity sized against your real user population. None of that is covered by the POC figures.

The minimum footprint is two servers: one application server and one database server.