Skip to content
transglot.platformStart free
the platform

Everything Transglot does, on one board.

Automatic translation, enforced glossaries, four quality gates on every row, a memory that stops you paying twice, twenty file formats and an editor that works on your live page. Each tile below links to the page that takes it apart.

Start for freePricing
the board

Memory, glossaries, formats and the checks between them.

seven pieces of the platform under the editor. Every tile does something when you touch it, and every tile links to the page that explains it.

Memory that stops you paying twice

Every approved translation is kept and searched before anything new is generated. A sentence you settled last quarter comes back exactly as you settled it, and an exact match skips the AI call, so it costs nothing.

  • exact match reuse
  • fuzzy leverage bands
  • provenance ranked
  • per project opt out

No fixed list of languages

There is no language list to run out of. Any standard language tag is accepted, which is 708 locales in ICU today, and plural forms come from the 224 languages CLDR has plural rules for.

  • fr-FR
  • ja-JP
  • ar-EG
  • pt-BR
  • ko-KR
  • de-CH
  • hi-IN
  • uk-UA
  • tr-TR
  • nb-NO
  • th-TH
  • he-IL

Four gates, every row

Placeholders, plural forms, glossary terms and length, checked on every row of every run. A row that fails is repaired once and re-checked. Fail again and it is refused rather than shipped.

Any repository

The CLI reads twenty formats.

$ npx transglot push
diff: 1 key changed
gates: 4 of 4 pass

Glossaries that are enforced

Your terms go into the prompt before the draft is written and are checked again after it. Mark a term do not translate, forbid a target word, or set one preferred word per language.

  • do not translate
  • forbidden targets
  • per language

Your AI agents can drive it

Sixteen MCP tools and twelve webhook events, on the same verbs and behind the same gates as everything else.

agent which keys fail length in de?
mcp 3 keys, re-drafted
mcp gates 4 of 4 pass
20

file formats

Round-tripped natively, with comments and placeholders intact. Seven of them carry plurals.

in the product

One project screen, everything on it.

How far each language has to go, the engine settings, tokens, webhooks, the glossary and the style guide. One page per project.
A project overview: keys, translated share, needs-review count, the languages with their progress rings, and the settings for auto-translate, quality mode and memory.
auto-translate · quality mode · memory
one page per project
live editor

Fix the words on the live page.

Alt click a string in your own running app, edit it where it renders, and commit. Placeholders, plurals and length are checked in the overlay as you type, and the row you commit is versioned, attributed, and left alone by every later run.

Start for freeHow in context editing works
Before
After
Screenshot the bad wording
Alt click the string in your own app
File a ticket against the repository
Edit it in the rendered component
Wait for a release to see it fixed
Commit it there, versioned and attributed
Discover the placeholder went missing
Placeholders and length checked as you type
checkout.pay_now
fr-FRcheckout screenillustrativedemo

Order summary

Payer maintenant
This card runs entirely in your browser.
  • v41Payer maintenantreviewer, 2 days ago
  • v40PayerGlossa Flux, 6 days ago
Nothing is sent anywhere. This card is a local demonstration of the editor, not a live project.
what to call each part

What each part is called, and what it owns.

the board above is what each part does. This is what each part is named, which is the half you need when you describe it to somebody else.
free to start

Your first 100,000 words are on us.

Upload your source file in the browser and watch the first run draft, check and repair itself. No card, and no sales call to book first. The CLI, the GitHub Action, the API and the MCP server all run on a project token, which starts at Starter.

CLIGitHub ActionREST APIMCP server

FAQs

The questions people ask on their way through the board.

It translates the text in your product into every language you have added, automatically, and checks each row before it ships. Strings come in from your repository, a connector or a file upload. Translations go back out through the API, the CLI or a delivery bundle, in the same format they arrived in.
No. It reads the string files you already have, in the format you already use, and writes them back the same way. If you want translations delivered at runtime instead of committed, there are framework SDKs for that, but nothing forces the change.
Twenty, round-tripped natively: JSON, XLIFF, PO, Android XML, iOS strings and stringsdict, Xcode string catalogs, Flutter ARB, YAML, properties, CSV, XLSX and the rest. Seven of them carry plurals, and comments and placeholders survive in both directions.
There is no fixed list. Any standard BCP-47 language tag is accepted, which is 708 locales in ICU today, and 224 of those languages have their own CLDR plural rules that the plural gate enforces. Right to left scripts are handled as part of the same path.
Yes. The GitHub Action drafts every changed string on a push and puts the translations in the same pull request, and a status check blocks the merge if a row failed one of its gates. GitHub, GitLab, Bitbucket, Jira and Azure Repos are the five connectors that start at Team; the other thirty-six are on any paid plan.
Yes, in the grid or on your own live page, and the engine will not write over it afterwards. A row a person edited or reviewed is left alone on every later run, so a wording decision stays made.
Before a string is translated it is looked up in memory, and an exact match is served instead of being generated, which skips the AI call and costs nothing. Exact matches come from one shared pool that carries no owner and can be switched off per project on every plan; a reviewed entry stays inside your organization. Runs are also diff aware, so a file nobody changed is not re-translated.
Yes. Glossary terms go into the prompt before the draft is written and are checked again after it, so a locked term is enforced rather than suggested. You can mark a term do not translate, forbid a target word, and set one preferred word per language, plus a style guide per language.
Four gates run on every row of every run: placeholders survive, the target language gets every plural form it needs, glossary terms hold, and the text still fits the component it renders in. A row that fails is repaired once and re-checked. Fail twice and it is refused and held for review rather than shipped.
Yes, plus a CLI, a GitHub Action, twelve signed webhook events and an MCP server with sixteen tools for AI agents. All of them authenticate with a project token, which is available from the Starter plan.
Free is $0 forever. Starter is $19 a month, Team $49 and Business $149, each with a larger word allowance. Past the allowance, paid plans meter at $0.0008 a word, which is $80 per 100,000 words, against a spend cap you set.
Yes, and it does not expire: 100,000 words to start and 10,000 a month after, one project, 15 language rows including your source, three seats, no card. It is a hard cap rather than a meter, so it cannot bill you. Free cannot mint a project token, so the API, CLI, Action, webhooks and MCP server start at Starter.
works with what you already run

41 connectors, already built.

All 41 integrations
your turn

Put the whole board to work on your own strings.

Import a file or connect a repository, and the first run drafts, checks and repairs itself while you watch.

Start for freeSee pricing
Free plan: 100,000 words to start and 10,000 a month after, 15 locales per project including the source, three seats. It is a hard cap and cannot bill you. Paid plans meter overage at $0.0008 a word.