From CAT Tools to Co-Pilots: A 75-Year Arc
The translation industry’s relationship with technology has always been more sophisticated than outsiders assume. From the first machine translation experiments in the 1950s through the computer-assisted translation (CAT) tool era of the 1990s and 2000s to today’s large language model (LLM)-driven pipelines, the fundamental challenge has never changed: How do you handle human language with all its ambiguity, register, and cultural weight at scale, without losing quality or client trust?
Trados and its peers gave us translation memories, terminology databases, and a model built around human expertise augmented by software. That model served language service providers (LSPs) well for three decades. It also created the habits, workflows, and client expectations that now make the AI transition genuinely hard. The co-pilot era doesn’t just add a new tool. It challenges the production model from the ground up.
Today’s platform landscape reflects that tension. Trados GroupShare with Studio Copilot can run local LLMs through Hugging Face. memoQ TMS has offered on-premises deployment since launch. Lilt advertises air-gapped and dedicated sovereign-cloud configurations for regulated and government work. XTM Server does too. Meanwhile, DeepL is moving toward AWS-only infrastructure, and the foundation models — Claude, ChatGPT, Gemini — cannot be truly on-premises because the model itself lives in someone else’s cloud.
The deployment menu is wide. What most LSPs are missing is not the technology. It’s the framework to explain the trade-offs honestly to clients.
What Is Genuinely New
I want to be precise here because intellectual honesty matters. Some things in 2026 are genuinely new, and they deserve the attention they are getting.
What is new is the combination: on-premises deployment philosophy layered with bring-your-own-LLM capability, packaged under a sovereignty narrative that is also anchored in specific ownership structures and community values. Companies like LIC (Language Intelligence Corporation), with its Canadian-Indigenous ownership model, are not simply reselling a technical architecture. They are making a value argument about who controls language infrastructure and who benefits from it. That is a different conversation, and an important one.
What is also new is the pace. The window between “experiment” and “client expectation” has collapsed. LSPs that took a wait-and-see posture in 2023 are now explaining gaps to clients who have been running their own AI pilots for two years. The technology did not wait for the industry to form a consensus.
The Real Risk: Buying the Badge Instead of Building the Practice
The danger I see most clearly for LSPs right now is not that they will adopt AI too slowly. It is that they will adopt the language of AI sovereignty without doing the harder work underneath it.
Sovereignty is a choice you make in how you build, not a badge you purchase from a vendor. An LSP that cannot walk a client through the full deployment menu and explain the data governance trade-offs for each item is not offering sovereign capability. It is reselling sovereignty marketing.
That distinction will matter in the regulated sectors that represent the highest-value, most defensible work in our industry: legal, medical, government, financial. Those buyers have compliance requirements that will force the conversation. LSPs that have built the practice — not just adopted the vocabulary — will win the work. The ones who bought the badge will lose it.