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

InvokeAI

Open-source Stable Diffusion creative studio with BYOK cloud image models

Website Source code

Category:
Image Generation Tools
Maintenance:
Actively developed (last commit 7 days ago)
Pricing:
Open Source
Open source:
Yes (Apache-2.0)
Self-hostable:
Yes
Local-first:
No
Platforms:
Self-hosted, Desktop, Web, Docker
AI providers (bring your own key):
OpenAI, Google Gemini, Custom / OpenAI-compatible
API key storage:
Stored locally on device
Key risk level:
LOW
Trust score:
81/100

InvokeAI (Invoke) is an open-source (Apache-2.0) creative engine for Stable Diffusion, offering a professional web UI with a unified canvas, inpainting/outpainting, node-based workflows, gallery/board management, model installation, and upscaling. It runs local diffusion models (SD 1.5/2/SDXL/3.5, Flux, etc.) self-hosted on your own hardware. It also supports externally-hosted ("API-only") image models from cloud providers using your own API keys: users add credentials to an api_keys.yaml file (external_openai_api_key, external_gemini_api_key, plus optional external_openai_base_url / external_gemini_base_url for OpenAI-compatible proxies or regional endpoints) to install models from OpenAI (GPT Image 1/1.5/mini, DALL-E 3), Google Gemini (Gemini image models), BytePlus Seedream, and Alibaba Cloud DashScope (Qwen Image, Wan). The Community Edition is free and self-hosted; paid cloud generation plans existed but the hosted cloud service was slated for discontinuation in late 2025 while the open-source edition continues. The repo is actively maintained (~27.5k stars, last push June 2026).

Why this trust score (81/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 23/25: The key is held on your own device.
  • 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 10/15: 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 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.
  • [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-15, about 0 month(s) ago. source

How your API key is handled

Your API key is stored locally on your device. 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

Open settings, paste your provider API key, choose a model, and start. The key stays on your device.