BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.
KISS Translator
Minimalist open-source bilingual webpage translation extension with bring-your-own-key AI support.
- 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:
- Browser Extension, Web, Self-hosted, Docker
- AI providers (bring your own key):
- OpenAI, Anthropic, Google Gemini, OpenRouter, DeepSeek, Ollama, Custom / OpenAI-compatible
- API key storage:
- Stored in browser storage
- Key risk level:
- MEDIUM
- Trust score:
- 75/100
KISS Translator is a simple, open-source bilingual translation browser extension and userscript (Greasemonkey/Tampermonkey) for translating webpages, selected text, input boxes, and YouTube/video subtitles side-by-side. It supports a wide range of translation backends, including AI/LLM services where the end user supplies their own API credentials: OpenAI, Google Gemini, Anthropic Claude, Ollama, DeepSeek, and OpenRouter, alongside conventional engines like Google, Microsoft, DeepL/DeepLX, Azure AI, and Cloudflare AI. Users configure their own API keys and can point AI services at custom OpenAI-compatible base URLs/endpoints; a Hook mechanism lets it work with virtually any translation interface. It runs across Chrome, Edge, Firefox, Safari (Mac/iOS), Kiwi (Android), Orion, and Thunderbird, and offers cross-device sync via WebDAV or a self-hostable KISS-Worker. Released under GPL-3.0, actively maintained (v2.0.25, June 2026), ~10.9k GitHub stars.
Why this trust score (75/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 13/25: The key is persisted in browser local storage, which any script on the page can read.
- 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-12, about 0 month(s) ago. source
How your API key is handled
Your API key is stored in your browser's local storage. 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 the extension/app settings, paste your provider API key (kept in your browser), and pick a model.