Lingo.dev
Day 5 after signup
Announces that users can connect their own model provider keys for localization and explains how billing, setup, and fallback behavior work. It also highlights other recent product updates and links to setup guides and the changelog.
Lingo.dev
Day 5 after signup
W42 Product Update: Bring your own model provider keys
Pay your model provider directly for translation tokens, with localization still running on Lingo.dev.
How it is built
Bring your own Anthropic, OpenAI, Google, or Mistral AI key for localization. Requests go directly to the provider on your key, and the provider bills you for those tokens. Open Settings → BYOK, add your provider key, and choose that provider’s models in your localization engine. Your key is used for the engine’s translation and editing steps. Your integrations keep using its glossary, rules, and brand voice, while Lingo.dev runs the localization infrastructure. If a model is unavailable on your key, it can run on Lingo.dev’s key and your credits instead. Read the Bring Your Own Key guide for setup and model routing details. If BYOK isn’t available on your plan, reach out to the Lingo.dev team. Also shipped Retranslate selected strings from a pull request. Use /lingo translate --key "button.label" to update a key while keeping other translations. Add --context "button label, keep sentence case" to guide that run without changing saved engine rules. GitHub App guide. Use JSONC comments as translation hints. See translator notes. Read the full changelog → The legacy CLI doesn’t support all the features of the new CLI, including your engine’s configured localization pipeline. Reach out to the Lingo.dev team for help migrating. – Veronica Lingo.dev · San Francisco, CA Unsubscribe