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.

You can now send translations to human review only when they re in a language you select and score below your quality threshold. All others continue without human review.

Keep human review to selected languages

You could already use a quality threshold to send low-scoring translations to human review. Now you can narrow that rule to selected languages within the same localization engine.

For example, when introducing Japanese or working through terminology issues in German, you can send low-scoring translations in those languages to a reviewer. Translations that meet your threshold continue automatically, and your other languages skip human review.

You can now connect content sources to your localization engines in Studio, translate content with your team's glossary, rules, and brand voice, and write translations back to your repositories, CMSs, or help centers.

Connect GitHub, Payload CMS, or Zendesk Help Center, or submit content through the CLI and API. Each source uses the localization engine you choose, with your team's glossary, rules, and brand voice. Product and content teams submit content from their own tools, while the localization team runs the localization infrastructure.

The CLI. Engineers use lingo push to submit source files through the localization engine's configured pipeline. lingo pull writes the completed translations to local target files on the same machine and checkout. Studio lists each submission with its status by language.

The GitHub App. When source files change on the default branch, the app translates the changes and opens a pull request with the translated files. Enable the pull request workflow to commit translations directly to a pull request branch. Require approval before automatic runs, or use /lingo translate to request specific files and languages.

Localization infrastructure is now in one place.

Infrastructure is where you configure localization engines, models, context, pipelines, and everything else that controls how your content gets translated.

Here's what you'll find there:

Localization engines. Create separate localization engines for different kinds of content. Your product UI, help center, and legal content can each have their own setup, models, context, and localization pipeline.

We just shipped the Inbox.

The Inbox is one place for localization work that needs a human.

The new Lingo.dev is here, and it is live for every organization.

Lingo.dev is completely redesigned around the way you work, so everything now has a clear place, across five areas:

• Home  your starting point: a quick read on recent activity.

• Infrastructure  where you build your localization engines: the models, glossaries, rulesets, and brand voices you configure once and reuse everywhere.

• Studio  where localization connects to the tools you already use: the GitHub App, a Zendesk Help Center, a Payload CMS, plus the CLI and the API.

• Queue  one inbox for everything that needs a person: human review, localization engine suggestions, and triage, in a single list you filter and save as views.

• Observability  where you see whether the output is good, even in languages you cannot read: reports, AI reviewers, and a log of every review beside the translation it scored.

This is the foundation for everything we build next, and the new home for your localization work.

You can now retranslate specific pieces of your content, down to a single key.

The Lingo.dev CLI command lingo push retranslates only the source text you edited. But some changes happen in your localization engine, not your files: you switch the model, add glossary terms, or edit your rules. Your source stays identical, so lingo push finds nothing to redo. Now you can retranslate the exact pieces you want, from a single key to a whole language.

Run lingo push messages/en.json --key auth.login and Lingo.dev retranslates only the keys you list. A key is its path in the file, so you can pick one value, a whole subtree, or several keys at once. Everything else stays the same. If you are not sure which keys to list, your AI coding assistant can read the file and write the command for you.

If a change affects more than a few strings, retranslate whole files. Run lingo push src/en/**/*.json --force and Lingo.dev retranslates every string in the files you list. And if one language needs redoing, run lingo purge --locale fr to delete the French files, then lingo push --backfill-missing to translate them again. Your other languages stay the same.

You can now translate your Payload CMS content from Lingo.dev.

The Payload CMS integration connects your Payload instance to a localization engine you host on Lingo.dev. Choose the collections and globals to cover, and Lingo.dev translates their localized fields into your target languages, then writes each translation back to Payload under that locale. Rich text translates as a Lexical tree, so formatting, links, uploads, and block structure survive the round trip and only the text inside is replaced.

Setup is one plugin. Install lingo.dev/payloadcms, add it to your Payload config, and redeploy. Scope, locales, and engine live in the dashboard, so you can change them without touching your config again.

You can now translate your Zendesk Help Center from Lingo.dev.

The Zendesk Help Center integration connects your Help Center to a localization engine you host on Lingo.dev. Choose the categories, sections, and articles to cover, and Lingo.dev translates their titles, descriptions, and bodies into your target languages, then writes each translation back to Zendesk. Article bodies translate as HTML, so links, formatting, and embedded media survive the round trip.

There are two ways to keep your Help Center translations up to date. The first, Sync, translates only the articles you have added or edited since the last run. The second, Retranslate, rebuilds every article in scope from scratch, which is what you want after changing the localization engine's glossary, brand voice, or rules and needing your existing translations regenerated against the new configuration.