Open-source, end-to-end encrypted secret management platform: distribute secrets/configs across your team/infrastructure and prevent secret leaks.

Slack | Infisical Cloud | Self-Hosting | Docs | Website

Introduction

Infisical is an open source, end-to-end encrypted secret management platform that teams use to centralize their secrets like API keys, database credentials, and configurations.

We're on a mission to make secret management more accessible to everyone, not just security teams, and that means redesigning the entire developer experience from ground up.

Features

• User-friendly dashboard to manage secrets across projects and environments (e.g. development, production, etc.)
• Client SDKs to fetch secrets for your apps and infrastructure on demand
• Infisical CLI to fetch and inject secrets into any framework in local development
• Native integrations with platforms like GitHub, Vercel, Netlify, and more
• Automatic Kubernetes deployment secret reloads
• Complete control over your data - host it yourself on any infrastructure
• Secret versioning and Point-in-Time Recovery to version every secret and project state
• Audit logs to record every action taken in a project
• Role-based Access Controls per environment
• Simple on-premise deployments to AWS, Digital Ocean, and more
• Secret Scanning and Leak Prevention

And much more.

Getting started

Check out the Quickstart Guides

Use Infisical Cloud	Deploy Infisical on premise
The fastest and most reliable way to get started with Infisical is signing up for free to Infisical Cloud.	View all deployment options

Run Infisical locally

To set up and run Infisical locally, make sure you have Git and Docker installed on your system. Then run the command for your system:

Linux/macOS:

git clone https://github.com/Infisical/infisical && cd "$(basename $_ .git)" && cp .env.example .env && docker-compose -f docker-compose.yml up

Windows Command Prompt:

git clone https://github.com/Infisical/infisical && cd infisical && copy .env.example .env && docker-compose -f docker-compose.yml up

Create an account at http://localhost:80

Scan and prevent secret leaks

On top managing secrets with Infisical, you can also scan for over 140+ secret types in your files, directories and git repositories.

To scan your full git history, run:

infisical scan --verbose

Install pre commit hook to scan each commit before you push to your repository

infisical scan install --pre-commit-hook

Lean about Infisical's code scanning feature here

Open-source vs. paid

This repo available under the MIT expat license, with the exception of the ee directory which will contain premium enterprise features requiring a Infisical license.

If you are interested in managed Infisical Cloud of self-hosted Enterprise Offering, take a look at our webiste or book a meeting with us:

Security

Please do not file GitHub issues or post on our public forum for security vulnerabilities, as they are public!

Infisical takes security issues very seriously. If you have any concerns about Infisical or believe you have uncovered a vulnerability, please get in touch via the e-mail address security@infisical.com. In the message, try to provide a description of the issue and ideally a way of reproducing it. The security team will get back to you as soon as possible.

Note that this security address should be used only for undisclosed vulnerabilities. Please report any security problems to us before disclosing it publicly.

Contributing

Whether it's big or small, we love contributions. Check out our guide to see how to get started.

Not sure where to get started? You can:

• Book a free, non-pressure pairing session / code walkthrough with one of our teammates!
• Join our Slack, and ask us any questions there.

Resources

• Docs for comprehensive documentation and guides
• Slack for discussion with the community and Infisical team.
• GitHub for code, issues, and pull requests
• Twitter for fast news
• YouTube for videos on secret management
• Blog for secret management insights, articles, tutorials, and updates
• Roadmap for planned features

Acknowledgements