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

Koharu

Rust-built ML manga translator with optional bring-your-own-key hosted LLM backends.

Website Source code

Category:
Productivity Tools
Maintenance:
Actively developed (last commit yesterday)
Pricing:
Open Source
Open source:
Yes (GPL-3.0)
Self-hostable:
Yes
Local-first:
Yes
Platforms:
Desktop, Self-hosted, CLI, Docker
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, DeepSeek, OpenRouter, Ollama, Custom / OpenAI-compatible
API key storage:
Stored locally on device
Key risk level:
LOW
Trust score:
85/100

Koharu is a local-first, Rust + Tauri desktop application that automates manga translation by chaining object detection, OCR, inpainting (source-text removal), and an LLM translation step, then rendering vertical CJK / RTL text and exporting layered PSDs. It runs GGUF models locally via llama.cpp (CUDA/Vulkan/Metal) by default, but the koharu-llm crate ships explicit provider modules (openai.rs, claude.rs, gemini.rs, deepseek.rs, openai_compatible.rs) so a user can instead plug in their own hosted API key for OpenAI, Anthropic Claude, Google Gemini, DeepSeek, or any OpenAI-compatible endpoint (OpenRouter, LM Studio), plus machine-translation services (DeepL, Google Cloud Translation, Caiyun). API keys are stored in the OS keychain via the Rust `keyring` crate (set_password/get_password) rather than plaintext config, with a filesystem credential fallback on Linux. Ships an HTTP API and MCP server for automation, runs on Windows/macOS/Linux, and offers a Docker headless mode.

Why this trust score (85/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 GPL-3.0, so anyone can check how the key is handled.
  • 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 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.