The localization engineering platform
Words processed on Lingo.dev:
Measure translation quality in languages you can’t read
The criteria you define score translations from LLMs and from native speakers. You know the quality of every language, and translations go live only at the quality you demand.
- Define your own quality criteria in plain words, bring the quality scorecard you have, or start from a template built for your content type.
- Find out the reason for every low score, and trace the error to the model, the translation rule, or the missing glossary term.
- Reduce the native speakers’ edit rate and edit distance over time, and fix low-scoring languages with the translation rules Lingo.dev drafts from manual edits.
“The knowledge stays with us – what quality looks like, what needs translating, for what audience. When we hand the boring parts to AI localization infrastructure, we solve important problems faster.”
Build your own localization engine around any LLM
Retrieval augmented localization selectively sends context to the LLMs, and native speakers’ corrections auto-tune the localization engine. You decide how your brand sounds, and translations read the way a native speaker of the language expects.
- Assign the highest-scoring LLM per language pair, with a fallback order, on your own LLM provider API key or through Lingo.dev without markup.
- Import the glossary and translation memory from the tools you used before, pick a template built for your industry, or start blank.
- The localization engine applies glossary terms and do-not-translate rules by meaning, in the grammatical form the sentence needs.
“Now our engineers don’t even think about localization. They just build features, and translations happen automatically in 36 languages.”
Integrate localization into the tools you already use
An edit in the code repository or in the CMS starts a localization pipeline, Lingo.dev translates the change, and the translation returns to the source of truth. You keep your current workflow, and continuous localization runs in the background.
- Connect the code repository, the CMS, the help center, and the email provider through native integrations, without writing code.
- Reach the localization engine from your code through the official API, and from the terminal or CI through the CLI.
- Reuse the same localization engine for all your content, so your style stays the same, or build several, one per project.
“We used to constantly worry about keeping translations in sync. Now we just build features, and localization happens automatically.”
Proofread translations with native speakers
Your localization engines send translations to native-speaking proofreaders, and the translations go live after the official sign-off. Available as an add-on.
- Decide what requires proofreading, by content type, by locale, or by a score threshold you set, for pipelines started from your integrations, the API, or the CLI.
- Assign a teammate who reads the language as the proofreader for a locale, so the pipeline waits for the teammate’s sign-off.
- For the languages nobody on your team reads, Lingo.dev supplies professional translators from a partner agency, available 24/7 as a step in your localization pipeline.
“Dutch reads naturally, and our brand voice stays consistent.”
