Enterprise platform
Share translation context, glossaries, and custom prompts across every project and content source in your company.
context · glossaries · promptsA dark event horizon sits at the center of otherwise empty ruled paper; the names of languages — Japanese, Spanish, Korean, Arabic, and more — wrap around it like a satellite belt, and the wordmarks of Cursor, Ramp, Profound, Partiful and ClickHouse sit inside the dark core.
Talk to an engineer — not a sales deck. We’ll walk your stack, your locales, and your review process, and leave you with a working plan.
Share translation context, glossaries, and custom prompts across every project and content source in your company.
context · glossaries · promptsReliable, scalable translation workflows across any file format or framework.
any format · any frameworkDedicated hours with forward-deployed engineers to bring localization to production.
dedicated hours · to productionNeed the full sheet? Open the enterprise contact desk.
Full-stack localization across buildtime, runtime, and review — with the controls procurement checks already on file. Send this page to your security team first.
Built for teams with real launch, security, and operational requirements.
Service organization controls, Type II audited.
EU data-protection compliance.
Certified information security management.
What the contract adds — engineers, workflows, and terms with names on them.
RBAC with custom roles — a Japanese translator whose permissions cover only Japanese files.
project:writeAdmin · Developertranslations:content:write@jun — ja onlySSO over SAML and OIDC, keys split by organization and project, webhooks you can verify.
Hold a string from the call site, approve it per entry and per locale — Spanish can ship while French is still held.
<T $requiresReview>The agent’s work arrives as a pull request on a prefixed branch — auto-merge off by default, merged only after your review.
@@ −12,3 +12,5 @@ app/checkout/page.tsx <main> <p>Payment received</p> <T> <p>Payment received</p> </T> </main>Translations publish to the edge as versions, per locale — tags carry your git metadata, and restoring a prior state is one step.
A history entry is a source version — inline edits never create one.
Every framework on this sheet maps to a first-party package — the same toolchain whichever stack renders your product.
gt-nextgt-reactgt-reactgt-reactgt-reactgt-reactgt-reactgt-tanstack-startgt-react-nativegt-react-nativegt-nodegt-fastapilocadexgt-sanity14 stacks · 7 packages · 1 agentEvery company’s localization needs are different. General Translation provides full-stack localization engineers who apply automation, design custom workflows, and carry launches through production.
Kudos to General Translation for helping with the localization efforts (great team)
General Translation is an incredible product, we are users at @cursor_ai