Provider fragmentation
Translation engines used different APIs, formats, authentication methods and operational environments.
Led by Pangeanic, iADAATPA developed an open platform that allowed European public administrations to access, compare and route translation requests across several machine translation providers through a common secure infrastructure.
Machine translation services differed by language, subject area, deployment model and quality. A provider that performed well for legal Spanish might not offer the best engine for Lithuanian parliamentary content or tourism data.
Integrating every provider separately created duplicated development, incompatible APIs and long procurement cycles. Switching between systems could require new connectors, security assessments and workflow changes.
iADAATPA addressed this fragmentation by creating a common platform able to receive translation requests, identify their language and domain, and route them to the most appropriate available engine.
Translation engines used different APIs, formats, authentication methods and operational environments.
Quality varied according to language direction, subject domain, training data and engine specialization.
Institutional documents required secure transport, controlled access and infrastructure suitable for public sector use.
Every additional provider could introduce new connectors, maintenance requirements and workflow complexity.
MT Hub created a shared access and orchestration layer between public administration workflows, European infrastructure and multiple machine translation providers.
Documents, text and web content enter the platform through a common interface, connector or API.
Automatic language identification determines the source language before translation begins.
Domain detection classifies content so that specialized engines can be selected where available.
Translation requests are sent to the most suitable provider according to language, domain and service configuration.
AS4 Domibus and European eDelivery components support reliable transfer of documents and service messages.
Translated content is delivered through the same platform, reducing integration work for the requesting administration.
The platform treated machine translation engines as interchangeable services that could be selected according to operational requirements.
Content arrives through an API, CAT tool, content management system, website or institutional workflow.
Language, domain, provider availability and service configuration determine the translation path.
iADAATPA combined translation technology with the integration, routing, security and workflow components required for institutional use.
Select engines according to source language, target language, domain, availability and configured service rules.
Classify content before translation to improve selection of specialized models and terminology.
Detect the source language automatically when the requesting workflow does not provide reliable metadata.
Use AS4 Domibus components for reliable and secure exchange aligned with European digital infrastructure.
Support immediate text translation and longer document processing through different request patterns.
Browse and translate web content through controlled platform services without exposing user activity unnecessarily.
Connect translation environments including Trados, MateCat and OmegaT to the same shared infrastructure.
Publish the routing platform openly so public bodies and technology providers could inspect, deploy and extend it.
Pangeanic led the consortium and oversaw the architecture required to connect several commercial technologies with European public administration services.
Pangeanic coordinated commercial providers, systems integrators, academic participants and institutional users.
The company supervised development of a provider neutral platform capable of handling multiple engines and workflows.
Pangeanic was responsible for security features and alignment with public sector document exchange requirements.
Pangeanic contributed specialized machine translation capacity alongside the other technology providers.
Real public sector and media use cases tested routing, domain detection and secure translation workflows.
The resulting platform was released as open source to support reuse beyond the original project.
The platform was evaluated through operational settings with different language pairs, content domains and integration requirements.
Translation workflows connected to the regional government Open Data and Transparency portal.
Multilingual digital services supporting tourism technology and public information.
Translation of parliamentary proceedings and institutional content involving a lower resource European language.
Multilingual website and academic content used to test platform access and translation delivery.
International media content used to validate multilingual routing and translation at practical scale.
The value of MT Hub extended beyond its translation engines. It created a common integration layer so that institutional users could keep their preferred tools while accessing different providers.
Connectors and APIs reduced the need to rebuild workflows every time an engine changed. This enabled public bodies to compare providers, introduce specialized models and maintain continuity at the application layer.
The same principle applies to modern enterprise AI. Models will change more rapidly than the systems and processes that depend on them. A controlled orchestration layer protects the organisation from unnecessary provider dependence.
iADAATPA moved beyond a translation engine demonstration and delivered the infrastructure required to manage several engines as a common public service.
Public administrations could reach several translation services through one platform and integration layer.
European Commission and commercial engines could operate behind a shared request and routing mechanism.
European eDelivery components supported reliable communication between institutional systems.
The platform was made publicly available under the GNU General Public License version 3.
The consortium brought together competing machine translation providers inside a shared architecture, supported by systems integration and academic expertise.
Consortium leadership, security oversight, architecture supervision and neural translation services.
Technical implementationCore platform coding, hosting and integration of commercial machine translation services.
Language technologyEuropean language technology, specialized engines and involvement of the Lithuanian Parliament.
Language technologyMachine translation services, language processing expertise and provider integration.
Systems integrationSystems integration, testing, project management support and identification of deployment scenarios. Everis is now part of NTT DATA.
Academic partnerAcademic language technology expertise and institutional website validation.
Modern organisations increasingly use several models rather than placing every task inside a single general system. Different languages, domains, security levels and workflows require different capabilities.
iADAATPA anticipated this environment. It placed a neutral control layer between users and models, allowing engines to be selected according to policy, performance and context.
The principle now extends beyond machine translation. Enterprises require governed gateways that can route tasks across small language models, private models, retrieval systems and external services while retaining control over data flows.
Select the most appropriate model according to task, language, domain, quality and deployment policy.
Keep applications separate from individual providers through common interfaces and orchestration.
Apply security, routing and infrastructure rules before documents are sent to a model.
Use smaller or domain adapted systems where they offer better operational performance.
The project provides a practical precedent for controlled access to several models through a shared enterprise layer.
Connect multilingual services to secure institutional workflows without rebuilding every application around one vendor.
Route sensitive content according to location, provider, model, security and data retention policies.
Manage specialist and general models behind consistent APIs, evaluation rules and operational controls.
Maintain control over model selection, data movement, infrastructure and service continuity.
These references document the action identifier, architecture, security layer, pilots and public release of MT Hub.
European Commission account of the platform architecture, eTranslation integration, Domibus security and pilot environments.
Read the Commission article →Public repositories containing components released by the project under an open source licence.
Explore the repositories →Pangeanic project account covering the consortium, platform capabilities, launch and open source release.
Read the project record →Early explanation of the common hub model, connectors, APIs and provider independence.
Read the platform article →European report describing iADAATPA as the project that produced MT Hub, an open source routing platform.
View the report →MT Hub within Pangeanic’s wider work in multilingual data, translation infrastructure, privacy and sovereign AI.
Explore all projects →iADAATPA established an infrastructure layer that was extended through later European projects addressing models, data assets and sensitive information.
Review projects covering multilingual datasets, translation, privacy, cultural heritage and sovereign AI infrastructure.
View all projects → Neural model infrastructureDiscover how Pangeanic coordinated 506 direct neural translation directions between the official EU languages other than English.
Explore NTEU → Privacy infrastructureExplore multilingual anonymization models and annotated datasets for sensitive administrative, legal and medical documents.
Explore MAPA → Reusable language dataDiscover the European infrastructure created to recover, share and reuse translation memories generated by public administrations.
Explore NEC TM →Pangeanic supports enterprises and public institutions with private translation infrastructure, model routing, multilingual data, controlled APIs, evaluation and sovereign deployment.