Simple & Transparent Pricing for your needs

PersonalBusiness
Basic
Free

The basics for individuals

Number of Projects

1 project

Number of Secrets (per Project)

50 secrets
Overview
Number of Projects1 project
Number of Secrets (per Project)50 secrets
Number of UsersUnlimited
Number of Access KeysUnlimited
Encrypted secret storage
Leaked secret detection
Built-in tool for common programming languages
Secret sharing with role-based access controls
Programmatic access with permission-based access controls
Audit logs on secret access
Automatic secret rotationUpcoming
Two-factor authentication
Always-on support
Professional
$37 per month

Billed monthly

Number of Projects

Unlimited ($3/project)

Number of Secrets (per Project)

Unlimited ($0.1/secret)

Overview
Number of ProjectsUnlimited
Number of Secrets (per Project)Unlimited
Number of UsersUnlimited
Number of Access KeysUnlimited
Encrypted secret storage
Leaked secret detection
Built-in tool for common programming languages
Secret sharing with role-based access controls
Programmatic access with permission-based access controls
Audit logs on secret access
Automatic secret rotationUpcoming
Two-factor authentication
Always-on support

* For more information about our Pricing Policy, see this article.

* If your team has a large number of secrets, please refer to the Business package.

Flexible and adaptive by supporting popular programming languages

golanggolangpythonpythonjsjsdotnetdotnetjavajavaclicli

Why does my development team need Locker Secrets Manager?

Locker Secrets ManagerHard-codingConfig Files

Security

Provides a more secure way to store sensitive information, as secrets are stored separately and encrypted. Access control mechanisms can be implemented.

Embedding secrets directly in code is less secure, as they are easily accessible to anyone with access to the codebase.

Storing secrets in configuration files can be risky, especially if these files are not adequately protected. Config files might be readable or accidentally shared, exposing sensitive information.

Dynamic Updates

Facilitates easy and dynamic updates of secrets without requiring changes to the application code. This is important for regular password rotations or key changes.

Requires modifying and redeploying the code whenever a secret needs to be updated, which can be time-consuming and error-prone.

Similar to hard-coding, updating secrets in config files may involve manual changes and redeployment.

Access Control

Offers robust access control mechanisms, allowing fine-grained permissions to be set for different users or systems.

Provides little control over who can access the embedded secrets within the code.

Access to config files might be controlled, but it's typically less flexible and secure compared to a dedicated secrets manager.

Collaboration

Facilitates collaboration by providing a centralized and shared location for storing secrets. Changes are managed more systematically.

Can lead to conflicts when multiple developers are working on the same codebase, especially if they are hard-coding different secrets.

Similar collaboration challenges as hard-coding, especially if changes to config files are not properly coordinated.

Auditing

Often includes auditing and logging features, allowing tracking of who accessed or modified secrets and when.

Typically lacks built-in auditing capabilities for tracking changes to secrets.

May or may not have auditing features, depending on the specific configuration management tools used.

Maintainability

Promotes cleaner and more maintainable code by separating secrets from the application logic.

Can make code harder to maintain, as changes to secrets require code modifications and redeployment.

Offers a middle ground, but improper handling can still lead to maintenance challenges.


Frequently Asked Questions

Everything you need to know about the product and billing.