Skip to content

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.

Six tiles, six mechanisms, all of them running here on the page. Each one opens on the page that takes it apart.
writes it, in two speeds
Glossa

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.

$ transglot push
flux drafting 9 locales in parallel
ja-JP { name }さん、ようこそ
de-DE Willkommen, { name }
ar-EG أهلاً { name }
glossary held · plurals held · 0 human edits touched
$0.0008 a word past the allowance
holds it, and the people who sign it off
Verso

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
catches what is wrong, and repairs it
Agents

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.

de-DE length 67 > 48 budget
heal re-drafting inside the budget
de-DE length 41 pass
shipped · 0 broken strings
proves it on your real screen
Overlay

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.

carries it in and out
Backbone

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
ships it without shipping a release
Dispatch
60s

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.

apps and integrations

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.

41 in the marketplace

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.

two way

WordPress

Posts, pages and registered meta, over your own site credentials.

planAny paid plan
two way

Contentful

Entries synced per locale, reviewed locales published back with your own token.

planAny paid plan
two way

Shopify

Products, collections and pages, synced per locale on your store.

planAny paid plan
two way

Zendesk Guide

Help centre articles kept in step per locale, with structure held.

planAny paid plan
import only

Notion

Pages and databases. Locale drafts land as siblings, because the API cannot take them back.

planAny paid plan
import only

Confluence

Space by space docs import with structure held, tracked per locale.

planAny paid plan
Twenty-six more, including WooCommerce, Magento, PrestaShop, Drupal, Prismic, Kontent.ai and Contentstack.
Every connector
how it works

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

in the open

Real numbers, counted from the code.

Every figure below is counted from what this release ships: the ICU locale table, the CLDR plural data, and the enums and config in the repository.
locale coverage01
708

ICU locales the validator accepts. There is no fixed language list to run out of. Source: the ICU locale table.

plural rules02
224

CLDR plural languages, Arabic and its six categories included. Straight from the CLDR plural tables.

file formats03
20

formats that round-trip natively. Seven of them carry plurals. Read from the format registry.

marketplace04
41

connectors, design plugins and apps. Thirty-two sync both ways. Read from the integration catalogue.

webhook events05
12

events your own systems can subscribe to, from batch.completed to source_drift.repaired. Read from the event catalogue.

the gates06
4

deterministic checks on every row: placeholders, plurals, glossary and length. Source: QaRunner::preGate().

Resources to get you started.

Watercolour of a tree canopy against a deep blue sky.
still being written

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.

Watercolour of a baroque dome against blue sky with a tree in the foreground.
live now

The locale reference

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

Watercolour of leaf shadows falling on a sunlit plaster wall.
live now

The lexicon

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

works with what you already run

41 connectors, already built.

your turn
100,000 words to start, then 10,000 a month

Open your next market.

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, never a meter. Paid plans meter overage at $0.0008 a word.