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

NextAI Translator

Open-source browser-extension and desktop translator (successor to OpenAI Translator) that translates, polishes, and summarizes text using your own provider API keys.

Website Source code

Category:
Productivity Tools
Maintenance:
Actively developed (last commit 11 days ago)
Pricing:
Open Source
Open source:
Yes (AGPL-3.0)
Self-hostable:
No
Local-first:
Yes
Platforms:
Browser Extension, Desktop
AI providers (bring your own key):
OpenAI, Anthropic, Google Gemini, Azure OpenAI, Groq, Cohere, DeepSeek, Ollama, Custom / OpenAI-compatible
API key storage:
Stored in browser storage
Key risk level:
MEDIUM
Trust score:
69/100

NextAI Translator (formerly OpenAI Translator, renamed after an OpenAI trademark warning) is an open-source, cross-platform translation tool that started as a Bob/Chrome plugin and grew into a browser extension (Chrome, Firefox) plus desktop apps for Windows, macOS, and Linux. It offers three modes (translate, polish, summarize) across 55 languages, with streaming responses, text-to-speech, screenshot/OCR translation, vocabulary book, and clip-extension integrations. Users bring their own provider API keys, configured in the settings UI. The repo ships dedicated engine implementations for a wide range of providers and confirmed OpenAI-compatible custom-endpoint support (used for local servers like Ollama and LM Studio, and providers such as MiniMax). It is AGPL-3.0 licensed, has ~24.9k GitHub stars, and is actively maintained (v0.6.20 released June 2026).

Why this trust score (69/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 AGPL-3.0, so anyone can check how the key is handled.
  • Privacy 8/15: Local-first: it works without sending your data anywhere. Analytics or error-reporting libraries are present; what they send was not established.
  • 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.
  • [REPORTED · SOURCE_SCAN] References Sentry, so some analytics or error reporting is present. This scan cannot tell whether it is opt-in or what it sends. 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 in your browser's local storage. Requests are sent directly to the AI provider.

Setup

Open the extension/app settings, paste your provider API key (kept in your browser), and pick a model.