8. Infisical for Secrets Management
Date: 2025-10-13Status
AcceptedCategory
Security & ComplianceContext
Production applications require secure secret management for:- API keys (LLM providers, OpenFGA, Keycloak)
- Database credentials
- JWT signing secrets
- Encryption keys
- Secrets in
.envfiles committed to git accidentally - No secret rotation capability
- No audit trail of secret access
- Secrets visible in process listings
- No centralized secret management across environments
Decision
Use Infisical as the primary secrets management solution with environment variable fallback.Why Infisical
- Open Source: Self-hosted option for compliance
- Developer Friendly: Simple SDK, good DX
- Multi-Environment: Dev, staging, production isolation
- Secret Versioning: Track secret changes over time
- Access Control: Fine-grained permissions
- Audit Logging: Who accessed what, when
- Secret Rotation: Programmatic secret updates
- SDKs: Python SDK available
Consequences
Positive Consequences
- Security: Secrets never in git, encrypted at rest
- Rotation: Easy programmatic secret rotation
- Audit Trail: Complete secret access history
- Multi-Environment: Separate secrets per environment
- Compliance: SOC 2, HIPAA audit requirements met
Negative Consequences
- Dependency: External service dependency
- Complexity: Additional infrastructure to manage
- Latency: Network call to fetch secrets (mitigated by caching)
Alternatives Considered
- HashiCorp Vault: More complex, enterprise-focused
- AWS Secrets Manager: Cloud vendor lock-in
- Environment Variables Only: No rotation, audit, or security