Words translated on Lingo.dev:229,938,97857 # The Localization API. Pre-editing. LLM translation. Qualified human review. Back-translation. Quality scoring. One API call. [Read the API Docs](/content/en/docs/api/index.html) [Talk to a Localization Expert](https://cal.com/team/lingodotdev/talk) Trusted by fast-growing global companies Platforms ## Multi-Tenant Localization Infrastructure. Add localization to your product with isolated context per user, per project, or per product. Provision via API, let your customers configure quality, track consumption for billing. ### Ship Localization as a Feature Provision isolated localization per user, per project, or per product with a single API call. Your customers get translation without leaving your product. ### Translations Match Each User's Voice Glossary, brand voice, and model selection isolated per user. You decide what to expose and what to configure behind the scenes. Their content, their voice - at any scale. ### Monetize Per User Token consumption tracked per user with per-model cost breakdowns. Build localization into your pricing tiers, or pass through at cost. Usage scales linearly with your platform. > “Developer experience is everything in developer tools. Lingo.dev nails it - they've turned complex localization into a few lines of code.” Paul Copplestone CEO & Co-Founder, Supabase ## What Happens Inside A Localization Engine. A localization engine is a stateful translation API. It remembers your glossary, brand voice, and model config across requests. When you call it, every step runs in sequence. Each step is configurable. 1 ### Source Refinement An LLM pre-processes the source text before translation. Resolves ambiguous references, normalizes concatenated strings, and flags placeholder syntax issues. Prevents the garbage-in / garbage-out problem at the source. 2 ### Context Enrichment Cosine similarity over vector embeddings matches source terms to glossary entries. Per-locale brand voice profiles inject tone and formality. Locale-specific instructions handle date formats, number separators, and currency conventions. 3 ### LLM Translation The model receives enriched context: glossary matches, brand voice profile, instructions, and the source text. Translation happens with the full context of your product, not in isolation. 4 ### Human Post-Editing Optional step, managed entirely behind the API. Our network of qualified translators reviews LLM output when your quality rules require it. Useful for regulated content, legal copy, or high-visibility launches. You configure the trigger - we handle the rest. 5 ### LLM Post-Review A second, independent model evaluates the human-edited translation. Boolean checks for tag preservation. Percentage scores for fluency and naturalness. Catches inconsistencies that single-pass review misses. 6 ### Delivery Results arrive via webhook with HMAC signature verification, or stream over WebSocket for real-time UIs. Each locale completes independently. > “Lingo.dev's approach reminds me of how Stripe revolutionized payments - making a complex process invisible to developers.” Pete Koomen Group Partner, Y Combinator Quality ## Every Translation Scored and Verified. Cross-model quality scoring, glossary enforcement, and human review when it matters. Quality you can measure, not just hope for. ### Automated Quality Scoring Cross-model evaluation: one model translates, a different model scores. MQM dimensions for fluency, accuracy, terminology, and style. Per-locale trends and regression alerts in the dashboard. ### Glossary and Brand Voice Lock terminology across locales. Configure tone and formality per language. 'Workspace' stays 'Workspace' in every translation. Each locale gets its own linguistic profile. ### Human Review When It Matters When a score drops below your threshold, the translation routes to our network of qualified translators behind the API - without vendor management or manual handoff coordination. > “With Lingo.dev, Dutch reads naturally, Russian fits our UI perfectly, and our brand voice stays consistent.” Sebastiaan van Leeuwen Product Manager, Truely Developers ## Integrate in Minutes. Your localization team configures quality rules. You call the API, run the CLI, or add the GitHub Action. [5,402 stars](https://github.com/lingodotdev/lingo.dev) [3,884 members](https://discord.gg/rJ8zGYJQj5) Official GitHub Technology Partner [**Lingo API** \\ \\ Translate via HTTP. Synchronous and asynchronous modes with webhook delivery.\\ \\ Read the docs](/content/en/docs/api/index.html) [**Lingo React MCP** \\ \\ AI agents configure engines and translate directly in your IDE.\\ \\ Read the docs](/content/en/docs/react/mcp/index.html) [**Lingo CLI** \\ \\ First translated build in 4 minutes. 14 file formats supported.\\ \\ Read the docs](/content/en/docs/cli/index.html) [**Lingo GitHub Action** \\ \\ Every push triggers translation. PRs include localized strings.\\ \\ Read the docs](/content/en/docs/integrations/index.html) + > “Just like Dependabot made package updates effortless through automation, Lingo.dev is doing the same for localization.” Grey Baker Creator of Dependabot Enterprise ## Professional Localization, Delivered As Infrastructure. The full professional localization workflow - source pre-editing, retrieval-augmented translation, human post-editing, AI quality gates - encapsulated behind a single API. SOC 2 Type 2 audited. Engineering ### Professional localization pipeline Source pre-editing, context enrichment, LLM translation, human post-editing, AI quality gates, and delivery - orchestrated behind a single API call with per-locale failure isolation. ### Retrieval-augmented translation Glossary terms matched by semantic similarity via vector retrieval, with brand voice and product context pulled automatically from your engine's state. ### Stateful localization engines Your engine accumulates glossary, brand voice, translation memory, and model configuration across requests - context persists and improves with every job. Localization ### Centralized governance Localization team defines glossaries, brand voice, quality thresholds, and review checkpoints per engine - product teams self-serve through CI/CD. ### Quality and cost reporting Per-engine dashboards with quality scores, token consumption, glossary coverage, change rates from GitHub commits, and per-model LLM cost breakdowns. ### Team autonomy Translations arrive in pull requests - Localization team owns governance and quality standards while localization scales without proportional team growth. Security ### SOC 2 Type 2 Audited security controls with encryption at rest and in transit, DPA available on request. ### Data encryption AES-256 at rest, TLS in transit, API keys hashed at the application layer, with data residency options for EU and US regions. ### 99.9% Uptime SLA Multi-region infrastructure with ranked model fallback chains protecting against individual provider outages. [Talk to a Localization Expert](https://cal.com/team/lingodotdev/talk) SOC 2 Type 2/99.9% Uptime SLA/GitHub Technology Partner/Dedicated Support ## Create Your First Localization Engine. One API call. Glossary, brand voice, model config, quality rules - all encapsulated in a stateful engine that improves with every job. [Read the API Docs](/content/en/docs/api/index.html) [Talk to a Localization Expert](https://cal.com/team/lingodotdev/talk) ### Platform [Localization API](/content/en/docs/api/index.html) [Async Jobs API](/content/en/docs/api/localization/index.html) [Localization Engines](/content/en/docs/platform/index.html) [Language Detection](/content/en/docs/api/recognize/index.html) [Lingo.dev Platform MCP](/content/en/docs/platform/mcp/index.html) [Pricing](/content/en/pricing/index.html) ### Developer Tools [Lingo React MCP](/content/en/docs/react/mcp/index.html) [Lingo CLI](/content/en/docs/cli/index.html) [Lingo GitHub Action](/content/en/docs/integrations/index.html) [Lingo React Compiler\\ Alpha](/content/en/docs/react/compiler/index.html) ### Resources [Documentation](/content/en/docs/index.html) [Guides](/content/en/guides/index.html) [Changelog](/content/en/changelog/index.html) [Languages](/content/en/languages/index.html) [LLM Models](/content/en/models/index.html) ### Company [Blog](/content/en/blog/index.html) [Research](/content/en/research/index.html) [Enterprise](https://cal.com/team/lingodotdev/talk) [Careers\\ Hiring](/content/en/careers/index.html) [humans.txt](/content/humans.txt) ### Community [GitHub](https://github.com/lingodotdev/lingo.dev) [Discord](https://discord.gg/rJ8zGYJQj5) [Twitter](https://x.com/lingodotdev) [LinkedIn](https://www.linkedin.com/company/lingodotdev) HQed in San Francisco + worldwide SOC 2 Type 2·CCPA·GDPR Backed by \\ Combinator](https://www.ycombinator.com/)& \\ Initialized Capital](https://initialized.com/)&our customers [Privacy](/content/en/legal/privacy/index.html)· [Terms](/content/en/legal/terms/index.html)· [Cookies](/content/en/legal/cookies/index.html)· [security.txt](/content/.well-known/security.txt) © 2026 Lingo.dev (Replexica, Inc). [All systems normal](https://status.lingo.dev/)