transglot keeps the text of your product translated: you push your source strings once, it translates them with AI and with your own past translations, your team reviews what needs reviewing, and the finished locales go back out to your app.
Who this is for
Everyone. This is the shape of the whole product; every other article is a detail inside it.
What happens next
The work moves through four stages, and every screen in transglot belongs to one of them.
Content in. A project holds your source strings and every translation of them. Strings arrive from your codebase over the command line or the API, from a connected code repository, from a content platform, or from a file you import. You tell the project which source language it is written in and which languages you want to ship.
Translation. Missing strings are translated with AI, guided by your glossary and your brand voice. When the exact same source text has been translated before, transglot reuses that translation at no cost instead of translating it again. Everything lands in the editor, where your team can change anything.
Quality. Automatic checks look for broken placeholders, wrong plural forms, length overflow and glossary conflicts. A quality score and a list of findings tell you where the risk is. Screenshots let a reviewer see a string in the place it actually appears.
Delivery. Finished locales are published to a CDN your app reads at runtime, pushed back to your code repository, or pulled down by the command line into your build.
Related
Your dashboard
Create your first project
Setup steps