One translation management system. Six products. Zero broken strings.
glossa
One translation management system. Six products. Zero broken strings.
Everything between the string a developer writes and the sentence a customer reads: the engine that translates it, the workspace your team reviews it in, the checks that refuse a broken row, and the delivery that ships a fix without a release. All of it on one plan.
Everything between the word you type and the word they read.
Automatic translation
One engine, two speeds. Everything is drafted the moment the English moves; the strings your brand lives on get the careful pass. Your glossary and your plural rules go in before it writes a word.
The translation workspace
Every string, every language, and the history of who changed what. Four roles with per-project and per-language grants, on every plan including Free.
- A grid that stays quick past ten thousand rows
- Per row context rail: screenshot, key, history
- Saved views and fuzzy search
- Plural editor, per language rule set
- Inline suggestions from Glossa
- Two person approval on the strings that matter
Quality checks and repair
Four checks run on every row before a model is asked anything. What fails is repaired once, re-checked, and then held rather than shipped.
In-context editing
Hold ALT, click any text in your running app, and fix the wording where it sits. The key in the page cannot write, so a leaked bundle cannot rewrite anything.
Integrations, API and CLI
Whatever your content lives in, it reaches here and goes back. There is no private API: the dashboard is a client of the same v1 you get, and all 41 integrations are included rather than sold.
- REST v1
- CLI
- GitHub Action
- MCP · 16 tools
- 12 webhooks
- 20 formats
- Shopify
- WordPress
- Contentful
- Figma
- Lokalise import
- Phrase import
- Crowdin import
- 41 integrations · $0
Over-the-air delivery
Fix a typo in Japanese without an app store review. A published correction is live inside the minute, and the last 20 versions stay pinnable.
It already works with the 41 tools you use.
Your CMS, your shop, your repository, your help desk, your design files. Thirty-two of the forty-one sync both ways, which means a reviewed translation is written back where it came from without anyone exporting a file. Nine are import only, because their API cannot take a translation back, and the card says so rather than promising a publish. Every one of the forty-one is included: there is no per-connector fee on any plan.
Each connector signs in with your own provider credentials. Drafts ride the same four gates as code strings, and reviewed locales publish back wherever the provider API allows it.
WordPress
Posts, pages and registered meta, over your own site credentials.
Contentful
Entries synced per locale, reviewed locales published back with your own token.
Shopify
Products, collections and pages, synced per locale on your store.
Zendesk Guide
Help centre articles kept in step per locale, with structure held.
Notion
Pages and databases. Locale drafts land as siblings, because the API cannot take them back.
Confluence
Space by space docs import with structure held, tracked per locale.
Frames per locale for design review, pushed back as variables so a translator never opens the design tool to fix a word.
Figma
Frames per locale for design review, pushed back as variables.
Sketch
Text layers pulled per locale and written back into the document.
Adobe XD
Artboard copy per locale, so expansion shows up at design time.
Repo hosts, issue trackers and the automation bridge. Five of the six need the Team plan; the automation bridge does not.
GitHub
Every push drafted, with the locales landing in one sync pull request.
GitLab
Merge requests carry the drafted locales, and say when a run came up short.
Bitbucket
Pull requests drafted on push, and an incomplete run says so in the body.
Azure Repos
The same push to draft loop inside Azure DevOps.
Jira
Refused rows become issues that link straight back to the row.
Zapier, Make and n8n
The automation bridge, driven by the same 12 webhook events.
Nobody has to do anything for this to happen.
One person changes one English string. Everything below runs on its own, and the first time anybody looks at it is when they choose to.
- 01$
You change a string
A commit, an edit in your CMS, a word fixed on the live page. Whatever moved is the brief. Nothing to export, nobody to email.
- "Pay with confidence"+ "Pay securely, in seconds" - 02Fx
Every language is written
Not one after another: all of them at once, with your glossary, your past approved translations and the screen the string renders on already in hand.
frjadeesarptkoit - 034x
Every row is checked
Four checks run on every translation before a human sees it: placeholders, plurals, glossary and length. One fails, it is repaired and re-checked. It fails again, it is held rather than shipped.
placeholderspluralsglossarylength - 04OK
It goes back where it came from
The pull request, the file in your repository, the connector it was pulled from, or the edge bundle your app fetches. You did not move a file in either direction.
→pull request→your repo→the connector→edge bundle
Real numbers, counted from the code.
ICU locales the validator accepts. There is no fixed language list to run out of. Source: the ICU locale table.
CLDR plural languages, Arabic and its six categories included. Straight from the CLDR plural tables.
formats that round-trip natively. Seven of them carry plurals. Read from the format registry.
connectors, design plugins and apps. Thirty-two sync both ways. Read from the integration catalogue.
events your own systems can subscribe to, from batch.completed to source_drift.repaired. Read from the event catalogue.
deterministic checks on every row: placeholders, plurals, glossary and length. Source: QaRunner::preGate().
Resources to get you started.

A first multi-locale launch
Sequencing, right to left, pricing pages and support load, in the order a first launch meets them. The outline is published while the book is written.

The locale reference
Every locale the validator accepts, how a tag is canonicalised, and which languages carry their own plural rule set.

The lexicon
The whole product set read as a dictionary entry: senses, a conjugation table and specimen plates.