Lingo.dev v1.0 introduces localization engines stateful translation APIs that you configure once and call from backend code, MCP, or CI/CD. Before today, every team that wanted consistent terminology, on-brand tone, and per-locale rules wired it up by hand: a glossary in one repo, brand-voice notes in a Notion doc, prompt scaffolding hard-coded into the app. The engine collapses all of that into a single addressable thing.
What's in the launch
Localization engines. Configure models, brand voice, instructions, and glossaries per locale.
LLM models. Pick the model per locale, with ranked fallback chains for reliability.
Brand voices. Linguistic rules and tone per locale.
Instructions. Per-locale translation rules for specific patterns.
Glossaries. Lock down product terminology across languages and builds.
AI Reviewers. Cross-model evaluation criteria for translation quality.
Playground. Test engine configurations before they go live.
Reports. Word generations, token consumption, top locales, glossary coverage, change rates.
Engine provisioning is an async API that takes a fresh engine plus a few URLs or content samples and auto-configures the brand voice, glossary, and instructions for you. Multi-step manual engine setup collapses into one call.
The Localization Jobs UI lands end-to-end. Inspect job groups, watch per-language progress, see the source payload, see the webhook delivery, drill into any failed locale. The async localization API ships jobs in parallel across every target locale, retries on failure, and webhooks back when done now you can watch it happen instead of reconstructing from logs.
The async localization API fans out a single localization request across every target locale in one POST and delivers results via webhook. Source payload in, job IDs out, webhook fires per locale as each finishes.
Also shipped
Glossary CSV upload. Bulk-import glossary items from CSV with conflict resolution on collision, so re-imports don't duplicate entries.
Jira and GitHub now connect over OAuth. Both integrations switched off API-token setup.
The triage workflow reads any Jira ticket about a bad translation, looks at the offending output, and proposes the actual fix in the engine config: a glossary item to add, an instruction to tighten, a model config to adjust. Review the suggestion, accept or edit it, and the engine is fixed for every future translation not just the one that was reported.
Also shipped
AI Reviewers now receive the same context the localizer saw. Brand voice, instructions, and glossary items reach the reviewer prompt, so scoring aligns with the engine's actual configuration instead of evaluating in a vacuum.
Review filters in translation logs. Filter the translation logs by reviewer and score threshold e.g. any reviewer below 80%, or a specific reviewer below a given percentage.
Today, we're introducing Lingo.dev Compiler: an npm library, that lets you build multilingual React apps without having to rewrite the existing React code.
It doesn't require extracting i18n keys, or wrapping text in tags. 100% free and open-source.
