BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.

Haystack

Open-source Python framework for building production RAG pipelines and agent workflows with any LLM provider.

Website Source code

Category:
Agent Frameworks
Maintenance:
Actively developed (last commit today)
Pricing:
Open Source
Open source:
Yes (Apache-2.0)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Library/SDK, Self-hosted, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, Azure OpenAI, Mistral, Cohere, Groq, Ollama, Hugging Face, Custom / OpenAI-compatible
API key storage:
User controls deployment
Key risk level:
LOW
Trust score:
80/100

Haystack is deepset's open-source, vendor-agnostic AI orchestration framework for building production-ready LLM applications in Python. Developers compose modular pipelines and agent workflows with explicit control over retrieval, routing, memory, and generation, covering RAG, semantic search, multimodal, and conversational systems. It is bring-your-own-credentials by design: generator components (e.g. OpenAIGenerator) read keys from environment variables by default but accept a key passed directly at init via Secret.from_token("<your-api-key>"), and OpenAIGenerator exposes a configurable api_base_url so end users can point at OpenAI-compatible or self-hosted/local endpoints. It integrates a very broad provider set including OpenAI, Anthropic, Mistral, Cohere, Azure OpenAI, Google Gemini (Google Gen AI / Vertex), Hugging Face, Ollama for local models, AWS Bedrock, NVIDIA, and Groq.

Why this trust score (80/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 21/25: The key lives in a deployment you run yourself.
  • Request Routing 17/20: Requests go straight from you to the AI provider.
  • Transparency 20/20: Source is public under Apache-2.0, so anyone can check how the key is handled.
  • Privacy 11/15: Local-first: it works without sending your data anywhere. Can be self-hosted, so the data path stays inside infrastructure you control. Analytics or error-reporting libraries are present; what they send was not established.
  • 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.
  • [REPORTED · SOURCE_SCAN] References PostHog, so some analytics or error reporting is present. This scan cannot tell whether it is opt-in or what it sends. source
  • [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-14, 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.