Customer-Hosted SecureAuth Deployment Overview
This section provides an overview of deploying the SecureAuth IAM platform in customer-hosted environments, whether on-premises, in private data centers, or in self-managed public cloud infrastructure (e.g., AWS, Azure, GCP).
Learn about available deployment models, required dependencies, and how to configure SecureAuth for production readiness.
Deployment Options
SecureAuth is designed to be deployed on Kubernetes (K8s) using Helm Charts.
Core Dependencies
SecureAuth supports the following components as part of its customer-hosted deployment:
| Dependency | Requirement | Description |
|---|---|---|
| CockroachDB | Required | Stores user identities, client configurations, consent records, and more. |
| Redis Cluster | Required | Stores session data, access tokens, ID tokens, and other key-value pairs. |
| TimescaleDB | Optional | Stores audit logs and analytics using a time-series-optimized database. |
| SpiceDB | Optional | Enables fine-grained authorization (FGA) for applications integrated with SecureAuth. |
| Fission or Self-Managed FaaS |