> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/installation/rpm.md).

# RPM

Install OpenIAM from RPM packages — the three shapes available, and how to choose between them.

The RPM route installs OpenIAM directly onto Enterprise Linux hosts you provide. Everything the platform needs — the identity services, message broker, cache, graph store, search tier and secret store — is installed and configured by the package.

Choose this route when you run your own Linux estate. If you already run Kubernetes and want OpenIAM to share its pipeline and monitoring, use [*Kubernetes*](/installation/kubernetes.md) instead.

## The three shapes

<table><thead><tr><th width="181.80001831054688">Shape</th><th>Use it when</th><th>What it survives</th></tr></thead><tbody><tr><td><a href="/installation/rpm/rpm-single-node.md"><strong>Single node</strong></a></td><td>Evaluating, or a single host meets your availability requirement</td><td>Nothing — loss of the host means restoring from backup</td></tr><tr><td><a href="/installation/rpm/rpm-ha.md"><strong>Three nodes</strong></a></td><td>The platform must keep serving when one application host is lost</td><td>The loss of one application host, with three dependencies outside that guarantee</td></tr><tr><td><a href="/installation/rpm/cloud.md"><strong>On AWS and Azure</strong></a></td><td>Either shape above, on cloud infrastructure rather than your own</td><td>The same as the shape you chose — the cloud pages cover provisioning and managed databases, not a different topology</td></tr></tbody></table>

**The third is not a separate topology.** It provisions the infrastructure — instances, networking, managed databases — and then hands over to the single-node or three-node procedure. Read it alongside one of the first two, not instead of them.

[Scope and availability](/installation/scope-and-availability.md) is the authority on what each shape actually survives, including the dependencies that sit outside every one of them.

## Before you pick

Two pages apply whichever shape you choose:

* [*What you need*](/installation/what-you-need.md) — hosts, sizing baselines and prerequisites
* [*Obtain the software*](/installation/obtain-the-software.md) — repository access and the packages

If you want the shortest path to a working evaluation, [*Quick start — one host*](/installation/one-host.md) condenses the single-node procedure onto one page with the decisions made for you.

## Already running OpenIAM

[*Upgrading OpenIAM*](/installation/rpm/rpm-upgrade.md) covers moving an existing deployment to a newer release. It starts by settling whether yours is a minor upgrade — staying on the line you are already on — or a major one onto the 2026 line, because the two differ in who runs them and in what they touch.

## Related

* [*Choose your route*](/installation/choose-your-route.md) — all eleven routes, RPM and Kubernetes, with the pages each uses in order
* [*Upgrading OpenIAM*](/installation/rpm/rpm-upgrade.md) — moving an existing deployment to a newer release
* [*Scope and availability*](/installation/scope-and-availability.md) — what each shape survives
* [*System requirements*](/installation/system-requirements.md) — supported versions and baselines
* [*Kubernetes*](/installation/kubernetes.md) — the other deployment route

*Applies to OpenIAM 2026.8.1. Last reviewed 24 August 2026.*


---

# 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.openiam.com/installation/rpm.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.