Infisical Self-Hosted Deployment
This skill guides you through deploying, configuring, and operating Infisical in self-hosted environments. Whether you are running Infisical on Docker, Docker Compose, or Kubernetes, this resource covers essential setup, security hardening, scaling, and maintenance patterns.
Not this skill
| If the user wants... |
Use |
| To deploy the Kubernetes Operator (also a Helm chart, different thing) |
infisical-kubernetes-operator |
| To reach a private resource from Infisical |
infisical-gateway |
| To configure SSO or SCIM on their instance |
infisical-sso |
| Roles, permissions, audit log streams |
infisical-access-control |
| To use Infisical once it is running |
infisical-setup |
| An external KMS or HSM backing the root key |
infisical-kms |
The Helm confusion is worth pre-empting: the secrets-operator chart installs the operator;
this skill covers the chart that installs the platform. Both come from the same Cloudsmith repo.
Guiding Principles
ENCRYPTION_KEY is Critical: This key encrypts all secrets at rest and cannot be recovered if lost. Back it up and rotate it carefully following Infisical's rotation procedures.
- Standard deployments: a random 16-byte hex string —
openssl rand -hex 16
- FIPS-enabled deployments: a 256-bit base64 key instead —
openssl rand -base64 32
AUTH_SECRET is Required: This key is used for session and JWT signing. It is 32 bytes (base64), generated with openssl rand -base64 32, and must be stable across restarts.
Database Requirements: PostgreSQL is the only supported database. Use 14+ for compatibility; Infisical is extensively tested on 16. Always backup your database before upgrading Infisical. Schema migrations run automatically on boot (since v0.111.0-postgres).
Redis is a hard dependency, not just a cache: Beyond caching it holds the background job queue, distributed locks, cross-instance coordination state, and rate-limit counters. The instance will not start unless one of REDIS_URL, REDIS_SENTINEL_HOSTS, or REDIS_CLUSTER_HOSTS is set, and a running instance is degraded while Redis is unreachable.
- Use Redis 6.x or 7.x; at least 6.2 is advised
- All three topologies are supported: standalone, Sentinel, and Cluster
- Active-passive is recommended. Active-active has not been tested and may behave in undocumented ways
- Set the eviction policy to
noeviction. This is required, not a tuning suggestion — evicting keys under memory pressure would silently drop queued work
- Enable persistence (AOF, or at minimum RDB snapshots) and back Redis up. Pending secret rotations, syncs, and webhook deliveries live there; a Redis that comes back empty loses them
- Give Redis the same availability target as the app instances — an unreplicated Redis is a single point of failure for the whole deployment
Stateless Architecture: Infisical is stateless. Scale horizontally by adding more replicas. All state lives in PostgreSQL and Redis. Each instance needs no more than 2–4 CPU cores and 4–8 GB memory; add containers rather than growing one.
FIPS Compliance: Infisical is compliant with FIPS 140-3. Deploy the separate infisical/infisical-fips Docker image (an Enterprise-only image, not a tag on the standard repo) and set FIPS_ENABLED=true. Remember the ENCRYPTION_KEY format changes to 256-bit base64 in FIPS mode.
Quick Start
- Docker Standalone: Pull
infisical/infisical:<version>, set environment variables, run on port 8080.
- Docker Compose: Use
docker-compose.prod.yml from the repository with PostgreSQL and Redis services.
- Kubernetes: Deploy via Helm chart
infisical-standalone-postgres from Cloudsmith registry with optional managed databases.
Reference Guides
Complete reference for all configuration environment variables, including:
- Required keys (ENCRYPTION_KEY, AUTH_SECRET, database, Redis)
- Database and replication setup
- Redis with Sentinel support
- SMTP configuration
- OAuth/SSO providers
- FIPS and telemetry settings
- Security options
Docker and Docker Compose deployment patterns, including:
- Standalone container setup
- Docker Compose production stack
- Image variants (standard and FIPS)
- Production hardening with security capabilities and read-only filesystems
- Health checks
Kubernetes and Helm deployment guide, including:
- Helm chart installation and configuration
- Secret creation and management
- Optional PostgreSQL and Redis (Bitnami charts)
- Pod security and RBAC
- Networking policies and Ingress/TLS
Production scaling patterns and HA architecture, including:
- Horizontal scaling (adding replicas)
- Sizing guidelines for Infisical, PostgreSQL, and Redis
- Database read replicas
- Redis Sentinel for HA
- Backup and upgrade procedures
- License server firewall rules
1---
2name: infisical-self-host
3description: Deploy and operate Infisical self-hosted instances with Docker, Docker Compose, and Kubernetes. Covers architecture, environment variables, ENCRYPTION_KEY management, PostgreSQL setup, Redis configuration (including the required noeviction policy), production hardening, FIPS 140-3 compliance, scaling, and high availability patterns. For deploying the Infisical platform itself. Not for the Kubernetes Operator, which is a separate Helm chart (infisical-kubernetes-operator), nor for using Infisical once running (infisical-setup).
4triggers:
5 - self-host infisical
6 - deploy infisical
7 - docker compose infisical
8 - infisical docker
9 - helm chart infisical
10 - kubernetes infisical
11 - ENCRYPTION_KEY
12 - infisical environment variables
13 - production deployment infisical
14 - FIPS infisical
15 - scale infisical
16 - ha infisical
17metadata:
18 source: https://skillmd.com/skills/infisical/infisical-self-host
19---
20
21# Infisical Self-Hosted Deployment
22
23This skill guides you through deploying, configuring, and operating Infisical in self-hosted environments. Whether you are running Infisical on Docker, Docker Compose, or Kubernetes, this resource covers essential setup, security hardening, scaling, and maintenance patterns.
24
25## Not this skill
26
27| If the user wants... | Use |
28|----------------------|-----|
29| To deploy the **Kubernetes Operator** (also a Helm chart, different thing) | `infisical-kubernetes-operator` |
30| To reach a private resource from Infisical | `infisical-gateway` |
31| To configure SSO or SCIM on their instance | `infisical-sso` |
32| Roles, permissions, audit log streams | `infisical-access-control` |
33| To use Infisical once it is running | `infisical-setup` |
34| An external KMS or HSM backing the root key | `infisical-kms` |
35
36The Helm confusion is worth pre-empting: the `secrets-operator` chart installs the **operator**;
37this skill covers the chart that installs the **platform**. Both come from the same Cloudsmith repo.
38
39## Guiding Principles
40
411. **ENCRYPTION_KEY is Critical**: This key encrypts all secrets at rest and **cannot be recovered if lost**. Back it up and rotate it carefully following Infisical's rotation procedures.
42 - Standard deployments: a random 16-byte hex string — `openssl rand -hex 16`
43 - **FIPS-enabled deployments: a 256-bit base64 key instead** — `openssl rand -base64 32`
44
452. **AUTH_SECRET is Required**: This key is used for session and JWT signing. It is 32 bytes (base64), generated with `openssl rand -base64 32`, and must be stable across restarts.
46
473. **Database Requirements**: PostgreSQL is the only supported database. Use 14+ for compatibility; Infisical is extensively tested on 16. Always backup your database before upgrading Infisical. Schema migrations run automatically on boot (since v0.111.0-postgres).
48
494. **Redis is a hard dependency, not just a cache**: Beyond caching it holds the background job queue, distributed locks, cross-instance coordination state, and rate-limit counters. **The instance will not start unless one of `REDIS_URL`, `REDIS_SENTINEL_HOSTS`, or `REDIS_CLUSTER_HOSTS` is set**, and a running instance is degraded while Redis is unreachable.
50 - Use Redis 6.x or 7.x; at least 6.2 is advised
51 - All three topologies are supported: standalone, Sentinel, and Cluster
52 - **Active-passive is recommended.** Active-active has not been tested and may behave in undocumented ways
53 - **Set the eviction policy to `noeviction`.** This is required, not a tuning suggestion — evicting keys under memory pressure would silently drop queued work
54 - Enable persistence (AOF, or at minimum RDB snapshots) and back Redis up. Pending secret rotations, syncs, and webhook deliveries live there; a Redis that comes back empty loses them
55 - Give Redis the same availability target as the app instances — an unreplicated Redis is a single point of failure for the whole deployment
56
575. **Stateless Architecture**: Infisical is stateless. Scale horizontally by adding more replicas. All state lives in PostgreSQL and Redis. Each instance needs no more than 2–4 CPU cores and 4–8 GB memory; add containers rather than growing one.
58
596. **FIPS Compliance**: Infisical is compliant with **FIPS 140-3**. Deploy the separate **`infisical/infisical-fips`** Docker image (an Enterprise-only image, not a tag on the standard repo) and set `FIPS_ENABLED=true`. Remember the `ENCRYPTION_KEY` format changes to 256-bit base64 in FIPS mode.
60
61## Quick Start
62
63- **Docker Standalone**: Pull `infisical/infisical:<version>`, set environment variables, run on port 8080.
64- **Docker Compose**: Use `docker-compose.prod.yml` from the repository with PostgreSQL and Redis services.
65- **Kubernetes**: Deploy via Helm chart `infisical-standalone-postgres` from Cloudsmith registry with optional managed databases.
66
67## Reference Guides
68
69### [Environment Variables](./references/environment-variables.md)
70Complete reference for all configuration environment variables, including:
71- Required keys (ENCRYPTION_KEY, AUTH_SECRET, database, Redis)
72- Database and replication setup
73- Redis with Sentinel support
74- SMTP configuration
75- OAuth/SSO providers
76- FIPS and telemetry settings
77- Security options
78
79### [Docker Deployment](./references/docker-deployment.md)
80Docker and Docker Compose deployment patterns, including:
81- Standalone container setup
82- Docker Compose production stack
83- Image variants (standard and FIPS)
84- Production hardening with security capabilities and read-only filesystems
85- Health checks
86
87### [Kubernetes Deployment](./references/kubernetes-deployment.md)
88Kubernetes and Helm deployment guide, including:
89- Helm chart installation and configuration
90- Secret creation and management
91- Optional PostgreSQL and Redis (Bitnami charts)
92- Pod security and RBAC
93- Networking policies and Ingress/TLS
94
95### [Scaling and High Availability](./references/scaling-and-ha.md)
96Production scaling patterns and HA architecture, including:
97- Horizontal scaling (adding replicas)
98- Sizing guidelines for Infisical, PostgreSQL, and Redis
99- Database read replicas
100- Redis Sentinel for HA
101- Backup and upgrade procedures
102- License server firewall rules