We use Infisical to manage secrets day-to-day, currently hosting it on our machines in our offices. Since secrets are something very vital to us, we need somewhere to store secrets securely, and that's why we are using it. Applications need secrets. Applications have APIs and certificates, so day-to-day we use the service to get our secrets and to rotate secrets. That's what we use it for. We use Infisical internally in my company.
Senior Software Engineer at a consultancy with 1-10 employees
Real User
Top 5
Jul 9, 2026
I have been using Infisical consistently for the past couple of years in my current company. The main use case of Infisical is to manage our secrets. We use it to properly manage application secrets and environmental variables across development, staging, and production, replacing hard-coded secrets and .env files with a centralized, secure secrets manager for .NET, Node.js, or AWS workloads. Our main use case is secure secret management, environmental variable management, and syncing it with any other Vercel or cloud deployment that we use. How we use it depends on the particular applications in the first place. Technically, we use Infisical to securely manage secrets for our AWS-hosted applications. During CI/CD deployments, our GitHub Actions pipelines retrieve environment-specific secrets such as database connection strings, JWT signing keys, and third-party API credentials like Knovo, Twilio, or Resend from Infisical and inject them into the applications at deploy time. This keeps secrets out of the codebase and avoids storing them in repository or pipeline variables. For AWS Lambda specifically, our AWS Lambda functions retrieve their configurations and secrets from Infisical during deployment. This allows us to maintain separate secrets for development, staging, and production while ensuring sensitive values such as database credentials and API keys are never committed to source control.
Intern at a educational organization with 501-1,000 employees
Real User
Top 20
Jun 26, 2026
My main use case for Infisical is to store secrets for other programs and tools, and I use it for that most often. For example, we had access keys for the local GitLab instance and those were stored inside Infisical and fetched from there. That is mostly what Infisical was used for with other tools as well.
My main use case for Infisical is to store my CI/CD secret keys, which I use in GitHub. A quick and specific example of how this integration makes my work easier is that it adds a lot of security in the sense of not using passwords in command prompts. That way, I can send commands directly in GitHub using Infisical's secret passwords, without having to leave traces in the commands directly in the terminal. Regarding how Infisical contributes to security or to the management of passwords and commands in my routine, it prevents us from leaving passwords in the command prompts. Alongside GitHub, GitHub does not store passwords. Instead, it accesses Infisical directly through the application without leaving command traces in any prompt. It is excellent regarding security in command prompts, with no password traces.
DevOps Engineer at a computer software company with 11-50 employees
Real User
Top 5
Jun 20, 2026
I primarily use Infisical for keeping the environment values that are used in our applications. We also use Infisical for secret sharing with our developers and clients using Infisical's secret sharing feature. We integrate Infisical to use environment values in our Dockerfile.
Programador Web Senior at a consultancy with 11-50 employees
Real User
Top 10
Jun 19, 2026
My main use case for Infisical is to manage my environment variables in Docker containers. When a container goes up, I hydrate the container with the values at runtime. In a recent project for software for organizational wellness, I have an entry point where I have Infisical CLI installed in the container. When the application comes up, I invoke Infisical CLI with a service token, and with that, I hydrate the container with the corresponding environment variables.
Infisical is primarily used to maintain secret variables or environment variables across different environments. When working on the development environment, environment variables that have been predefined are directly fetched. For example, if environment variables have been placed into an API folder in the development environment, they can be quickly fetched from dev/API. In the same way, if environment variables need to be fetched from staging or production, the particular command attached to that environment can be used to fetch the environmental variables associated with those environments. Integration with Vercel has been implemented on the deployed environment. In that instance, environmental variables also need to be maintained, so the same Infisical environments are used on the Vercel deployed environment as well, depending on the environment, which could be development, staging, or production.
Full Stack Engineer at Marathwada Mitra Mandal's Institute of Technology
Real User
Top 20
Jun 1, 2026
My main use case for Infisical is storing secret keys and secret tokens for a company and injecting them dynamically into the CI/CD workflow because companies typically do not hard-code these key secrets and tokens into their source code.The process was straightforward. I obtained the Infisical token and used it to log in to Infisical from the cloud machine to obtain all the secrets. The secrets were divided based on the project, so for different projects, I obtained different secrets and injected them into the environment file.
Infisical provides a comprehensive solution for managing secret keys and sensitive data, streamlining security processes for businesses. Designed for efficiency, Infisical ensures the protection of data and facilitates better data management workflows.Infisical caters to businesses aiming to secure their sensitive information by offering a robust infrastructure for managing encryption keys and secret data. The system integrates seamlessly into existing workflows, providing specialized...
We use Infisical to manage secrets day-to-day, currently hosting it on our machines in our offices. Since secrets are something very vital to us, we need somewhere to store secrets securely, and that's why we are using it. Applications need secrets. Applications have APIs and certificates, so day-to-day we use the service to get our secrets and to rotate secrets. That's what we use it for. We use Infisical internally in my company.
I have been using Infisical consistently for the past couple of years in my current company. The main use case of Infisical is to manage our secrets. We use it to properly manage application secrets and environmental variables across development, staging, and production, replacing hard-coded secrets and .env files with a centralized, secure secrets manager for .NET, Node.js, or AWS workloads. Our main use case is secure secret management, environmental variable management, and syncing it with any other Vercel or cloud deployment that we use. How we use it depends on the particular applications in the first place. Technically, we use Infisical to securely manage secrets for our AWS-hosted applications. During CI/CD deployments, our GitHub Actions pipelines retrieve environment-specific secrets such as database connection strings, JWT signing keys, and third-party API credentials like Knovo, Twilio, or Resend from Infisical and inject them into the applications at deploy time. This keeps secrets out of the codebase and avoids storing them in repository or pipeline variables. For AWS Lambda specifically, our AWS Lambda functions retrieve their configurations and secrets from Infisical during deployment. This allows us to maintain separate secrets for development, staging, and production while ensuring sensitive values such as database credentials and API keys are never committed to source control.
My main use case for Infisical is to store secrets for other programs and tools, and I use it for that most often. For example, we had access keys for the local GitLab instance and those were stored inside Infisical and fetched from there. That is mostly what Infisical was used for with other tools as well.
My main use case for Infisical is to store my CI/CD secret keys, which I use in GitHub. A quick and specific example of how this integration makes my work easier is that it adds a lot of security in the sense of not using passwords in command prompts. That way, I can send commands directly in GitHub using Infisical's secret passwords, without having to leave traces in the commands directly in the terminal. Regarding how Infisical contributes to security or to the management of passwords and commands in my routine, it prevents us from leaving passwords in the command prompts. Alongside GitHub, GitHub does not store passwords. Instead, it accesses Infisical directly through the application without leaving command traces in any prompt. It is excellent regarding security in command prompts, with no password traces.
I primarily use Infisical for keeping the environment values that are used in our applications. We also use Infisical for secret sharing with our developers and clients using Infisical's secret sharing feature. We integrate Infisical to use environment values in our Dockerfile.
My main use case for Infisical is to manage my environment variables in Docker containers. When a container goes up, I hydrate the container with the values at runtime. In a recent project for software for organizational wellness, I have an entry point where I have Infisical CLI installed in the container. When the application comes up, I invoke Infisical CLI with a service token, and with that, I hydrate the container with the corresponding environment variables.
Infisical is primarily used to maintain secret variables or environment variables across different environments. When working on the development environment, environment variables that have been predefined are directly fetched. For example, if environment variables have been placed into an API folder in the development environment, they can be quickly fetched from dev/API. In the same way, if environment variables need to be fetched from staging or production, the particular command attached to that environment can be used to fetch the environmental variables associated with those environments. Integration with Vercel has been implemented on the deployed environment. In that instance, environmental variables also need to be maintained, so the same Infisical environments are used on the Vercel deployed environment as well, depending on the environment, which could be development, staging, or production.
My main use case for Infisical is storing secret keys and secret tokens for a company and injecting them dynamically into the CI/CD workflow because companies typically do not hard-code these key secrets and tokens into their source code.The process was straightforward. I obtained the Infisical token and used it to log in to Infisical from the cloud machine to obtain all the secrets. The secrets were divided based on the project, so for different projects, I obtained different secrets and injected them into the environment file.