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

CrewAI

Open-source Python framework for orchestrating collaborative, role-playing autonomous AI agents.

Website Source code

Category:
Agent Frameworks
Maintenance:
Actively developed (last commit today)
Pricing:
Open Source
Open source:
Yes (MIT)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Library/SDK, CLI, Self-hosted, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, Azure OpenAI, OpenRouter, Groq, Mistral, Perplexity, Ollama, Hugging Face, Fireworks, Custom / OpenAI-compatible
API key storage:
Configured by environment variable
Key risk level:
LOW
Trust score:
90/100

CrewAI is a lean, standalone Python framework (independent of LangChain) for building multi-agent systems where role-playing autonomous agents collaborate to complete tasks via "crews" and "flows." It is fully model-agnostic: the user brings their own LLM provider API key, supplied through environment variables (OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, etc.), a YAML config, or the Python LLM class. Through native integrations plus LiteLLM it supports a very broad set of providers and lets users point at any OpenAI-compatible or self-hosted endpoint by setting a custom base_url, including local models via Ollama. It is a developer library/SDK installed via pip and run self-hosted; a separate paid hosted "CrewAI Enterprise/AMP" platform also exists, but the open-source framework itself requires no CrewAI account and uses only the user's own provider keys.

Why this trust score (90/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. 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: 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] 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-14, 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.