Automated
Raw machine translation with your terminology and a quality score for every segment.
OneLanguage · For the people who write and translate
OneLanguage is 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. You can use it in five ways.
01
Run translation projects on it
Files in any format keep their structure and layout. The risk level of each type of content decides how much review it gets, from your translators or ours.
02
Write with your terminology and style
Your writers and AI tools use the same terms and style guides, also when they write directly in the language of a market.
03
Translate more than your team can check
For large volumes, Supervised AI translation scores every segment, and our linguists correct the segments with low scores.
04
Connect your systems
Your CMS, PIM, documentation tool and code repository connect through the API, an automation tool or ready connectors.
05
Your language data is used in the next task
Terminology, translation memory, style guides, review decisions, QA results and quality scores from every project, writer, AI tool and connected system go into one account. The next task uses them, whichever of the four ways it comes from.
01 · For the people who work with translations daily
Run the whole translation operation on top of OneLanguage
Translation projects differ: 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 see 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.
Your company gives each type of content a risk level. Each risk level leads to one of four quality levels:
Supervised AI
Machine translation, and a linguist post-edits only the segments with low scores.
Professional
Machine translation, and a translator post-edits and approves every line (full post-editing).
Four-eyes review
A translator translates every line, and a second linguist reviews it (human translation and review).
For example, every safety instruction can get the risk level Critical, so it always goes to Four-eyes review.
Before a translation goes out, TextUnited checks it against the original: numbers, units, part numbers, safety warnings, and content that the AI added or left out.
Your company decides who changes terms and who approves translations. OneLanguage records every change.
See what a project looks like
Some of your content is not translated at all. Your team writes it directly in the language of the market, often with AI tools.
02 · For the people who write and publish
Write technical content with precision and craft marketing with your brand voice
Your support team drafts an article with Copilot. A colleague in Milan writes a new Italian landing page with Claude. Both should use your terminology and style instead of inventing their own.
The TextUnited MCP server connects these AI tools to your account. Your team can ask, for example: “What is our approved Polish term for this part?”, and the answer comes from your terminology. Colleagues without a Copilot or Claude licence use OneLanguage in the web browser.
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: Each API token has scopes. With ‘Read’, an AI agent can look up information. With ‘Write’, it can also change it, for example add a term approved during translation. Tokens are stored as hashes, so nobody, 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.
The service works in OneLanguage and in your AI tools, such as Copilot and Claude. It includes the maintenance of your terminology, translation memory and style guides, and the fine-tuning of the system to your company.
Passed the threshold, publishedRouted to our translators, automatically
Supervised AI translationSet up with us
You pay one monthly fee, whatever the languages. Quality scoring checks every segment. Segments below the threshold go to our translators at no extra charge. Your team does not route, queue or follow up on anything.
With the API, the whole process runs without your team: your CMS or PIM sends new content, and the checked translation goes back automatically.
Ask what this looks like on your content
Supervised AI translation is an add-on to your OneLanguage layer. It adds options and does not replace standard OneLanguage features.
04 · For the people who run the systems
Connect the systems you already run.
There are 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 that hold your content connect to the account.
For SharePoint, Confluence, GitHub and GitLab, TextUnited has ready connectors that work in both directions. The translated file goes back to the place where the original is stored.
CMSPIMProduct documentation / CCMSHelp deskCode repositoryDAMMarketing automation
Something changes
Your system pushes it. Segments carry your own identifiers, so nothing on your side tracks ours.
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.
For your IT team: Sign-in with your company account (SSO), automatic user management (SCIM) and central rollout in Copilot and Claude.
05 · What accumulates
Every project, AI tool and connected system adds to the same language data.
Language data is the terminology, translation memory, style guides, review decisions, QA results and quality scores 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. When a document changes, TextUnited translates only the parts that changed.
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 stays yours
Your language data stays in your own tenant, whichever provider, tool or AI agent uses it. You can export terminology as TBX, translation memory as TMX and style guides as Markdown at any time.
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, QA results and quality scores 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 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. We recommend that you contact us first and discuss your needs.
Start with real work
Bring one page and the terms two departments disagree on.
We work with your real content, not with a demo dataset. Bring something that a colleague published last week in a language you cannot check, and the vocabulary that nobody has settled.