Every string in every language, on one screen.

The context to translate each one, the checks that caught what was wrong, and the people who sign it off. All of it sits on the row.

Start for free Open the workspace

verso

strings in a project: no cap
strings in a project
reviews on a row: no cap
reviews on a row
locales the validator accepts: 708
locales the validator accepts
progress, while the run happens: live
progress, while the run happens

Everything your team does to a string, without leaving the row.

Nobody leaves the row to find out why a string is wrong, and the roles and grants that gate who may change it ship on every plan including Free.

the row

checkout.pay_now

Everything about a string, on the string.

The screenshot, the key, the gates, who touched it last, and the button to put it back.

en-US Pay now

de-DE Jetzt bezahlen v42

gates 4 of 4 · length 41 of 48

review requested · reviewer

approved · second person · shipped

the grid

10k

rows, and no spinner

Virtualised, keyboard first, fuzzy search, saved views. Find the row, fix the row, move on.

roles and grants

Free included

Four roles on every plan.

Owner, admin, developer, translator, then per project and per language grants over them. Most of the field sells this as Enterprise.

on the row

What never leaves it.

comments and mentions
version history
revert
plural editor
inline suggest
two person approval

vendors

Assign a locale to an outside team.

They see their rows and nothing else, and their work goes through the same gates.

saved views

The views a team actually keeps.

the translation workspace

Every string, every language, edited from the keyboard.

live, not a screenshot: arrows or j and k move, e edits, enter saves, / finds, a approves. Change a row and the four gates run on it

acme / checkout

12 rows · 2 need review · 1 stale

keysourcetargetstategates

contextcheckout.cta

where it renders

Jetzt {amount} bezahlen

23 / 24 · de-DE

history

v42Jetzt {amount} bezahlenMira, 2 d

v41Zahlen Sie jetzt {amount}Glossa Flux, 6 d

comments

@théo the button is 48px wide on mobile, keep it under 24

↑ ↓ or j k movee editsenter savesesc cancels/ findsa approvesdouble-click edits

Twelve fixture keys running in your browser. The grid, the views, the gates and the two-person rule are the shipped ones.

working together

A developer, a marketer and an outside translator, on the same project, without standing on each other.

Roles, and per project and per language grants, are on every plan including Free. Most of the field sells that as Enterprise. The two-person approval rule, where the last two stamps have to come from different accounts, turns on from the Team plan.

drafted

Glossa Flux

suggested

inline, on the row

reviewed

one person

approved

a second person

shipped

attributed, revertable

Give one person one language

An outside translator can be granted French and nothing else. They never see the rest of the project, and you never make a copy of it to send them.

Two people, or nobody ships

Turn the rule on for the workspace and the last two stamps have to come from different accounts. A machine draft still needs a human to sign it off, and nobody can approve wording they wrote themselves.

The argument stays on the string

Comment on the row, mention the person who knows, and the whole thread stays attached to that string instead of scrolling away in a channel.

Every change has a name on it

Six months of versions, each stamped with who wrote it, and revert is one click. Nobody has to reconstruct who changed the checkout copy.

every stamp is a row in the version history, and any of them can be reverted

The small things that make a long day shorter.

Every item below is a shipped behaviour of the workspace, not a roadmap.

Never touch the mouse
Move, edit, save and jump to the next untranslated row from the keyboard. The grid is virtualised, so ten thousand rows scroll at the same speed as ten.
Find the row you half remember
Search across the key, the English and the translation at once, then stack filters on language, review state and which check failed.
Nothing overwrites your work
An automatic draft can never land on top of something a person typed, and two people editing the same row are held apart rather than silently merged. Two different problems, two different guards.
Undo anything, for six months
Every version is kept for 180 days, with a floor of the twenty most recent per string, each stamped with who wrote it. Revert is one click on any of them.
Argue on the row, not in email
Comment on the exact string, mention the person who knows the answer, and require a second reviewer across the workspace on the Team plan. Their edit goes back through the same four checks.
Give an outside translator one language
Owner, admin, developer and translator, scoped to a project or to a single language. Access control is on every plan including Free, not sold as an upgrade.

Three ways a word gets fixed.

The grid is one of them. Which one you reach for depends on who noticed the problem.

Watercolour of a narrow stone street passing under an arch.

a marketer notices it

On the page itself

Hold ALT, click the words in your own running product, and fix them where they render. The screenshot goes with the change, so whoever reviews it can see the button it broke.

Watercolour of a rocky Mediterranean coast with cypresses and a bright sea.

a developer notices it

From the terminal

Pull, edit, push. The CLI and the GitHub Action put the same rows in front of a developer without opening a browser, and a missing translation fails the pull request rather than the launch.

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

nobody has to notice it

Before anyone reads it

The engine drafts the row, four checks run on it, and one repair pass happens before a person is asked to look. Most rows never need either of the other two.

FAQs

The questions teams ask before they move off a spreadsheet.

What is a translation management system, and do I need one?

It is one place that holds every string in your product in every language, plus who changed what and whether it passed review. You need one at the point where a spreadsheet stops being able to answer "is French ready to ship". That is usually the second language, or the second person.

Can I use this instead of hiring translators?

Most teams use it instead of an agency and keep one reviewer. The engine writes every language on every push; a person reviews the strings that carry the brand. If you already have translators, they work in the same grid with their own accounts and their own language grants.

How many strings can it hold before it gets slow?

There is no cap on strings in a project, and the row list is virtualised and paged, so ten thousand rows scroll at the same speed as ten. Search and filters run on the server against the whole project rather than against the page you have loaded.

What happens if two people edit the same string at once?

The second write is refused rather than silently applied, and the editor shows the version that arrived first so nothing is lost. A separate guard holds machine writes off a human edit, so an automatic draft can never land on top of something a person just typed.

Can I undo a bad translation?

Yes. Every version is kept for 180 days with a floor of the twenty most recent per string, on every plan including Free, each stamped with who wrote it. Revert is one click and restores it in place.

Can I give an outside translator access to one language only?

Yes. Grants are per project and per language, so a freelancer can be given French and see nothing else. There are four roles (owner, admin, developer, translator) and all of them exist on every plan, Free included.

How do I get my translations out again?

Through the API pull endpoint, the CLI, the delivery bundle or file storage sync. Translations do not leave through the browser today, and all four of those routes need a project token, which is available from the Starter plan.

Does it work with my file format?

Twenty formats round-trip natively, including JSON, XLIFF, PO, Android XML, iOS strings and stringsdict, ARB, YAML and properties. Seven of them carry plurals, and plurals and placeholders are preserved in both directions.

Is there a free plan, and what is actually in it?

100,000 words to start and 10,000 a month after, one project, 15 language rows including your source so 14 targets, three seats, and every role and permission. It is a hard cap rather than a meter, so it cannot produce a bill.

works with what you already run

41 connectors, already built.

All 41 integrations

your turn

Make your translation work take an afternoon, not a quarter.

Import a file, invite a reviewer, and have your first language reviewed and shipped in the same sitting.

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