How transglot began
We build the localization platform we wanted to use ourselves — fast, scriptable, and honest about what AI can and cannot do for translation quality
What ships today
AI translation powered by Claude, guided by per-project style guides and brand voice
An in-context editor that captures screenshots of the real UI translators are working on
Glossary enforcement and agentic Translation QA runs
A CLI, a GitHub Action, a REST API, and signed webhooks with delivery logs
File formats, natively supported
00
Building the localization platform we wanted
A commitment to open source and developer ergonomics.
Vision
Translation should never be the reason a release slips.
Mission
Build an open-source, AI-native localization platform that fits a normal engineering workflow instead of interrupting it.
The people behind transglot
We are a small team building in the open. Names, roles, and photos land here as the team grows — until then, the code is the introduction.
Founding team member
Role to be added
Real bio coming soon — this card is a placeholder until the team supplies names, roles, and photos.
Founding team member
Role to be added
Real bio coming soon — this card is a placeholder until the team supplies names, roles, and photos.
Founding team member
Role to be added
Real bio coming soon — this card is a placeholder until the team supplies names, roles, and photos.
Your entire stack — one source of truth
Push and pull strings over a REST API, the transglot CLI, a first-party GitHub Action, or an MCP server your AI agent can call — round-trip twenty native file formats, from i18next JSON to Android XML to XLIFF, and deliver fixes at runtime over the CDN.
