What is the best approach for me if i want the simplest possible secret management tool.…
- User
What is the best approach for me if i want the simplest possible secret management tool. No need in extra features, need self hosted, lightweight, with embedded db like sqlite and simple http api. Dont want anything else, hashicorp, infisical dont suit those requirements
- Assistant
Okay, your requirements are very specific and lean towards a highly minimalist tool, stripping away almost all the features that modern secret managers often provide. This makes finding an exact match challenging, as most dedicated secret managers add features like auditing, multiple auth methods, UI, etc.
Given your constraints:
- Self-hosted: Required.
- Lightweight: Required (low resource usage, simple deployment).
- Embedded DB (like SQLite): Required (no separate database server needed).
- Simple HTTP API: Required (basic PUT/GET for secrets).
- No extra features: Required (minimalist).
- Exclude Vault/Infisical: Required.
Building something yourself using a lightweight web framework (like Flask in Python or
net/httpin Go) with SQLite or a simple key-value store like BadgerDB or BoltDB would technically meet these requirements. However, building your own secret management tool is generally strongly discouraged due to the significant security complexities involved (encryption at rest, secure key handling, preventing timing attacks, proper authentication/authorization).Finding an existing open-source project that meets all these exact requirements and is actively maintained and secure is difficult because the niche is so small (most people want some features).
However, based on searching for projects that prioritize simplicity, embedded storage, and an API, one tool that appears to fit this very specific description quite well is:
Sekret
- Meets Self-hosted: Yes, you deploy it yourself.
- Meets Lightweight: Yes, it's a single Go binary.
- Meets Embedded DB: Yes, it uses BadgerDB, which is an embedded, lightweight key-value store (similar concept to BoltDB, often considered faster).
- Meets Simple HTTP API: Yes, it provides basic REST endpoints for putting and getting secrets.
- Meets No extra features: Yes, it's explicitly designed to be simple and minimalist, focusing just on storing and retrieving secrets securely. It has basic features like encryption at rest and API token authentication, but lacks complex UIs, integrations, dynamic secrets, etc.
- Excludes Vault/Infisical: Yes.
How it works (Sekret):
- You run the single binary.
- It uses a local directory to store the embedded BadgerDB files.
- Secrets are encrypted at rest. You provide the master encryption key when starting the service.
- You interact with it via simple HTTP requests, typically using an API token for authentication.
Caveats:
- Security: While Sekret handles basic encryption and token auth, you are responsible for managing the master encryption key securely and securing the service endpoint itself (firewall, TLS termination if needed, though Sekret can do TLS). Ensure you understand its security model.
- Maturity/Community: It's not as widely used or battle-tested as Vault or Infisical, which is expected given your constraint of excluding them. Check its activity and features to ensure it's robust enough for your needs (though you asked for simplest, robustness is still important for secrets).
Recommendation:
Given your extremely specific and minimalist requirements, Sekret seems to be the closest existing tool that avoids building your own (and the associated security risks) while meeting the criteria of self-hosted, lightweight, embedded DB, simple API, and minimal features.
Research Sekret further to ensure its security features and operational simplicity align exactly with what you need.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.