Alternatives
Products that do what KeyHaven does
Secure api key management and analytics platform
- 1ES
2017 · envkey.com
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9IB
2024 · github.com
- 10
- 11
- 12
- 13
- 14
- 15
- 16CM
2016 · github.com
- 17GM
2017 · gitmonkey.io
- 18KD
I built this after seeing multiple teams accidentally ship API keys in their frontend code. The problem: Modern web development moves fast. You're vibe-coding, shipping features, and suddenly your AWS keys are sitting in a tag visible to anyone who opens DevTools. I've personally witnessed this happen to at least 3-4 production apps in the past year alone. KeyLeak Detector runs through your site (headless browser + network interception) and checks for 50+ types of leaked secrets: AWS/Google keys, Stripe tokens, database connection strings, LLM API keys (OpenAI, Claude, etc.), JWT…
Nov 2025 · github.com
- 19LO
Key management for multiple users and multiple cloud LLM/GenAI APIs is difficult to be both safe and convenient. Sharing keys among users risks leaking the key and makes it difficult to curb the leakage without interruptions. But assigning one key per user per cloud API results in too many keys to keep track of. Meet LlaMa(ster)Key, the secure and easy solution for API key management: * For each user, one master key for multiple APIs. * The master key is unique to each user. Granting and revoking a user's access won't impact other users. * The actual API keys to authenticate with cloud…
2024 · github.com
- 20
- 21
- 22AA
G’day Hacker News, I’m Simon Gurcke, the sole founder of Apitally (https://apitally.io). I’m building a simple API monitoring and analytics tool for Python / Node.js apps. It helps users understand API usage and performance, spot issues early and troubleshoot effectively when something goes wrong. Features include: - Dashboards: Provide insights into API traffic, errors, performance and consumers. - Request logging: Opt-in and highly configurable in terms of what data is logged. Users can drill down from aggregated metrics to individual requests (proven to be super helpful…
2025 · apitally.io
- 23KC
I think in-process key management is the right abstraction for multi-key LLM setups. Not LiteLLM, not a Redis queue, not a custom load balancer. The failure modes are well-understood: a key gets rate-limited, you wait, you try the next one. Billing errors need a longer cooldown than rate limits. This is not a distributed systems problem — it's a state machine that fits in a library. The problem is everyone keeps solving it with infrastructure instead. Spin up LiteLLM, now you have a Python service to maintain. Reach for Redis, now you have a database for a problem that doesn't need one.…
Mar 2026 · github.com
- 24TD
Hey HN! After 6 years of R&D, our small team is excited to share our project TideCloak - an IAM designed to help developers move fast without worrying about catastrophic breaches or overpowered admins with keys to the kingdom. Traditional IAMs rely on centralized authority - admins, root certificates, and decryption keys - which create glaring vulnerabilities in a breach. To address this, we’ve integrated Keycloak (Red Hat’s IAM) with a decentralized key architecture powered by our (academically validated) Ineffable Cryptography. Here’s the idea: keys are split across a decentralized network…
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →