Deployment architecture overview
Itential Platform supports multiple deployment architectures to meet different operational requirements, from minimal setups for development to highly available configurations for production. This section provides an overview of all available deployment models and architectures.
High-availability architectures
For production environments requiring redundancy and fault tolerance:
- High-availability architecture: Production-ready HA2 architecture with redundant components.
- Active-standby architecture: Geographically redundant setup for business continuity and disaster recovery.
Alternative and minimal architectures
- Alternative architectures: Flexible configurations for specific use cases, including colocated services.
- Minimal architecture: Simplified setup for development, testing, and learning environments.
Main deployment models
Deployment vs. installation
Installation covers placing the Platform software onto a host along with installing dependencies, the Platform binary or RPM, initial configuration, and first startup. See Install Platform for an overview.
Deployment covers how Platform runs as an ongoing workload — container lifecycle, orchestration, scaling, ingress, and secrets management. The guides in this section assume you are working with Itential-provided container images rather than installing directly onto a host.
Before you begin
Both deployment models require:
- Access to the Itential container registry (contact your Itential Account Manager for credentials)
- MongoDB and Redis provided externally — neither is included in the Itential images
- An encryption key generated before starting any Platform container see Install Platform 6 — step 4