# Notes on localization engineering

Research, architecture, and product notes from building localization infrastructure at scale.

## 2026

- [Apr 21 2026  Blog 7 min read  **Enterprises pay a coordination tax on localization** ](/content/en/blog/multi-team-localization-tax/index.html)
  Managing shared glossaries, aligning terminology across teams, and carrying the cost of ever migrating. An organization-scoped localization engine with retrieval at inference time, and forward-deployed localization engineering from the Lingo.dev team, reduce the tax.

- [Mar 31 2026  Blog 5 min read  **The Localization API** ](/content/en/blog/the-localization-api/index.html)
  Professional localization - source refinement, glossary enrichment, quality scoring, and optional human review - encapsulated behind a single POST. One request, any number of target locales, results via webhook.

- [Mar 14 2026  Blog 5 min read  **Introducing Lingo.dev v1.0** ](/content/en/blog/introducing-lingodotdev-v1/index.html)
  After proving that retrieval augmented localization reduces LLM terminology errors 17-45%, we built Lingo.dev v1.0 - a localization engineering platform where teams create stateful localization engines with per-locale models, glossaries, and quality scoring.

- [Mar 9 2026  Research 10 min read  **Retrieval Augmented Localization Cuts LLM Terminology Errors 17-45%** ](/content/en/research/retrieval-augmented-localization/index.html)
  Raw LLMs translating isolated paragraphs produce 17-45% more terminology errors without a domain glossary. Holistic quality metrics miss this entirely.