For a secrets management platform, the first results are infisical/infisical, hashicorp/vault (Vault is the industry-standard secrets management platform with environment-based secrets, role-based access control, audit logging, encryption at rest and in transit, and broad CI/CD integration — exactly the centralized, team-oriented tool this search describes) and cyberark/conjur (CyberArk Conjur is a purpose-built secrets management platform that secures and distributes secrets across teams and environments, supporting environment-based access, RBAC, audit logs, encryption, and automation via API/CLI and CI/CD integration). stack-auth/stack and logto-io/logto round out the shortlist. Compare the match explanations and check the project documentation against your requirements.
Centralized tools for securely storing, distributing, and managing sensitive credentials across distributed development environments and teams.
Infisical is a centralized secrets management platform designed to store, synchronize, and control access to sensitive credentials and configuration data across distributed development, staging, and production environments. It employs client-side encryption to ensure that secrets remain unreadable to the underlying storage infrastructure, while providing a hierarchical permission model to govern both user and machine access. The platform distinguishes itself through dynamic credential provisioning, which generates short-lived access tokens that are automatically revoked after use. It supports
Infisical is a centralized secrets management platform that stores and syncs environment-specific secrets with client-side encryption, hierarchical RBAC, CLI/API automation, and CI/CD integration, directly addressing every feature in this search including environment separation and team collaboration.
Vault is a centralized secrets management platform designed to secure, store, and control access to sensitive credentials such as API keys, passwords, certificates, and encryption keys. At its core, the system employs a barrier-based cryptographic sealing mechanism that requires an unseal process to decrypt internal storage, ensuring that sensitive data remains protected. It provides identity-based access control to manage granular permissions across distributed infrastructure, effectively centralizing security policies and authentication for both human and machine workloads. What distinguish
Vault is the industry-standard secrets management platform with environment-based secrets, role-based access control, audit logging, encryption at rest and in transit, and broad CI/CD integration — exactly the centralized, team-oriented tool this search describes.
CyberArk Conjur automatically secures secrets used by privileged users and machine identities
CyberArk Conjur is a purpose-built secrets management platform that secures and distributes secrets across teams and environments, supporting environment-based access, RBAC, audit logs, encryption, and automation via API/CLI and CI/CD integration.
Stack is an open-source identity provider that manages user authentication, passkeys, and OAuth tokens. It provides an identity infrastructure that handles user data storage and authentication flows via a centralized administrative dashboard. The platform differentiates itself by integrating a multi-tenant user management system that organizes users into team workspaces through invitation flows. It includes a secure secret vault for storing encrypted API keys and user tokens using encryption keys that remain hidden from the service provider. The system covers a broad range of administrative
Stack is an open-source identity and authentication platform that includes a secret vault for storing encrypted API keys and tokens, but it is not a dedicated secrets management tool for environment-specific secrets across teams and deployments, lacking environment scoping and CI/CD integration.
Logto is an open-source identity provider that serves as a centralized authentication and authorization server for web, mobile, and command-line applications. It implements the OpenID Connect and OAuth 2.1 standards to handle secure user sign-in and the issuance of identity tokens. The platform is specifically designed as a multi-tenant authentication framework for software-as-a-service environments, featuring built-in organization management and tenant isolation. It includes an enterprise single sign-on gateway to integrate external identity providers and supports role-based access control t
Logto is an identity and access management platform for user authentication, not a dedicated secrets management tool for environment-specific secrets, API keys, or CI/CD credential distribution.
This is a role-based access control system for Laravel applications that manages user permissions and roles within a database. It provides a database permissions manager to assign specific abilities to users and roles, utilizing authorization gates to restrict access to routes and interface elements. The project features a wildcard permission system that uses pattern matching to grant broad access across multiple related permissions. It also supports team-scoped access control, allowing users to maintain different roles and permission levels across separate organizational contexts or teams.
Laravel Permission handles role-based access control within a Laravel app, but it is a permissions library, not a secrets management platform for distributing environment-specific secrets across teams—it lacks encryption, audit logging, CI/CD integration, and secret distribution.
Blog.Core is a production-ready backend boilerplate for building enterprise APIs and microservices using ASP.NET Core. It provides a foundational infrastructure for distributed systems, including tools for database-first scaffolding and the implementation of multi-tenant API frameworks. The project distinguishes itself through automated data layer generation, which produces entity models and repository layers directly from database schemas. It implements a centralized identity management system using standard identity server protocols to handle authentication and authorization across multiple
Blog.Core is a backend boilerplate with centralized configuration and RBAC, but it is not a dedicated secrets management platform for distributing environment-specific secrets across teams—it lacks secure secret storage, environment-based scoping, and encryption features tailored to that use case.
Casbin is an authorization library that provides a model-based engine for enforcing access control across diverse application environments. It decouples authorization logic from application code by using a configuration-driven approach, allowing developers to define access rules and evaluation logic independently. The system supports a wide range of access control models, including role-based, attribute-based, and relationship-based patterns, which are evaluated at runtime to determine if a subject is permitted to perform an action on a resource. The project distinguishes itself through a hig
Casbin is an authorization library for access-control policies, not a secrets management platform — it lacks the core capabilities of storing, encrypting, and distributing environment-specific secrets that this search requires.
Dotenv is a configuration management library designed to load environment variables from local files into the process environment. By separating application settings from source code, it enables developers to maintain consistent configurations across different deployment stages and team environments. The utility provides mechanisms to transform plain text configuration files into encrypted formats, allowing sensitive secrets to be stored securely within version control systems. It handles the parsing and normalization of key-value pairs, ensuring that configuration data is consistently proces
dotenv is a library for loading environment variables from local files, not a team-oriented secrets management platform with role-based access control, audit logging, or CI/CD integration.
Kanidm is a centralized identity management server designed to handle authentication, authorization, and directory services across distributed infrastructure. It provides a comprehensive framework for managing human and service accounts, utilizing a schema-driven database to store identity records, group memberships, and system attributes. The platform supports a wide range of authentication methods, including passkeys, passwords, and standard protocols like OAuth2, OIDC, LDAP, and RADIUS. The system distinguishes itself through a granular access control engine that enforces security policies
Kanidm is an identity and access management server for authentication and directory services, not a dedicated secrets management platform with environment-based secret distribution and CI/CD integration; while it offers strong access control, it does not provide the secrets vault and team-centric environment workflows this search requires.
Semaphore is a web interface and API for running and scheduling Ansible playbooks and other infrastructure automation tools. It serves as an infrastructure automation dashboard and DevOps task scheduler for orchestrating deployments. The platform functions as a multi-tool automation hub, providing a centralized dashboard for managing infrastructure as code using Ansible, Terraform, OpenTofu, and Terragrunt. It includes an inventory management tool for organizing target servers and containers, alongside a secret management service for storing sensitive environment variables required during exe
Semaphore is an infrastructure automation dashboard and task scheduler for Ansible, Terraform, etc., which includes a secret management service for environment variables—but its core identity is running playbooks, not serving as a standalone secrets management platform for teams and environments.
Appsmith is a low-code platform designed for building internal business tools, such as operational dashboards and administrative panels. It enables developers to construct dynamic user interfaces by dragging and dropping modular widgets onto a canvas and binding them directly to backend data sources. The platform utilizes a reactive framework that automatically updates interface elements and triggers functions whenever underlying data or widget properties change, eliminating the need for manual event handling. The platform distinguishes itself through a server-side proxy architecture that exe
Appsmith is a low-code internal-tool builder with team collaboration and API support, but its core purpose is constructing user interfaces, not managing and distributing environment-specific secrets across teams and deployment environments the way a dedicated secrets platform would.
| Repository | Stars | Language | License | Last push |
|---|---|---|---|---|
| infisical/infisical | 27.4K | TypeScript | NOASSERTION | |
| hashicorp/vault | 35.8K | Go | NOASSERTION | |
| cyberark/conjur | 937 | Ruby | NOASSERTION | |
| stack-auth/stack | 6.8K | TypeScript | NOASSERTION | |
| logto-io/logto | 12.2K | TypeScript | MPL-2.0 | |
| spatie/laravel-permission | 12.9K | PHP | MIT | |
| anjoy8/blog.core | 5.3K | C# | Apache-2.0 | |
| casbin/casbin | 19.8K | Go | apache-2.0 | |
| motdotla/dotenv | 20.3K | JavaScript | bsd-2-clause | |
| kanidm/kanidm | 4.6K | Rust | mpl-2.0 |