> 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/rpm-single-node.md). # Single node A complete OpenIAM deployment on one host — what it includes, when to choose it, and the order of the pages. Everything OpenIAM needs, on one host. The installation configures and starts every tier for you: the application services, the message broker, the cache, the graph and search tiers, the secret store, the reverse proxy, and a database if you want one locally. **Allow about three hours end to end** for a first build, most of it unattended. **Building on AWS or Azure?** Read [*RPM on AWS and Azure*](/installation/rpm/cloud.md) alongside these pages — it covers instance sizing, storage, networking and the managed database. ## How requests reach the platform **Two ports are open to users — 80 and 443.** Everything else stays on the host. ```mermaid flowchart TD U["User's browser"] U -->|"80 / 443"| H["Apache httpd with mod_openiam"] H -->|"8080"| N["Interface router (nginx)"] H -->|"9080"| E["Service bus"] N --> I1["idp — 8081"] N --> I2["Webconsole — 8082"] N --> I3["SelfService — 8083"] N --> I4["SelfService extended — 8084"] N --> I5["report viewer — 8085"] N --> I6["static assets — 8086"] I1 --> E I2 --> E I3 --> E I4 --> E I5 --> E I6 --> E E --> D[("Database")] E --> V["Secret store"] E --> Q["Message broker"] E --> C["Cache"] E --> G["Graph tier and its storage"] E --> S["Search tier"] ``` The reverse proxy is the front door. Behind it, the interface router hands each request to the interface that serves it, and every interface talks to the service bus, which is the backbone the rest of the platform sits behind. [*Ports*](/installation/rpm/rpm-single-node/ports.md) lists each port and what it is for; [*Configure the reverse proxy*](/installation/rpm/rpm-single-node/configure-the-reverse-proxy.md) covers the first hop. ## When this is the right shape * **Evaluations and proofs of concept.** One host, one procedure, a working platform. * **Development and test environments**, where the whole deployment can be rebuilt quickly. * **Production deployments** where a single host meets your availability requirement, or where the platform runs behind infrastructure that provides recovery — a hypervisor cluster, a storage snapshot regime, or a documented rebuild-and-restore procedure. Choose the three-node shape instead when the platform itself must survive the loss of a host. ## Using your own database The single-node shape supports either a local database installed for you, or your own database server. A remote database is a common choice in organisations where database administration is a separate function, and it does not change anything else about the procedure. See [*Use a remote database*](/installation/rpm/rpm-single-node/use-a-remote-database.md). ## The pages, in order
PageWhat it does
Prepare the hostConfirm the host is ready before you install anything
Use a remote databaseRead this before installing if the database is your own
InstallThe package, the configuration, and the initialisation that builds every tier
Install on a separate partitionOptional, during Install: put OpenIAM somewhere other than the root filesystem
Start and verifyConfirm every tier is running and the console is reachable
First sign-inSet the administrator password and the address the platform is published on
ConfigureThe settings worth reviewing before the deployment is used
Add a connectorConnect your first managed system
Configure the reverse proxyHow requests are routed, and what to change if components move
Enable HTTPSPut your certificate in front of the deployment
Back up and restoreEverything to back up, and how to restore it
PortsTwo ports for users; everything else stays on the host
TroubleshootSymptom, meaning, action
**Upgrades** are covered in [*Upgrading OpenIAM*](/installation/rpm/rpm-upgrade.md), which starts by settling whether yours is a minor or a major one. Take a backup first. Work through them in order the first time. On a rebuild you will use *Install* and *Start and verify* alone. ## What you will have at the end A running OpenIAM platform with the Webconsole reachable, an administrator account, and one connector installed and ready to configure. Configuring managed systems, roles, policies and campaigns is the [Administration Guide](/administration-guide/admin.md). ## Related * [*Choose your route*](/installation/choose-your-route.md) * [*Scope and availability*](/installation/scope-and-availability.md) — what this shape survives * [*What you need*](/installation/what-you-need.md) *Applies to OpenIAM 2026.8.1.* --- # 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/rpm-single-node.md?ask=&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.