Alternatives
Products that do what GitHub does
Stop losing tokens to dead API keys
- 1
- 2IB
Hey HN, I am proud to show you guys that I have built an open source alternative to Azure OpenAI services. Azure OpenAI services was born out of companies needing enhanced security and access control for using different GPT models. I want to build an OSS version of Azure OpenAI services that people could self host in their own infrastructure. "How can I track LLM spend per API key?" "Can I create a development OpenAI API key with limited access for Bob?" "Can I see my LLM spend breakdown by models and endpoints?" "Can I create 100 OpenAI API keys that my students could use in a classroom…
2023 · github.com
- 3
- 4
- 5
- 6
- 7CG
Howdy all. I'm Zack :wave:. I've been thinking about the problem of misguided AI pull requests and figured I'd throw a possible solution out there for feedback. Basically, CleverCrow lets supporters give tokens to a GitHub repo (or set of issues in that repo) for the maintainers to use to build/fix stuff. The fun implementation challenges have been around implementing the pooling dynamics and keeping the maintainers in charge while the backers are motivated to support their work.
Jun 2026 · clevercrow.io
- 8
- 9
- 10AT
I recently built a small open-source tool to benchmark different LLM API endpoints — including OpenAI, Claude, and self-hosted models (like llama.cpp). It runs a configurable number of test requests and reports two key metrics: • First-token latency (ms): How long it takes for the first token to appear • Output speed (tokens/sec): Overall output fluency Demo: https://llmapitest.com/ Code: https://github.com/qjr87/llm-api-test The goal is to provide a simple, visual, and reproducible way to evaluate performance across different LLM providers, including…
2025 · llmapitest.com
- 11LT
Current AI-assisted CLI tools are often part of larger systems and work better on Linux. I built llm-term to address these. It's a Rust-based tool that compiles into a single binary file. You only need to download the binary, add it to your PATH, and configure your OpenAI key to get started. While llm-term offers an option for gpt-4o, it works great with gpt-4o-mini. So it's not costly. I appreciate any feedback or suggestions.
2024 · github.com
- 12KD
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
- 13KC
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
- 14
- 15CM
2016 · github.com
- 16OS
Jun 2026 · github.com
- 17
- 18IB
over this weekend myself and two of my friends took part in a hackathon and built this side-project. we have been diving into computer-use recently and developed an sdk to make it easy to implement for devs like us. one feature we were missing though, was the agent being able to log into services. anthropic understandably blocks this capability with their guardrails, and you wouldn't want your credentials to end up in any model context anyways. so we added a keychain service to the vm that the agent is using. it was built using the pass cli (https://www.passwordstore.org/).…
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
- 20AC
Hi HN! We love the "backend-less" stack: Stripe for payments, Supabase for data, Clerk for auth. But the moment we add AI features, we're forced to spin up a backend to hide API keys, implement per-user token-based rate limits and graceful degradation, etc. So we built Airbolt. What it does: Drop in our SDK and start making OpenAI calls directly from your frontend. Your keys are AES-256-GCM encrypted on our servers, never exposed to the client. We provide token-based per-user rate limits and origin allow lists to address inference abuse. Short-lived JWTs and bring-your-own-auth are coming…
Sep 2025 · airbolt.ai
- 21
- 22
Scan every LLM API call for PII and injection attacks
Jun 2026 · secure-mind-live.github.io
- 23
- 24FA
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →