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

Hugging Face Chat UI

Open-source SvelteKit chat interface powering HuggingChat, self-hostable against any OpenAI-compatible endpoint with your own API key.

Website Source code

Category:

AI Chat Interfaces

Pricing:

Open Source

Open source:

Yes (Apache-2.0)

Self-hostable:

Yes

Local-first:

Yes

Platforms:

Web, Self-hosted, Docker

AI providers (bring your own key):

OpenAI, Ollama, Hugging Face, OpenRouter, Custom / OpenAI-compatible

API key storage:

User controls deployment

Key risk level:

LOW

Trust score:

90/100

Chat UI is the open-source codebase behind Hugging Face's HuggingChat. It is a SvelteKit web app (MongoDB optional; an embedded DB is used in dev) that you self-host and point at any OpenAI-compatible API. BYOK is the core configuration path: you create a .env.local file and supply OPENAI_BASE_URL plus OPENAI_API_KEY, and Chat UI auto-discovers available models from your endpoint. The docs give ready-made base-URL/key pairs for the Hugging Face Inference Providers router (hf_xxx), Ollama (local), llama.cpp (local), and OpenRouter (sk-or-v1-xxx), and state that any service speaking the OpenAI protocol works by default. It supports MCP tool/function calling, multimodal image input on vision models, an LLM router for model selection, and optional OpenID authentication. Note: recent versions (v0.10.0, May 2026) speak the OpenAI protocol only and removed legacy provider-specific integrations, so non-OpenAI providers like Anthropic or Gemini must be reached through an OpenAI-compatible proxy/router rather than a native key field.

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.