Self-Host Infisical: HashiCorp Vault Alternative 2026

Q: Why a Secrets Manager?

The problem with .env files: Secrets live in plaintext files on developer laptops .env files accidentally get committed to Git No audit log — who changed DATABASE_URL last Tuesday at 3am? No access control — every developer has every secret Rotating secrets requires updating N servers manually What a secrets manager provides: Centralized secret storage with encryption at rest Role-based access control (dev gets staging secrets, not prod) Audit log of every read and write Secret versioning (rollb

TL;DR

Infisical is a modern, developer-friendly open source secrets management platform — a simpler alternative to HashiCorp Vault for teams managing environment variables and secrets. It provides a web UI, CLI, SDKs, and integrations with GitHub Actions, Kubernetes, Docker, and major cloud providers. MIT license, ~17K GitHub stars. Self-host with Docker Compose in ~15 minutes. HashiCorp Vault is more powerful for PKI and dynamic secrets, but Infisical is the right choice for most teams managing app secrets and environment variables.

Key Takeaways

Infisical: MIT license, ~17K GitHub stars, TypeScript/React, modern UI, focused on env vars and secrets
HashiCorp Vault (now BSL): Enterprise PKI, dynamic secrets, complex setup — overkill for most teams
OpenBao: Community fork of Vault with MPL 2.0 license — for teams that need Vault's power without BSL
Setup: Docker Compose + Postgres, 15 minutes
CLI injection: infisical run -- node server.js injects secrets automatically
SDK: Available for Node.js, Python, Go, Java, Ruby, .NET

Why a Secrets Manager?

The problem with .env files:

Secrets live in plaintext files on developer laptops
.env files accidentally get committed to Git
No audit log — who changed DATABASE_URL last Tuesday at 3am?
No access control — every developer has every secret
Rotating secrets requires updating N servers manually

What a secrets manager provides:

Centralized secret storage with encryption at rest
Role-based access control (dev gets staging secrets, not prod)
Audit log of every read and write
Secret versioning (rollback to previous value)
Automated injection into apps — no .env files on servers

Infisical vs HashiCorp Vault vs OpenBao

Feature	Infisical	HashiCorp Vault	OpenBao
License	MIT	BSL 1.1 (non-OSS)	MPL 2.0
Setup complexity	Simple (20 min)	Complex (hours)	Complex (hours)
UI	Modern, React	Basic	Basic
env var management	✅ Core feature	Via KV secrets engine	Via KV secrets engine
Dynamic secrets	❌ (limited)	✅	✅
PKI / certificates	❌	✅	✅
Secret leasing/renewal	❌	✅	✅
GitHub Stars	~17K	~32K	~4K
Language	TypeScript/Go	Go	Go
Best for	App secrets, env vars	Enterprise PKI, dynamic secrets	Vault without BSL

Recommendation: Use Infisical for most teams managing app environment variables and API keys. Use Vault or OpenBao if you need PKI, database credential rotation, or enterprise-level dynamic secrets.

Part 1: Docker Compose Setup

# docker-compose.yml
version: '3.8'

services:
  infisical:
    image: infisical/infisical:latest
    container_name: infisical
    restart: unless-stopped
    environment:
      # Required:
      NODE_ENV: production
      ENCRYPTION_KEY: "${INFISICAL_ENCRYPTION_KEY}"    # 32-char random string
      AUTH_SECRET: "${INFISICAL_AUTH_SECRET}"           # 32-char random string

      # Database:
      DB_CONNECTION_URI: "postgresql://infisical:${POSTGRES_PASSWORD}@db:5432/infisical"

      # Redis (for rate limiting and sessions):
      REDIS_URL: "redis://redis:6379"

      # Your deployment URL:
      SITE_URL: "https://secrets.yourdomain.com"

      # Email (optional but recommended for account verification):
      SMTP_HOST: "${SMTP_HOST}"
      SMTP_PORT: "587"
      SMTP_USERNAME: "${SMTP_USER}"
      SMTP_PASSWORD: "${SMTP_PASSWORD}"
      SMTP_FROM_ADDRESS: "noreply@yourdomain.com"

    ports:
      - "8080:8080"
    depends_on:
      - db
      - redis

  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: infisical
      POSTGRES_USER: infisical
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    volumes:
      - postgres_data:/var/lib/postgresql/data

  redis:
    image: redis:7-alpine
    restart: unless-stopped
    command: redis-server --save 60 1 --loglevel warning
    volumes:
      - redis_data:/data

volumes:
  postgres_data:
  redis_data:

# .env — generate secure values:
INFISICAL_ENCRYPTION_KEY=$(openssl rand -hex 16)  # Must be exactly 32 chars
INFISICAL_AUTH_SECRET=$(openssl rand -base64 32)
POSTGRES_PASSWORD=$(openssl rand -base64 24)
SMTP_HOST=smtp.yourdomain.com
SMTP_USER=noreply@yourdomain.com
SMTP_PASSWORD=your-smtp-password

docker compose up -d

Access at http://your-server:8080 (put behind Caddy/Nginx for HTTPS).

Part 2: HTTPS with Caddy

secrets.yourdomain.com {
    reverse_proxy localhost:8080
}

Part 3: First Setup

Visit https://secrets.yourdomain.com
Create your admin account
Create an Organization (e.g., "My Company")
Create a Project (e.g., "backend-api")
Add Environments (Development, Staging, Production)
Add your secrets to each environment

Infisical Data Model

Organization
  └── Projects
        └── Environments (dev, staging, prod)
              └── Secret folders
                    └── Secrets (KEY=VALUE)

Members can have different roles per project (Viewer, Developer, Admin).

Part 4: CLI — Inject Secrets into Any App

Install the Infisical CLI:

# macOS:
brew install infisical/get-cli/infisical

# Linux:
curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.deb.sh' | sudo bash
sudo apt-get install infisical

# Windows:
scoop install infisical

# Set your self-hosted URL:
infisical login --domain https://secrets.yourdomain.com

# In your project directory, initialize:
infisical init
# Select your organization, project, and environment
# Creates: .infisical.json (commit this — no secrets in it)

Run Your App with Injected Secrets

# Inject secrets as environment variables and run:
infisical run -- node server.js
infisical run -- python app.py
infisical run -- npm start
infisical run --env staging -- node server.js   # Use staging env

# Export secrets to a file (for tools that need .env):
infisical export --format dotenv > .env.local

# View all secrets in current environment:
infisical secrets

Docker Run with Infisical

# Inject Infisical secrets into a Docker container:
infisical run -- docker run \
  -e DATABASE_URL \
  -e API_KEY \
  -e JWT_SECRET \
  myapp:latest

Dockerfile — Service Token Approach (Production)

For production, use a Service Token (machine identity) instead of your personal login:

# Dockerfile
FROM node:20-alpine

RUN npm install -g @infisical/cli

COPY . .
RUN npm ci

# At runtime, use service token via INFISICAL_TOKEN env var:
CMD infisical run --token=$INFISICAL_TOKEN -- node server.js

# Generate a service token:
# Infisical UI → Project → Settings → Service Tokens → Add Token
# Copy the token — it's only shown once

# Run container with token:
docker run -e INFISICAL_TOKEN=st.xxx myapp:latest

Part 5: SDK Usage (Node.js)

For apps that need to fetch secrets programmatically (not just at startup):

import { InfisicalClient } from "@infisical/sdk";

const client = new InfisicalClient({
  clientId: process.env.INFISICAL_CLIENT_ID!,
  clientSecret: process.env.INFISICAL_CLIENT_SECRET!,
  siteUrl: "https://secrets.yourdomain.com",  // Your self-hosted URL
});

// Get a single secret:
const dbUrl = await client.getSecret({
  secretName: "DATABASE_URL",
  projectId: "your-project-id",
  environment: process.env.NODE_ENV ?? "development",
});

console.log(dbUrl.secretValue);

// List all secrets:
const secrets = await client.listSecrets({
  projectId: "your-project-id",
  environment: "production",
});

Python:

from infisical_sdk import InfisicalSDKClient

client = InfisicalSDKClient(
    client_id="your-client-id",
    client_secret="your-client-secret",
    site_url="https://secrets.yourdomain.com",
)

secret = client.getSecret(
    secret_name="DATABASE_URL",
    project_id="your-project-id",
    environment="production",
)
print(secret.secretValue)

Part 6: GitHub Actions Integration

Reference Infisical secrets directly in CI/CD:

# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Inject Infisical Secrets
        uses: Infisical/secrets-action@v1.0.7
        with:
          client-id: ${{ secrets.INFISICAL_CLIENT_ID }}
          client-secret: ${{ secrets.INFISICAL_CLIENT_SECRET }}
          env-slug: production
          project-id: your-project-id
          domain: https://secrets.yourdomain.com

      # Secrets are now available as environment variables:
      - name: Deploy
        run: |
          echo "Database: $DATABASE_URL"  # Injected from Infisical
          ./deploy.sh

Part 7: Kubernetes Secret Injection

Infisical can sync secrets to Kubernetes as native Secrets:

# Install Infisical Operator:
# helm repo add infisical-helm-charts https://dl.cloudsmith.io/public/infisical/helm-charts/helm/charts/
# helm install --generate-name infisical-helm-charts/secrets-operator

# InfisicalSecret resource:
apiVersion: secrets.infisical.com/v1alpha1
kind: InfisicalSecret
metadata:
  name: myapp-secrets
spec:
  authentication:
    universalAuth:
      credentialsRef:
        name: infisical-credentials  # K8s secret with clientId/clientSecret
        namespace: default
  infisicalUrl: https://secrets.yourdomain.com
  projectId: your-project-id
  environment: production
  managedSecretReference:
    secretName: myapp-env     # Creates/updates this K8s Secret
    secretNamespace: default

Comparing with OpenBao (Vault Fork)

If you need features Infisical lacks — PKI, database credential rotation, identity-based secret delivery — consider OpenBao instead of HashiCorp Vault:

Use Case	Tool
App env vars, API keys	Infisical
TLS certificate management	OpenBao (Vault fork)
Dynamic database credentials	OpenBao
Enterprise compliance / auditing	OpenBao
SSH certificate issuance	OpenBao
Most developer teams	Infisical

OpenBao is the community fork of HashiCorp Vault (same as OpenTofu for Terraform), released under MPL 2.0 after Vault moved to BSL.

Backup

# Backup Postgres database:
docker exec db pg_dump -U infisical infisical | \
  gzip > infisical-db-$(date +%Y%m%d).sql.gz

# Automated weekly backup script:
#!/bin/bash
docker exec infisical-db pg_dump -U infisical infisical | \
  gzip > /backups/infisical-$(date +%Y%m%d).sql.gz
find /backups -name "infisical-*.sql.gz" -mtime +30 -delete

Cost Comparison

Service	Monthly Cost (10 users)
Doppler (managed)	$24/month
HashiCorp Vault (HCP)	$35+/month
AWS Secrets Manager	~$5 + per-API-call
Infisical (self-hosted)	~$0 (server cost)

Why Self-Host Infisical?

The case for self-hosting Infisical comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Infisical means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Infisical, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Infisical headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Infisical data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Infisical without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Infisical's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Infisical backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Infisical's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Infisical's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Infisical's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Infisical's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f infisical

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Infisical's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats infisical. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Infisical Updated

Infisical follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Infisical is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source HashiCorp alternatives at OSSAlt.com/alternatives/hashicorp-vault.

See open source alternatives to Infisical on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)