Locker is a secrets manager that lets you store, manage, and access sensitive information such as passwords, API keys, tokens, certificates, and more. Whether you are an IT student, professional developer, or business owner, Locker is here to help.

Storing sensitive data directly in source code (secrets hardcoding) is a security vulnerability. If the source code is accidentally exposed or through server file-read attacks, these secrets can be collected by attackers, leading to unauthorized access to related systems.

Importing files of secrets from other secrets managers, or applications to Locker Secrets Manager helps you move to Locker faster to secure your secrets.

Export secrets from Locker to protect your data when needed.

On self-hosted Locker Secrets Manager, workspace admins can set up SMTP Email to automatically send any notification to their workspace members via email address.

A workspace is a typical working area in Locker Secrets Manager built up for teams and organizations’ members. Each workspace is independent.

Locker allows you to audit the access logs of any project throughout your workspace to manage your members’ usage of secrets. Follow the instructions below to view all events in your workspace.

With a Cloud account of Locker Secrets Manager, you can create your own workspace and invite other Locker users to your workspace. This helps you and your team collaborate effectively during the development process.

On the self-hosted version of Locker Secrets Manager, you can create new member accounts and grant your team members to access your workspace. This helps you and your team collaborate effectively during the development process.

A project refers to a collection of secrets and environments that are stored together logically and securely within the Locker Secrets Manager and can be accessed by your development team members.

Adding members to a project allows them to access all secrets inside that project. You can add any member within your workspace to a project you created, or to a project where you are designated as the Project Admin.

Access logs show information about actions and events made from Locker CLI or Locker SDKs to the secrets within a particular project, using the project access keys.

Secrets refer to sensitive information such as passwords, API token, database credentials, or any other confidential data that is used to access and protect various resources in your software project.

An environment is where the code in a software project is executed. It allows you to track deployments of your application. Secrets that are stored in an environment are only available to workflow jobs that reference that environment.

Access keys provide programmatic access to, and the ability to decrypt, edit, and create secrets from the Locker CLI or Locker SDKs. You can have a maximum of two active access keys for a project at a time.

The Professional plan of Locker Secrets Manager requires upfront monthly billing based on the project's and secrets' usage in a specific workspace.

Locker Secrets Manager provides two solution for businesses: a cloud-based solution and a self-hosted solution. The two solutions have different billing policies.

Infrastructure dependencies you need to know to set up the Locker Secrets Manager on your self-hosted server.

Configuration to set up the Locker Secrets Manager on your self-hosted server.

Installing and configuring dependencies

Detailed deployment guide for Locker Secrets Manager

Locker Secrets features a command-line interface (CLI) that wraps common functionality and formats output. The Locker Secrets CLI is a single static binary. It is a wrapper around the HTTP API.