What a translation management system is.
The category has an ugly name and a simple job: keep every language of your product saying the same thing as the source, without a person remembering to make that happen.
The short answer
A translation management system is where the sentences in your product live once they leave the code. It holds the source text, every translation of it, and the rules that govern them — which terms never change, which must be translated one exact way, what tone to use in each language. Software pushes strings in and pulls translated files back out, so the codebase keeps its own format — YAML, JSON, PO, .strings — and nobody edits a language file by hand. The reason to buy one is rarely the first translation. It is the fiftieth change to the source afterwards.
The loop, in four moves.
1. Strings leave the code
A script tag, a build step, an API call or an AI assistant reports the sentences your product shows. Each one gets a key, and the key is what everything else hangs off.
2. The rulebook applies
A glossary fixes the terms you always translate the same way. A do-not-translate list protects product names. Substitutions catch the things a model gets wrong twice. Translation memory means a sentence you have already approved is never paid for again.
3. The translation happens
A model drafts inside those rules, a person reviews what matters, and both leave a trail. The useful question about any tool here is not whether it uses AI — they all do now — but whether the rules bind it on every run or only when someone remembers.
4. Files come back
Translations return in the format your build already reads, so the app does not learn anything new. Whether they are served from the vendor or shipped inside your own deploy is the difference that decides whether your pages can rank.
The source text moves. That is the whole problem.
A one-off translation is a purchase. Keeping seven languages true to a page you edit on a Tuesday is a process, and a translation management system exists to be that process so a person does not have to be. When you compare tools, compare what each one does on the day the English changes — not on the day you install it.
What to ask before you shortlist.
Does it give each language its own URL?
Browser-side translation makes a site readable, not findable. If ranking in the new market is the point, the tool has to produce a page a crawler can fetch.
What is the price counting?
Words, pageviews, seats and languages are four different meters, and they behave very differently as you grow. Ask what happens to the bill when you add a language, not just when you add a page.
Can you leave with your words?
Your translations are content you paid for. Check that you can export every language in a standard format on the day you decide to go elsewhere.
What does BeMyWords cost?
Free to start: 5,000 words stored, 1 site, no card. Paid tiers open at 199 kr a month — 1,990 kr for a year — and are counted on words stored — the source plus each translation of it — never on seats, pageviews or a cap on how many languages you run. Bring your own AI key and it is 199 kr a month flat with no word limit.
Every tier, and what it holdsOr skip the reading and watch it happen.
Free to start, no card. Point it at a site and the first language is done before the shortlist is.
Start free