Lingo.dev is a localization engineering platform where teams create localization engines: Stateful translation APIs configured with glossaries, brand voice rules, per-locale model chains, and AI quality scoring.
Integrate via API, CLI, CI/CD, or MCP.
This is the 2nd launch from Lingo.dev. View more
Lingo.dev v1
Launched this week
On Lingo.dev, teams configure localization engines: Stateful translation APIs with glossaries, brand voice rules, per-locale model chains, and AI quality scoring, and then call them via API, CLI, CI/CD, or MCP.



Free Options
Launch Team / Built With







Lingo.dev
@Kilo Code, pay.sh by @Solana Foundation, now @Lingo.dev. packed week for the oss ecosystem! lfg
Lingo.dev
@fmerian Lessgo lessgo! 💪
Thanks for chiming in Flo!
Lingo.dev
@lakshminath_dondeti Great questions!
We have internal benchmarks and only after we pass strict standards do we roll out support for a language.
For tone, style and context, you can set it all up in one go and all your future translation requests retain complete context.
Give it a shot!
Indie builder question — at what point in the journey do you think a consumer app should start localizing? English-only right now with our nutrition app but EU is on the radar and I can't tell if it's a 1k-user problem or a 100k-user problem.
Lingo.dev
@ethansharg Great question!
My knowledge about indie apps is limited but I'll say: It's rarely a 1k problem, and waiting until 100k means leaving a lot of growth on the table (like all things, this too compounds). For a consumer app, the sweet spot is usually right after you've nailed core Product-Market Fit (PMF) in primary language.
Brand voice rules and glossaries is the part most translation tools skip. How do you handle the conflict when brand voice wants formal but a locale prefers casual?
Lingo.dev
@ebazan33 brand voice gets preference as it is user defined and the best part is that you only need to set it up once.
Beyond that every subsequent translation request inherits all the context ensuring perfect consistency.
Lingo.dev
@lakshminath_dondeti Thanks for bringing up the mobile view, will resolve soon.
What confused you about the pricing?
Localization but actually built for engineers this time
Stateful translation APIs + AI QA scoring sounds kinda insane.
Wonder how well it handles brand voice consistency across languages tho?
Lingo.dev
@le_ng_c_dan_nhi I’d say just one thing: try it and you’ll be amazed by the consistency