BYOAIK — Bring Your Own AI Key: a directory of AI tools that run on your own API key.

Langfuse

Self-hosted LLM engineering platform — prompt management, playground and evals all run against a key you bring.

Website Source code

Category:
Developer Infrastructure
Pricing:
Open Source
Open source:
Yes (Mixed: MIT core, separate enterprise licence for ee/)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Self-hosted, Docker, Web, Library/SDK
AI providers (bring your own key):
OpenAI, Anthropic, Azure OpenAI, Ollama, Custom / OpenAI-compatible
API key storage:
User controls deployment
Key risk level:
LOW
Trust score:
75/100

Langfuse is an open-source LLM engineering platform combining prompt management, a prompt playground, tracing, evaluations and datasets. The self-hosting documentation describes the LLM connection for the playground and LLM-as-judge evaluations as optional and bring-your-own: you connect your own key for OpenAI, Anthropic, Azure OpenAI or any OpenAI-compatible endpoint including Ollama, and nothing is routed through a Langfuse-owned key. Deploys through Docker Compose, Kubernetes or Helm. Core code is MIT with enterprise features under a separate licence in the ee/ directory. 32,899 stars.

Why this trust score (75/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 15/20 — Source is public, though the licence is unclear or non-standard.
  • 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, not set by hand.

  • [STRONG · SOURCE_SCAN] Supports a local model backend, so it can run with no cloud provider key at all. source
  • [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] Ships a container definition, so it can be self-hosted on your own infrastructure. source
  • [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-08-11 — 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.