Skip to main content
ZICQ

Skills ZICQ category:DevOps & Cloud infisical-self-host

Infisical Self Host

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).

576 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

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).

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Infisical Self-Hosted Deployment; Not this skill; Guiding Principles; Quick Start; Reference Guides; [Environment Variables](./references/environment-variables.md).

File analysis

File analysis: besides SKILL.md, the body references references/environment-variables.md, references/docker-deployment.md, references/kubernetes-deployment.md, references/scaling-and-ha.md. Those resources load on demand.

Infisical Self-Hosted DeploymentNot this skillGuiding PrinciplesQuick StartReference Guides[Environment Variables](./references/environment-variables.md)[Docker Deployment](./references/docker-deployment.md)[Kubernetes Deployment](./references/kubernetes-deployment.md)[Scaling and High Availability](./references/scaling-and-ha.md)

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
infisical-self-host
description
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).
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 4
  • references/environment-variables.md
  • references/docker-deployment.md
  • references/kubernetes-deployment.md
  • references/scaling-and-ha.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "infisical-self-host" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-a3183359bdad1535-Infisical-Self-Host.html
Save it as .cursor/skills/infisical-self-host/SKILL.md or .claude/skills/infisical-self-host/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/infisical/ai-skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/infisical/ai-skills' --list

npx skills add 'https://github.com/infisical/ai-skills' --skill 'infisical-self-host'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: infisical-self-host description: 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). triggers: - self-host infisical - deploy infisical - docker compose infisical - infisical docker - helm chart infisical - kubernetes infisical - ENCRYPTION_KEY - infisical environment variables - production deployment infisical - FIPS infisical - scale infisical - ha infisical --- # 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 1. **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` 2. **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. 3. **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). 4. **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 5. **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. 6. **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:`, 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 ### [Environment Variables](./references/environment-variables.md) 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 Deployment](./references/docker-deployment.md) 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 Deployment](./references/kubernetes-deployment.md) 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 ### [Scaling and High Availability](./references/scaling-and-ha.md) 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

Related skills

DevOps & Cloud

Docker Essentials

Essential Docker commands and workflows for container management, image operations, and debugging.

DevOps & Cloud

Find Skills

Discover and install skills from the open agent skills ecosystem. Use when: (1) user asks "how do I do X" where X might have an existing ski…

DevOps & Cloud

Microsoft Foundry

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd a…

DevOps & Cloud

Azure Deploy

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT us…