BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.
Pot (pot-desktop)
Cross-platform desktop app for selection translation and OCR, powered by your own provider keys.
- Category:
- Productivity Tools
- Maintenance:
- Maintained (last commit about 2 months ago)
- Pricing:
- Open Source
- Open source:
- Yes (GPL-3.0)
- Self-hostable:
- No
- Local-first:
- Yes
- Platforms:
- Desktop
- AI providers (bring your own key):
- OpenAI, Google Gemini, Azure OpenAI, Ollama, DeepSeek, OpenRouter, Custom / OpenAI-compatible
- API key storage:
- Stored locally on device
- Key risk level:
- LOW
- Trust score:
- 82/100
Pot is an open-source (GPL-3.0) cross-platform desktop application for text translation, OCR/screenshot translation, text-to-speech, and vocabulary collection. It runs on Windows, macOS, and Linux. Users bring their own credentials: each cloud service (OpenAI, Gemini Pro, DeepL, Zhipu/ChatGLM, Baidu, Tencent, Volcengine, Youdao, Yandex, and more) is configured in Service Settings with the user's own API key, and v3.0+ allows multiple instances of the same service with different keys/configs. The built-in OpenAI service reads a user-supplied requestPath (custom domain/base URL), apiKey, and model, and supports both OpenAI and Azure modes, so it can target any OpenAI-compatible endpoint (e.g. DeepSeek, OpenRouter, local servers). Ollama is supported for fully local/offline models. An extensible .potext plugin system lets users add additional translate/OCR/TTS providers with their own API key and parameters. Actively maintained (latest pushes June 2026; 3.0.7 release), ~18.8k GitHub stars.
Why this trust score (82/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 11/15: Local-first: it works without sending your data anywhere.
- 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-07-04, about 1 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.
Setup
Open settings, paste your provider API key, choose a model, and start. The key stays on your device.