BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.
ChainForge
Visual prompt-engineering environment for comparing prompts across models, with keys you enter or load locally.
- Category:
- Prompt Engineering Tools
- Maintenance:
- Actively developed (last commit 17 days ago)
- Pricing:
- Open Source
- Open source:
- Yes (MIT)
- Self-hostable:
- Yes
- Local-first:
- No
- Platforms:
- Web, Self-hosted, Docker
- AI providers (bring your own key):
- OpenAI, Anthropic, Google Gemini, AWS Bedrock, Hugging Face, Custom / OpenAI-compatible
- API key storage:
- User controls deployment
- Key risk level:
- LOW
- Trust score:
- 88/100
ChainForge is a visual programming environment, from an academic HCI project, for battle-testing and comparing prompts side by side across models. You enter your OpenAI, Anthropic, Google or Bedrock credentials in a settings panel, or when running locally the app loads them from your environment, so nothing passes through ChainForge's servers in the self-hosted path. Runs as a local web app. MIT licensed, 3,025 stars, last commit about two months before review.
How this tool was scored
Key handling 85/100 (where your key rests and who sees it, comparable across any licence) and verifiability 90/100 (how much of that BYOAIK could confirm, lower for closed source). Neither contains a popularity signal.
- Key Safety 21/25: The key lives in a deployment you run yourself.
- Request Routing 20/20: Requests go straight from you to the AI provider. The provider endpoint is configurable, so you can point it at the provider or your own gateway.
- Transparency 20/20: Source is public under MIT, so anyone can check how the key is handled. Key handling was located in the published source.
- Privacy 10/15: Can be self-hosted, so the data path stays inside infrastructure you control.
- Maintenance 10/10: Actively developed, with commits within the last three months.
- Verification Confidence 7/10: Key handling was found in the published source by BYOAIK's scanner.
What was checked
Verification tier SOURCE_VERIFIED, derived from the evidence below and not set by hand.
- [STRONG · SOURCE_SCAN] The user supplies their own OpenAI key: the project references its API key variable. source
- [STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
- [STRONG · SOURCE_SCAN] The provider endpoint is configurable, so requests can be pointed straight at the provider or at your own gateway. source
- [STRONG · SOURCE_SCAN] The user supplies their own Anthropic key: the project references its API key variable. source
- [STRONG · SOURCE_SCAN] The user supplies their own DeepSeek key: the project references its API key variable. source
- [STRONG · SOURCE_SCAN] The user supplies their own Cohere key: the project references its API key variable. source
- [STRONG · SOURCE_SCAN] The user supplies their own Hugging Face key: the project references its API key variable. source
- [CONFIRMED · SOURCE_SCAN] Ships a container definition, so it can be self-hosted on your own infrastructure. source
- [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-09-27, about 0 month(s) ago. source
How your API key is handled
You self-host the app, so your API key lives in your own deployment. Requests are sent directly to the AI provider. Because it can be self-hosted, your key never has to touch a third-party backend.
Setup
Deploy it (Docker/compose), add your provider API key in the admin or environment config, then select models.