transglot for platform teamsmany repos, one contract
Every team's strings translated on one contract.
Fourteen repositories, three app teams, one marketing site, and somehow four translation vendors. Put them all on one pipeline, with one glossary, single sign-on, scoped tokens and an audit log procurement can actually read.
Without
With
Every team picked its own vendor, so nobody owns the glossary and the brand terms drift.
One pipeline across every repository, with one glossary enforced by the terminology check.
A security review per tool, a processing agreement per vendor, a renewal per quarter.
One contract, one processing agreement and one renewal. Procurement does the work once.
Translation memory scattered across vendors who charge to hand it back.
One memory, no training on your content, and a per-project opt-out available on every plan.
a worked example
Four vendors down to one: what actually changes.
approved
to: eng-all · from: platform · re: translation vendors, four down to one
- Vendors four to one. Renewals four to one. Security reviews four to one. Channels arguing about the glossary, three to none.
- One flat plan absorbed the growth that per-word pricing was billing us for. The only meter left is $0.0008 a word past the allowance.
- Adding a language stopped being a procurement conversation and became a setting. It uses allowance, like everything else, and nothing else changes.
- The audit log went from a CSV somebody exports to a query with a CSV export behind it, and the security questionnaire became mostly links.
- The exit was tested before we signed: the pull endpoint, the CLI and the CDN bundle all return the strings without anyone approving it.
A worked example. No company, no signatory and no spend figure, because we have no customer outcome to quote.
The win is not a translation feature. It is one contract, one glossary and one place to look.
the paperwork
What security and procurement will ask you for.
One review covers every team. Each row links to the page that states the current position, including the ones still in progress.
- trust centre
Compliance posture, with its real status on each row
the trust page - dpa
The data processing agreement, rendered as a page you can read now
/legal/dpa - sub-processors
Every company that touches your content, named and located
the trust centre - sla
Uptime targets and the service credit schedule
99.9% Business, 99.95% Enterprise - security
How the platform is built, and who to send a report to
security@transglot.ai
Those uptime figures are contractual targets on Business and Enterprise, not a measurement. We publish no uptime percentage, because we run no probe of our own.
FAQs
The questions a security review and a procurement form both ask.
We already have a translation vendor per team. What exactly are we replacing?
Four contracts, four security reviews and four renewals, with one workspace: every repository wired to the same pipeline, one glossary enforced across all of them, and one invoice. Importers for Lokalise, Phrase, Crowdin, Transifex, Weblate and POEditor exist so the move does not have to start with an export and a fortnight.
Can every repository use the same pipeline?
Yes. Each repository adds the GitHub Action, or calls the CLI or the REST API with its own scoped project token, and the drafted languages land in the same pull request in that repository. GitLab, Bitbucket and Azure Repos connectors are available from the Team plan.
Do you support SAML single sign-on and SCIM provisioning?
Both ship, and both are Enterprise. Sign-in is real SAML with just-in-time provisioning and an enforce-SSO setting, and SCIM 2.0 provisions and deprovisions users and records what it did in the audit log.
Is there an audit log, and can we export it?
Yes, on Enterprise. It is append only, enforced in the application so an update or a delete throws rather than quietly succeeding, and it exports as CSV. There is no hash chain, so we do not call it tamper evident, and streaming into a SIEM is not supported.
How granular is access control?
Four organisation roles, owner, admin, developer and translator, on every plan including Free, plus grants that can be scoped to a single project or a single language. Roles and permissions are never sold as an upgrade here.
Who processes our content, and where?
The trust page names every subprocessor and its location, and it renders from configuration rather than from prose, so a company we do not disclose cannot appear on it. Six are disclosed today. Your content reaches the AI subprocessors for inference only, under commercial terms, and none of it is used to train a model.
Do you have a SOC 2 report?
Not yet, and the trust page says so in those words: the audit is in progress, Type I readiness first and then the Type II observation window. ISO/IEC 42001 is being pursued. No page on this site can render a certification badge unless the configuration marks it as held, which is the reason the page is worth reading.
What uptime do you commit to?
A contractual monthly target of 99.9% on Business and 99.95% on Enterprise, with a published service credit schedule that tops out at 25% of monthly fees. We publish no measured uptime percentage anywhere, because we run no probe of our own, and live status is reported by an independent provider.
How do we get our data out if we leave?
Four ways, none of which needs our permission: the REST pull endpoint, the CLI, the delivery bundle on the CDN, and file storage sync to S3, Dropbox or Drive. There is deliberately no browser download of translations. Your translation memory is yours and is not held back as a retention tactic.
Can we self-host, or run it in our own cloud?
Not today. There is no packaged image, no installer and no air-gapped build. Packaged and air-gapped self-hosting is the single item on the Enterprise roadmap, and until it ships we do not sell it or describe it as available.
How does billing work across many teams?
One workspace, one plan, one invoice. Words are the only meter: your source words are counted once for each language they are translated into, and anything past the allowance is $0.0008 a word. Seats are unlimited from Team, projects are unlimited on every paid plan, and all 41 integrations are included.
How do we stop brand terms drifting between teams?
One glossary per project, enforced by the terminology check when the engine writes and again in the QA review pass, with up to 40 terms folded into each chunk the engine sees. The glossary is available from the Starter plan. That is the mechanism that stops four teams inventing four words for the same feature.
one plan · unlimited seats from Team
Put every team on one translation pipeline.
Single sign-on, SCIM and the audit log are Enterprise. Everything else on this page ships on a paid plan today.