Full-stack localization across buildtime, runtime, and review — two plans and a published rate card. Unlimited users, projects, and languages from the first day: the gate is a payment method, not a feature list.
$ npx gt translate --dry-run
gt-next detected · Next.js App Router
128 strings · 24,000 input tokens · 5 locales
project context · glossary 24 · directives 6 · 1,000 tok
dry run — nothing translated, nothing billed
Everything you need to localize a real product, metered at the published rates.
$5 / LCUThe same toolchain, plus governance, custom workflows, and the engineers who build it.
Both plans run the same toolchain at the same published rates. Enterprise adds governance, custom workflows, and the engineers who build the product.
Rates are quoted per 10,000 input tokens, itemized as base + context, and capped by a Usage Limit — the price of a translation is knowable before you run it.
Every once in awhile, I see a snippet of code that makes me a bit emotional.
Now is one of those moments. Internationalization went from “$%!# this” to “trivial”.
Everything below restates the docs and the rate card, not a sales page.
npx gt translate --dry-run first and the estimate is itemized before anything is billed.<T> to start?i18next, next-intl, and react-i18next from package.json and translates your existing files in place — same keys, same ICU syntax, same nesting. gt-next and gt-react are the upgrade path, not the price of entry.Start at $0 with unlimited users, projects, and languages — or talk to an engineer about volume, custom workflows, and your security review.
Mark up UI copy, route locales, and ship static translations in your codebase.
Translate user-generated and backend content on demand across every runtime surface.
Curate glossaries, style rules, and project context, along with editing, versioning, and integrations.
Locadex scans repos, updates i18n code, generates translations, runs visual QA, and opens guarded PRs.