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

manga-image-translator

One-click OCR and translation of text baked into manga, comics, and images, with your own LLM/MT provider keys.

Website Source code

Category:
Productivity Tools
Maintenance:
Maintained (last commit about 2 months ago)
Pricing:
Open Source
Open source:
Yes (GPL-3.0)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Self-hosted, Web, CLI, Library/SDK, Docker
AI providers (bring your own key):
OpenAI, Google Gemini, Groq, DeepSeek, Together AI, Ollama, Custom / OpenAI-compatible
API key storage:
Configured by environment variable
Key risk level:
LOW
Trust score:
93/100

A self-hostable Python tool that detects text in manga/comic/images via OCR, removes it through inpainting, machine-translates it, and re-renders the translated text back into the image. It ships a web server (FastAPI backend + Vue front), a CLI, and Docker/docker-compose images, plus optional GPU acceleration. Translation can route through many backends: LLM providers configured with the end user's own API keys (OpenAI/ChatGPT, Google Gemini, Groq, DeepSeek, Together AI, and any OpenAI-compatible endpoint including local Ollama), conventional MT services (DeepL, Baidu, Youdao, Caiyun, Papago), the Sakura LLM, and fully offline models (NLLB, Sugoi, M2M100). Keys are supplied via a .env file or Docker environment variables (OPENAI_API_KEY, DEEPSEEK_API_KEY, GROQ_API_KEY, GEMINI_API_KEY, TOGETHER_API_KEY, CUSTOM_OPENAI_API_BASE/CUSTOM_OPENAI_API_KEY, etc.), confirmed directly in manga_translator/translators/keys.py and examples/Example.env. Note: the candidate's claimed license (MIT) is incorrect, the repo is GPL-3.0, and star count is ~10k, not 6k.

Why this trust score (93/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 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 GPL-3.0, 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] The user supplies their own Google Gemini key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own Groq key: the project references its API key variable. source
  • [STRONG · SOURCE_SCAN] The user supplies their own DeepSeek 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
  • [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-07-20, about 1 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.