General TranslationLaunch in every language.Keep every control.
The same developer-first toolchain, run at organization scale — SOC 2 Type II, SSO and RBAC, review gates before a translation ships, and versioned rollbacks for the one that already did.
The security review, answered
The certifications and controls your audit asks for first, in one ledger.
Trusted by the world’s best companies — Cursor, Ramp, and Profound ship in over thirty languages.
Access is scoped, not granted.
Roles scope people to projects and to locales, sign-on belongs to your identity provider, and every machine surface is keyed and signed.
One language, and nothing else
RBAC with custom roles — a Japanese translator whose permissions cover only Japanese files.
project:writeAdmin · Developertranslations:content:write@jun — ja onlyManage Locadex secretsAdminYour IdP signs people in. Your keys sign the rest.
SSO over SAML and OIDC, keys split by organization and project, webhooks you can verify.
Terminology, decided once.
Context Groups hold your glossary and style directives at the organization; every assigned project inherits them, and on overlap the top group wins.
One group, every project
Glossary and directives live at org level and are assigned across projects — Apply pushes a change through existing translations.
The difference a directive makes
The same sentence with and without the group — context, not model roulette.
“Locadex is the GT agent. This product name should never be translated.”
From org rule to edge region
One governed column: glossary, directives and scoped access press down through the review gate and the guarded Locadex PR — what ships below is versioned per locale and one step from rolled back.
Nothing ships until someone says so.
Hold a translation from the call site, review it in the workspace, approve it per entry and per locale — then it goes to the edge, and not before.
The review gate
Source and translation travel together; the gate holds the pair until a reviewer lets it through.
<T $requiresReview> · hash df0269baApproval is per entry, and per locale
Labels, one note per locale, and comment threads live on the pair — Spanish can be approved while French is still in review.
The gate starts as a prop
Hold a string for approval from the call site — it renders only after review lets it go.
1import { T } from 'gt-next';2export default function Receipt() {4return (5<T $requiresReview $id="checkout.receipt">6Payment received7</T>8);9}
tx(text, { $requiresReview: true })An agent on rails.
Locadex internationalizes your code and opens pull requests with translations — every change reviewable, on a prefixed branch, and setup is a separate PR you merge yourself.
Proof of work is a pull request
Red is your bare JSX, green is the same JSX wrapped — merged only after review.
@@ −12,3 +12,5 @@ app/checkout/page.tsx <main> <p>Payment received</p> <T> <p>Payment received</p> </T> </main>
opened by Locadex47 files changedYour repo shape, your commands
Point it at a directory; it runs in a sandbox with your org secrets injected as env vars.
apps/webtargetapps/apiout of scopepackages/uiout of scopeGenerate code
Wraps source with t() and the <T> component.
Generate translations and push
Creates translations in context and commits them.
Keep locales in sync
Re-runs as your source changes, so no locale drifts.
Rollouts you can take back.
Translations publish to a global CDN as versions, per locale — fixing production is an edit without a redeploy, and rolling back is one step.
Versioned per locale
Tags come from the CLI, so translation history carries your git metadata — restore any prior state.
A history entry is a source version — inline edits never create one.
Served from the edge
A global, low-latency translation CDN — push over-the-air updates without redeploying your app.
Get a demo.
Talk to an engineer about implementation, volume, and your security review — or start free and upgrade when you ship.
Forward-deployed engineers
Support from the engineers who build the product — Slack and phone, not a ticket queue.
Custom workflows
Any format or framework, wired into your own pipeline.
Shared context
Glossaries and directives shared across every project in the organization.
Custom SLA
Delivery and support commitments, written into the contract.