Something changes
Your system pushes it. Segments carry your own identifiers, so nothing on your side tracks ours.
OneLanguage · For the people who write and translate
One multilingual layer under everything your company publishes.
OneLanguage is TextUnited's enterprise language layer. One account holds your multilingual files, terminology, translation memory, style guides and review decisions. Five things you can use it for.
01
Run translation projects on it
Any file format, structure and layout preserved. Your translators or ours, with the review each language needs.
02
Terminology
Approved and prohibited terms, from technical vocabulary to brand names. Served to translators, writers and AI assistants alike.
03
Translation memory
Every confirmed sentence is reused in the next project and readable by every connected system.
04
Style guides
Rules by territory, product line or department. Applied in projects, and read by AI assistants through the MCP server.
05
Available to every system you run
Every approved term, confirmed sentence and review decision applies to the next task, whichever system sends it.
TextUnited Self-ServiceGitHub / GitLabAPISanityConfluencen8nSharePointCopilotMCP
01 · For the people who work with translations daily
Run the whole translation operation on top of OneLanguage
Translation comes in all shapes and sizes: a detailed user manual translated into 12 languages, or a set of 500 UI strings for a control panel in 5 languages, including a right-to-left language. You keep an eye on what matters: who works on each language and how much review each job gets, without sending emails or involving a developer.
Operating manual, crane v4.25 languages · 12,400 words
de-DE
Your reviewer, HamburgTwo approvers
fr-FR
Your freelancer since 2019One reviewer
it-IT
TextUnited linguist, ordered hereOne reviewer
pl-PL
Handed to TextUnited to runNot started
ar-SA
Your reviewer, Dubai · right to leftOne reviewer
Files in and out: PDF, DOCX, PPTX, XLSX, XML, InDesign IDML, JSON, SCORMAnyone with access sees this screen
Bring your own translators at the rates you already agreed. Files come back in the format they arrived in: PDF, DOCX, PPTX, XLSX, XML, InDesign IDML, JSON and SCORM.
See what a project looks like
Not everything your company publishes starts as a file somebody sends for translation.
02 · For the people who write and publish
Write technical content with precision and craft marketing with your brand voice
Your support team drafting an article with a Copilot, while a colleague in Milan creates a landing page in Italian from scratch using Claude, not as a translation, but as an original piece. In both cases, they shouldn’t have to invent your terminology or language style.
Inside OneLanguage, AI assistants are hard at work connecting the dots in your data: one focuses on translations, while the others ensure your terminology and language styles stay consistent. Outside of it, the TextUnited MCP server allows any AI your team uses to access your account and retrieve the necessary information.
Colleague's editor · connected to TextUnited
Write the German product description for the RT crane.
→ textunited.terminology.lookup("pressure relief valve", "de-DE")
approvedÜberdruckventil
not usedDruckbegrenzungsventil
not usedSicherheitsventil
approved byProduct · DE · Sep 2025
→ textunited.styleguide.get("product description", "de-DE")soon
× terminology.update unavailable · token scope: read
For the tech-savvy: An API token comes with specific permissions, called scopes. 'Read' allows agents to access information, while 'Write' lets them make changes, such as updating a term approved during translation so it appears in your account instantly. If an agent doesn’t have 'Write' access, they won’t see features that could modify anything in your TextUnited account. To keep things secure, tokens are stored as hashes, meaning no one, including us, can retrieve them.
See the MCP landing
One person asking one question is fine. Four thousand descriptions overnight is not.
03 · Add human intelligence to your OneLanguage account without staffing it yourself
When translation volume outgrows the human capacity to check it
Supervised AI translation is TextUnited's managed service option. Our experts build your initial terminology and implement custom automation. It extracts terms as content arrives, routes them for approval and scores every translated segment. Segments with low scores are sent to translators for improvements, which are eventually added to your language data to enhance future translations.
Passed the threshold, publishedRouted to our translators, automatically
Supervised AI translationSet up with us
A flat fee per volume, whatever the languages. Quality scoring gates every segment; those below the threshold go to our translators at no extra charge.
Nothing on your side routes, queues or chases anything.
Ask what this looks like on your content
Supervised AI translation is an add-on to your OneLanguage layer.
It expands your options, not replacing standard OneLanguage features.
04 · For the people who run the systems
Connect the systems you already run.
Two ways to make the same connection. A team with developers calls the API. A team without them builds the same sequence in the automation tool it already runs. Either way, the systems your content already lives in reach the account.
CMSPIMProduct documentation / CCMSHelp deskCode repositoryDAMMarketing automation
It runs on your data
Terminology, memory and style guides apply before anything is produced.
Content type picks the route
To a reviewer, to publication or to the archive, rather than to whoever is watching the queue.
Versions come back
Each sync moves what changed.
The API is open and what your team builds on it stays yours. The MCP server is a wrapper over the same API, so anything your systems can reach, your assistants can reach on the same terms.
05 · What accumulates
Keep what all four of them produce.
Language data is the terminology, translation memory, style guides, review decisions and quality signals your organisation accumulates. It grows every time you publish. A translation project, an AI assistant, and a connected system all read and write to the same source of truth.
It applies to the next job
An approved term reaches the next file, the next language and the next colleague without anyone forwarding it.
It answers later questions
Segment states and the comments around them explain why a phrase reads the way it does, a year after the person who chose it moved teams.
It leaves with you
Terminology and translation memory export as TBX and TMX, style guides as Markdown files which a competing system can open. Your content sits in your own tenant.
Questions
Before you talk to us
Is OneLanguage a translation management system?
No. A TMS manages translation jobs after the content is written. OneLanguage holds the language data your company accumulates: terminology, translation memory, style guides and review decisions. Translation projects run on it. So does content written natively in a market, and content drafted with your company's AI tools. Nothing on this page requires you to buy a TMS first.
What is language data?
The terminology, translation memory, style guides, review decisions and quality signals your company accumulates as it publishes in more than one language. It sits in your own tenant and belongs to you.
Do we write our content in TextUnited?
No. Your content stays in the CMS, PIM or documentation tool where your team writes it. OneLanguage connects to those systems through the API or an automation tool. Your writers keep their editors, and the MCP server gives those editors access to your language data.
We write a lot of content natively, not as translations. Does that fit?
Terminology and style are properties of how your company writes, not of a translation. They apply to Italian written in Milan the same way they apply to Italian translated from English.
Which systems can we connect?
Anything that can call a REST API, which in practice means your CMS/CCMS, PIM, product documentation tool, help desk or code repository. Teams that prefer not to write an integration build the sequence in the automation tool they already run.
Can I bring my own translators and agencies?
Yes, at the rates you already agreed. You add existing freelancers to your account as users with a limited access and assign them per language on each project. You can also order TextUnited linguists for a language, or hand a whole language to TextUnited to run.
What happens to our language data if we leave?
You export translation memory as TMX, terminology as TBX and style guides as Markdown. A competing system can open all three. Your content sits in your own TextUnited tenant until you close it.
We already use a translation management system. What moves over?
Translation memory imports as TMX, terminology as TBX and style guides as Markdown. Any system that exports those formats can hand its data to OneLanguage. Your freelancers and agencies keep working in the new account at the rates you agreed with them.
Who in our company can own the TextUnited account?
Usually the team responsible for technical documentation or compliance, with localisation running the day-to-day work.
How do we start?
Most teams begin with a free trial but a good idea is to contact us directly and discuss your needs first.
Start with real work
Bring one page and the terms two departments disagree on.
Not a demo dataset. Something a colleague published last week in a language you cannot check, and the vocabulary nobody has settled.