BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.
Fabric
Open-source CLI framework for augmenting humans with AI via reusable, crowdsourced prompt "patterns."
- Category:
- Developer Infrastructure
- Maintenance:
- Actively developed (last commit 6 days ago)
- Pricing:
- Open Source
- Open source:
- Yes (MIT)
- Self-hostable:
- Yes
- Local-first:
- Yes
- Platforms:
- CLI, Web, Self-hosted, Library/SDK, Docker
- AI providers (bring your own key):
- OpenAI, Anthropic, Google Gemini, Azure OpenAI, OpenRouter, Groq, Mistral, DeepSeek, Perplexity, Together AI, Ollama, Custom / OpenAI-compatible
- API key storage:
- Configured by environment variable
- Key risk level:
- LOW
- Trust score:
- 84/100
Fabric is an open-source (MIT) command-line framework by Daniel Miessler that organizes AI prompts into reusable, version-controlled "patterns" (e.g. summarize, analyze code, extract wisdom) runnable from the CLI, a built-in web UI, or REST API. The `fabric --setup` interactive wizard initializes config and lets users enter their OWN API keys for each vendor; if no vendor is specified, it auto-detects based on model name and the keys you've provided. It supports 20+ providers through a three-tier architecture: native SDK integrations (OpenAI, Anthropic/Claude, Google Gemini, Azure OpenAI, Amazon Bedrock, Vertex AI), an OpenAI-compatible layer for vendors like Groq, Mistral, DeepSeek, Together, OpenRouter, and Perplexity (150+ providers via openai_compatible plugins with configurable base URLs), plus local models via Ollama. Runs on macOS, Linux, and Windows. Actively maintained with frequent releases (v1.4.455 on Jun 9, 2026; 408 total releases) and continuous provider updates including Claude Opus 4.7 support.
Why this trust score (84/100)
Trust measures how the tool treats your API key and how much of that has been verified. It contains no popularity signal.
- Key Safety 22/25: The key is supplied by an environment variable or local config file you control.
- Request Routing 17/20: Requests go straight from you to the AI provider.
- Transparency 20/20: Source is public under MIT, so anyone can check how the key is handled.
- Privacy 14/15: Local-first: it works without sending your data anywhere. Can be self-hosted, so the data path stays inside infrastructure you control.
- Maintenance 10/10: Actively developed: commits within the last three months.
- Verification Confidence 1/10: Compiled from public documentation by an AI-assisted pass, not independently confirmed.
What was checked
Verification tier RESEARCH_ASSISTED, derived from the evidence below and not set by hand.
- [REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
- [STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
- [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-04, about 0 month(s) ago. source
How your API key is handled
Your API key is supplied via an environment variable or local config file. 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
Install the tool, set your provider API key as an environment variable (or in its config file), and pick a model.