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

OpenMAIC

Multi-agent AI classroom from Tsinghua that turns a topic into a course, on providers you configure.

Website Source code

Category:
Education Tools
Maintenance:
Actively developed (last commit today)
Pricing:
Open Source
Open source:
Yes (MIT)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Web, Self-hosted, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, DeepSeek, Groq, OpenRouter, LM Studio, Ollama, Custom / OpenAI-compatible
API key storage:
User controls deployment
Key risk level:
LOW
Trust score:
92/100

OpenMAIC is an open multi-agent interactive classroom from Tsinghua University's MAIC group: agents generate slides, quizzes, simulations and project work around a topic rather than serving one fixed lesson. It is self-hosted and provider-agnostic, with OPENAI_API_KEY, Anthropic, Ollama and any OpenAI-compatible endpoint configured by the operator, so a school can run the whole thing against a local model and keep student work on its own machines. MIT, and by a wide margin the most-adopted education tool in this directory.

How this tool was scored

Key handling 92/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 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, 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.

  • [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] The user supplies their own OpenAI key: the project references its API key variable. 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 OpenRouter key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Azure OpenAI key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own xAI Grok 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 DeepSeek 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-29, 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.