Translation & Localization
memoQ
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by memoQ Translation Technologies Ltd. · www.memoq.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
memoQ at a glance
- Vendor
- memoQ Translation Technologies Ltd.
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates memoQ 2.5/5, the mean of 6 judges. memoQ is a translation management system from memoQ Translation Technologies Ltd., registered in Budapest, with generative AI translation (memoQ AGT) running on Microsoft's Azure OpenAI Service. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
memoQ is a translation management system from memoQ Translation Technologies Ltd., registered in Budapest, with generative AI translation (memoQ AGT) running on Microsoft's Azure OpenAI Service. Its strongest scores cluster at 6-7 in integrations and formats, content confidentiality and machine translation: the pages document three server APIs, five SDKs, Git-based sync and named CMS connectors, and the terms state that customer prompts and completions are never used to train LLMs and that the LLM relied on is stateless. Pricing transparency is the weakest score, capped at 4: only Starter is priced publicly — 'From $3,025 / year' for one PM license and five linguist subscriptions — while Essential, Professional and Enterprise all read 'Contact Sales'. Sovereignty split the judges: the in-house document translator scored it 8, crediting the on-premises edition, while the data protection officer and e-commerce marketer stopped at 6, citing a cloud described only as 'the Microsoft Azure worldwide infrastructure', a processor list stated to be not exhaustive, and EEA-to-USA transfers under GDPR Standard Contractual Clauses. Portability and exit topped out at 6, with one judge at 5.
Speaks for it
- The published terms state that customer prompts and completions are never used to train, retrain or improve any LLM, and that the LLM relied on is stateless.
- Documented Web Service, Resources and CMS APIs plus five SDKs support building custom connectors and extensions.
- An on-premises edition installs the TMS in the customer's own infrastructure, with custom private MT and LLM plugins available there.
- Terminology exports in open formats — TBX, CSV/TXT and MultiTerm XML — with package import from Trados and Transit.
- Unlimited characters in any plan at no charge, with no volume-based pricing.
Held against it
- Only the Starter tier carries a public price, 'From $3,025 / year'; Essential, Professional and Enterprise all read 'Contact Sales'.
- We found no public information on how long translated texts are retained or deleted, or on encryption at rest.
- We found no public information on translation-memory export in TMX, complete project export with history, or data return and deletion when a subscription ends.
- Single sign-on is offered only with Azure Private Server or On-Premises deployments.
- The Web Services API is listed only for Azure Private Server or on-premises, while the Starter plan runs on Azure Multitenant Cloud only.
Best for
- You translate documents in-house and need a central, browser-based terminology system that exchanges TBX, CSV/TXT and MultiTerm XML.
- You want AI translation under written terms: prompts and outputs never train models, and the AI provider is named with 15 days' notice of any change.
- You can run on-premises or on an Azure Private Server and want the TMS plus custom MT and LLM plugins inside your own infrastructure.
- Your developers build their own integrations and need documented APIs, five SDKs, and Git or CMS connectors.
Avoid if
- You must compute the annual cost of a team with several project managers from public pages before talking to sales.
- You have no linguists on staff and cannot check and approve every AI translation output.
- You need single sign-on on the shared multitenant cloud, where it is offered only with Azure Private Server or On-Premises.
- You want the Web Services API on the Starter plan, which runs on Azure Multitenant Cloud only.
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3 of 5 |
| Translation memory, terminology & review workflow | 3 of 5 |
| Integrations, file formats & developer tools | 3.5 of 5 |
| Confidentiality of translated content | 3.5 of 5 |
| Data export, portability & self-hosting | 3 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 2 of 5 |
Machine translation & AI quality
panel disagrees
Show reasoningHide reasoning
How this is scored
What the machine translation does and how well it is controlled: the languages and language pairs covered, the engine (own neural or LLM model, or a choice of third-party engines such as DeepL, Google, Microsoft or an LLM), glossaries and formality applied during translation, document translation that keeps the layout (Word, PowerPoint, PDF, InDesign), custom or adaptive models trained on the customer's own translations, automatic quality estimation or scoring, and published evaluations of translation quality.
0 — No machine translation of any kind, and no way to connect an engine.
3 — Machine translation is offered or one engine can be connected; languages, glossary use and quality controls are basic or not described.
5 — Machine translation for the major European and world languages with the list published, glossaries applied during translation, a formality or tone setting, document translation that keeps formatting for common office formats, and either an own engine or a choice of several named engines.
8 — Custom or adaptive models that learn from the customer's translation memory or corrections, automatic quality estimation per segment with a threshold that routes weak segments to human review, LLM-based translation with style guides and context, engine selection per language pair stated, and a published quality evaluation with its method.
10 — Translation quality that an organisation can measure and steer: evaluations against named benchmarks or blind human review published with their method, quality estimation calibrated and explained, custom models with their training data and isolation documented, and every machine-translated segment traceable to the engine, model version and glossary that produced it.
The Localization Manager
Generative AI translation is documented (memoQ AGT) that combines the in-context learning of LLMs with retrieval from the customer's own translation environment, engines can be custom-trained on the customer's data, DeepL, Google and Microsoft plugins are named, and AI output is explicitly routed to a human linguist for approval. We found no public information on published quality evaluations, automatic quality estimation, or engine selection per language pair, so it sits below the very top of what I would need to steer quality at scale. 2 7 10
The App Developer
Own AI translation is well documented: memoQ AGT combines large language models with the TMS text-retrieval functionality, the LLM is named as Microsoft's Azure OpenAI Service, and customers can use stock or custom domain-adapted engines trained on their own data, deployed cloud or on-premises, with DeepL, Google and Microsoft engine plugins free to connect (third-party account required). A machine-translation quality-estimates integration category exists on the API page, but we found no public information on a published engine language list, glossary or formality handling during machine translation, built-in per-segment quality estimation with routing to review, or a published quality evaluation. 2 6 7 10
The In-House Document Translator
Adaptive generative translation is documented in detail: memoQ AGT combines an LLM's in-context learning with translation memory retrieval, the models come from Microsoft's Azure OpenAI Service, and custom domain-adapted engines can be trained on our own data in cloud or on-premises modes, with a rule that any AGT output must be checked and approved by a human linguist. DeepL, Google and Microsoft machine translation plugins connect free with a third-party account, and PDF conversion plus an InDesign-compatible preview cover the contract and manual formats I deal in. We found no public information on automatic per-segment quality estimation with routing to review, engine selection per language pair, or a published quality evaluation with its method. 2 7 10
The Data Protection Officer
Generative AI translation (memoQ AGT) runs on Microsoft's Azure OpenAI Service combined with translation-memory retrieval, third-party engines DeepL, Google Translate and Microsoft Azure Translator can be plugged in, and the terms describe custom, domain-adapted engines trained on the customer's data — with AGT output still required to pass a human linguist. We found no public information on a published language list, formality or tone controls, per-segment quality estimation with routing, or any published translation quality evaluation. 2 6 7 10
The E-Commerce Marketer
Plugins for DeepL, Google Translate and Microsoft Azure Translator come with free integration via a third-party account, and the adaptive generative translation runs on Microsoft's Azure OpenAI Service with 'custom, domain-adapted engines trained on the Customer's data' — good news for my cycling-apparel vocabulary. But every generative output 'still needs to be checked and approved by a human linguist', and I have no translator on staff; I also found no public information on which languages are covered or any published quality evaluation. That sits just above the middle for a tool I would have to staff around. 2 7 10
The Skeptic
The AI story is real but unexamined: memoQ AGT combines large language models with the TMS's own text retrieval, third-party engines are named (DeepL, Google Translate, Microsoft Azure Translator) with free integration, and custom domain-adapted engines can be trained on the customer's data, cloud or on-premises. What I could not find: a published language list, glossary or formality controls applied to the AI output, per-segment quality estimation that routes weak output to human review, or any quality evaluation with its method. Human checking of AGT output is required, which is honest, but nothing published lets a buyer measure the engine. 2 7 10
Translation memory, terminology & review workflow
panel disagrees
Show reasoningHide reasoning
How this is scored
How translation is managed as an ongoing process: translation memory with fuzzy matches, a termbase or glossary managed centrally, style guides, review and approval stages, automated QA checks (placeholders, tags, length, terminology, punctuation), an in-context or visual editor, screenshots and context for translators, tasks and deadlines, roles per language, and ordering or inviting human translators and agencies inside the product.
0 — No management of translations at all; text goes in and comes out with nothing stored or reviewed.
3 — Translations can be edited or a glossary kept; translation memory, review stages and QA checks are basic or not described.
5 — A translation memory reused across projects, a central glossary, at least one review or approval stage, automated QA checks for placeholders and terminology, comments and screenshots for context, and roles that limit translators to their languages.
8 — Configurable multi-step workflows with automation rules, an in-context or visual editor for apps or websites, QA checks configurable per project with blocking rules, style guides applied by the AI, translation memory and termbase shared across projects with penalties and priorities, vendor or agency management with ordering inside the product, and progress and cost reporting per language.
10 — A translation process an enterprise runs on: workflows per content type with conditional routing on quality scores, linguistic quality assessment with a named framework (MQM or similar), termbase with approval workflow and forbidden terms, full revision history per segment, and productivity and quality metrics per translator and vendor.
The Localization Manager
The terminology backbone is real: Qterm with TBX, CSV and MultiTerm exchange, cross-database search, collaborative discussions, permission-controlled lookup beyond a linguist's own projects, shared memories, web and desktop editors, real-time collaboration and a PM dashboard, with human approval required for AI output. But the captured pages show only generic "quality checks", and we found no public information on configurable multi-step workflows with blocking QA rules, inviting translators or agencies inside the product, or cost and progress reporting per vendor — the last is exactly how I run my agency spend. 1 2 4 7 10
The App Developer
This is a managed process, not a file in/out: translation memories and term bases are reusable assets, Qterm gives a browser-based termbase with approval statuses, term requests, discussions, permissions and cross-term-base search, project management runs in web and desktop with a dashboard and real-time collaboration, and the vendor states any AGT output must still be checked and approved by a human linguist. What the pages do not settle for me are the enterprise details — configurable QA checks with blocking rules, an in-context editor for apps, and roles that limit translators to their languages — though a QA SDK, a preview SDK, PDF previews compatible with InDesign and timecoded video preview are documented. 1 2 4 7 10
The In-House Document Translator
Translation memories and term bases are shared across the server, with a lookup tool that reaches beyond assigned projects under admin-controlled access, and Qterm manages terminology in the browser with approval statuses, term requests, discussions and ISO 704/10241 support — exactly the central glossary a legal and export team needs. The workflow side promises workflow management, project tracking, quality checks, reports and a PM dashboard, and the product list includes in-country review. We found no public information on configurable blocking QA rules per project, a named linguistic quality framework, or ordering translators and agencies inside the product. 1 2 4 7
The Data Protection Officer
Translation memories are shared across projects, Qterm manages terminology centrally with approval statuses, term requests and TBX/CSV/MultiTerm XML exchange, and there are project-manager dashboards, real-time collaboration and an explicit human review step for AI output. Quality assurance appears as a named capability and as an SDK rather than as described checks, and we found no public information on configurable QA rules with blocking, style guides, vendor or agency ordering inside the product, or productivity and quality metrics per translator. 1 2 4 7
The E-Commerce Marketer
The browser-based terminology system with cross-term-base search, commenting, term requests and approval-status filters is exactly how I would fix a bad product name once and be done, and translation memories, shared resources, real-time collaboration and reporting are all named on the product pages. I found no public information on inviting or ordering translators and agencies inside the product, on roles per language, or on the automated checks for placeholders and terminology, so I hold it just above the middle. 2 4 7
The Skeptic
Translation memories are shared across projects and searchable beyond them with per-resource access control, the Qterm termbase runs in the browser with approval statuses, term requests and discussion threads, and every AGT output must be checked and approved by a human linguist; project management runs in web and desktop editors with dashboards. We found no public information on configurable multi-step workflows, what the QA checks actually cover, blocking rules, screenshots or context for translators, or inviting vendors and agencies inside the product. That is a solid working process described at brochure level, not an enterprise specification. 1 2 4 7
Integrations, file formats & developer tools
panel disagrees
Show reasoningHide reasoning
How this is scored
How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
0 — No documented way to get content in or out except typing or pasting by hand.
3 — File upload and download or a basic API; formats, repository sync and connectors are basic or not described.
5 — A documented REST API, a list of supported file formats covering the common software and document formats, sync with at least one Git host or CI, and connectors or plugins for several named CMS, shop or design tools.
8 — A CLI and SDKs for named platforms, over-the-air updates for mobile or web apps, Git sync with branching, webhooks, connectors for the main CMS, shop, design and support tools, office or browser add-ins, a public status page, and API limits documented.
10 — Integration that scales across an organisation: an API covering every function of the product with versioning and SDKs, an app or connector framework third parties build on, continuous localization in CI with pull requests opened automatically, and every connector documented with its limits and the fields it syncs.
The Localization Manager
Documented APIs (web service, resources, CMS — with the option to build our own CMS connector), five SDKs, Git/GitHub/GitLab/BitBucket sync, and named connectors for WordPress, Drupal, Contentful, Adobe Experience Manager, FirstSpirit, Figma and the Easyling website proxy cover most of our pipeline. We found no public information on a CLI, over-the-air delivery for apps, webhooks, documented API limits or a public status page, and the actual list of supported file formats was not captured on the pages we read. 1 5 6 7
The App Developer
The developer story is real: a documented Web Service API to manage projects, documents and resources programmatically, plus Resources and CMS APIs and five SDKs for building quality-assurance, machine-translation, memory, preview and termbase extensions, a Git Connector for GitHub, GitLab, BitBucket and SVN, and named connectors for Drupal, WordPress, Contentful, Adobe Experience Manager, FirstSpirit and Figma. Two things hold me back: the pricing page places the Web Services API only with Azure Private Server or On-premises deployments, and we found no public information on a CLI, over-the-air updates for apps, webhooks or the contents of the supported file formats list — as someone shipping Android XML and xcstrings daily, that list is the first thing I look for. 5 6 7
The In-House Document Translator
There are documented APIs — a Web Service API to manage projects, documents and resources, a resources API and a CMS API for building our own connector — plus five SDKs, connectors for WordPress, Drupal, Figma, Contentful and Adobe Experience Manager, Git-based sync with GitHub, GitLab and BitBucket, and package import from Trados and Transit. The PDF conversion and InDesign-compatible preview are what matter most for my Word and PDF files. The Web Services API is available only with an Azure private server or on-premises deployment, and we found no public information on a command-line tool, webhooks or documented API limits. 5 6 7 10
The Data Protection Officer
There are documented Web Service, Resources and CMS APIs with five SDKs, a Git connector covering GitHub, GitLab and BitBucket alongside SVN, and named connectors for Drupal, WordPress, Contentful, Adobe Experience Manager, Figma and FirstSpirit. The supported file formats appear only as a section heading on the captured page, and we found no public information on a CLI, webhooks, over-the-air updates, a public status page or API limits. 5 6 7
The E-Commerce Marketer
There are connectors for WordPress, Drupal, Contentful, Figma, FirstSpirit and Adobe Experience Manager, sync with Git, GitHub, GitLab, BitBucket and SVN, three server APIs and five SDKs for building your own connectors. Two catches for a shop like mine: I found no public information on a Shopify connector, and the pricing page lists the Web Services API as available with Azure Private Server or on-premises only, while the Starter plan I would start on is multitenant cloud only. 5 6 7
The Skeptic
The pipes exist and are named: server APIs for projects, resources and CMS connectors with SDKs for quality assurance, machine translation, memories, previews and term bases, sync with Git, GitHub, GitLab, BitBucket and SVN, and connectors for WordPress, Drupal, Contentful, Figma and Adobe Experience Manager. The pricing page ties the Web Services API to Azure Private Server or on-premises deployments, and we found no public information on the actual file-format list beyond a section heading, a CLI, webhooks, over-the-air updates or API limits. 5 6 7
Confidentiality of translated content
panel disagrees
Show reasoningHide reasoning
How this is scored
What happens to the text a customer translates: whether source and target texts are stored and for how long, deletion after translation, whether customer content is used to train the vendor's or a third party's models, which machine translation and LLM providers a TMS sends text to and whether that can be restricted or switched off, encryption in transit and at rest, single sign-on, roles and audit logs, and certifications (ISO 27001, SOC 2) with their scope. Where the text is processed is scored under sovereignty.
0 — Customer texts are stored indefinitely and used for the vendor's own purposes, or no statement on data handling exists at all.
3 — The product is described as secure or GDPR-compliant and a privacy policy exists; retention of translated texts, model training and third-party engines are basic or not described.
5 — A documented statement that customer texts are not used to train models, retention or deletion of translated texts stated, the third-party engines or LLM providers named, encryption in transit and at rest, single sign-on on a business tier, and a data processing agreement offered.
8 — Texts deleted immediately after translation or after a retention period the customer sets, third-party AI processing switchable per project or account, zero-retention terms with the named LLM providers, audit logs, granular roles, ISO 27001 or SOC 2 certification stated with its scope, and a private or dedicated deployment option.
10 — Confidentiality that can be verified: an on-premise or customer-controlled deployment, customer-managed encryption keys, every subprocessor that sees content listed with its role, independent audit reports available, and every data flow of a translation request documented end to end.
The Localization Manager
The AI terms are unusually explicit: prompts and outputs never train models, never reach other customers, the LLM is stateless, the provider (Azure OpenAI) is named with 15 days' notice of any change, and the customer retains all rights to its content — alongside an ISO/IEC 27001:2017 certification, enforced multi-factor authentication, granular resource permissions and private-cloud or on-premises deployment. We found no public information on retention or deletion of translated content itself, encryption at rest, or switching third-party AI processing per project. 7 9 10 11
The App Developer
The terms commit that customer prompts and outputs are not available to other customers or third parties, are not used to train, retrain or improve LLMs, and that the LLM relied on is stateless with no prompts or generations stored; the AI provider is named as Microsoft's Azure OpenAI Service, a data processing addendum chapter is published, ISO/IEC 27001:2017 certification is stated with multi-factor authentication enforced for all user accounts, and private cloud or on-premises deployments are documented. Three things the pages do not settle: the privacy policy states its service-provider list is not exhaustive, we found no public information on customer-set retention or deletion of translated content after translation, and the certification's scope is not spelled out. 7 9 10 11
The In-House Document Translator
The terms contain the written promise I need: customer prompts and outputs are never used to train, retrain or improve any LLM or third-party service, the LLM relied on is stateless with nothing stored, the customer retains all rights to their content, and a data processing addendum is part of the published terms. ISO 27001:2017 certification, enforced multi-factor authentication and the documented on-premises or dedicated private-cloud deployment would let me keep draft contracts on our own servers, with the AI provider named as Microsoft's Azure OpenAI Service. The processor list is expressly not exhaustive, single sign-on exists only with a private server or on-premises deployment, and we found no public information on customer-set retention or deletion of translated texts. 7 9 10 11
The Data Protection Officer
The terms commit in writing that prompts and completions are never used to train or improve any model, are not shared with other customers, and that the LLM relied on is stateless with nothing stored; the third-party engines and the LLM provider are named, an ISO 27001:2017 certification with annual independent review and a data processing addendum are published, and an on-premises deployment exists. What I could not find is what a health insurer needs first: how long the translated texts themselves are kept and when they are deleted, encryption of that content at rest, and product audit logs — and single sign-on is restricted to the Azure Private Server and on-premises deployments rather than the multitenant cloud, with the processor list stated to be not exhaustive. 7 9 10 11
The E-Commerce Marketer
The terms state that customer prompts and completions are never used to train LLMs or shared with other customers, that the LLM relied on is stateless, and the AI provider is named as Microsoft's Azure OpenAI Service; there is an ISO/IEC 27001:2017 certification, a data processing addendum inside the terms, and an on-premises option. I found no public information on how long translated content itself is retained or deleted, and single sign-on comes only with private-server or on-premises deployments, so I stop just above the middle. 7 9 10 11
The Skeptic
The terms promise the right things about AI: prompts and completions are never used to train models, never shared with other customers, and the LLM relied on is stateless — and the provider is named as Microsoft Azure OpenAI with 15 days' notice of any change. Around it sit ISO/IEC 27001:2017 certification, multi-factor authentication enforced for all user accounts, and private or on-premises deployments for those who want their own chain. But the question I always ask first — how long the translated texts themselves are kept — has no answer, single sign-on exists only with Azure Private Server or on-premises, encryption at rest is not stated, and the processor list is expressly 'not exhaustive'. 7 9 10 11
Data export, portability & self-hosting
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether translation assets stay the customer's and can leave with them: export of translation memory and termbase in open formats (TMX, TBX, XLIFF, CSV), export of all projects and files, import from another TMS, an API that can read every asset, the return or deletion of data on termination, open-source code and a self-hosted or on-premise edition.
0 — Translations cannot be exported; they exist only in the vendor's interface or engine.
3 — Translated files can be downloaded; export of translation memory and glossary, import and termination terms are basic or not described.
5 — Translation memory exportable as TMX and glossary as TBX or CSV, all project files downloadable, import of translation memory and glossaries from another tool, and an API that reads translations and keys.
8 — Complete export of every asset (memory, termbase, files, comments, history) in open formats, a documented migration path from named competitors, the data returned or deleted on termination under stated terms, and a self-hosted or on-premise edition with its own documentation.
10 — The customer owns the assets end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete export another tool can import without loss, and the deletion of every copy on termination documented.
The Localization Manager
Terminology leaves in open formats (TBX, CSV/TXT, MultiTerm XML), packages from Trados and Transit import, migration assistance is a listed service, the Resources API can read projects and documents programmatically, and an on-premises edition runs in the customer's own infrastructure. We found no public information on translation memory export in TMX or another open format, complete export of history and comments, or what happens to the data when a subscription ends — and the memory is the asset I care most about taking with me. 4 6 7 10
The App Developer
The assets can leave: Qterm imports and exports TBX, CSV/TXT and MultiTerm XML, the Web Service, Resources and CMS APIs plus the translation-memory and termbase SDKs can program every resource type, packages import from Trados and Transit with paid migration assistance available, the terms state the customer retains all rights to their content, and an on-premises licensed edition means the whole TMS can run in the customer's own infrastructure rather than the vendor's cloud. We found no public information on translation memory export as TMX, complete export of comments and revision history, or the return and deletion of data when a subscription ends — and the code is not open source. 4 5 6 7 10
The In-House Document Translator
Terminology leaves in open form — Qterm imports and exports TBX, CSV and MultiTerm XML — packages arrive from Trados and Transit, migration assistance moves resources into memoQ (manual on Starter, automated at a custom fee on the higher plans), and the on-premises edition with installation assistance keeps our translation assets in our own infrastructure, with the customer retaining all rights to their content. We found no public information on translation memory export in TMX, on export of comments and revision history, or on the return or deletion of data when a subscription ends. 4 7 10
The Data Protection Officer
Termbases export to TBX, CSV and MultiTerm XML, packages import from Trados and Transit, automated migration is offered for a custom fee, the APIs manage projects, documents and resources, and a documented on-premises edition runs in the customer's own infrastructure. We found no public information on the export format of translation memories themselves, on downloading whole projects with their history, or on the return or deletion of data when the contract ends. 4 6 7 10
The E-Commerce Marketer
Terminology exports to TBX, CSV/TXT and MultiTerm XML, Trados and Transit packages import on the desktop, migration assistance is offered with automated migration at a custom fee, the customer 'retains all rights to its Content', and an on-premises edition exists. I found no public information on translation-memory export as TMX, on a complete download of all projects, or on data return or deletion when a contract ends — the part I would want nailed down before signing. 4 7 10
The Skeptic
Terminology can leave in open formats — TBX, CSV/TXT and MultiTerm XML — packages import from Trados and Transit, migration assistance is sold as a service, APIs and SDKs can read memories and term bases, and the customer formally retains all rights to their content. We found no public information on translation-memory export as TMX, a complete export of projects with history, or what is returned or deleted when the subscription ends. For a TMS of this age, exit terms should be one paragraph, not an inference. 4 6 7 10
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where texts are translated, stored and processed, and who the subprocessors are (hosting, machine translation engines, LLM providers, CDN for over-the-air delivery, support and payment tools). Independently sourced by the sovereignty pipeline; translated texts often hold personal data and trade secrets, so the whole chain counts, including the engines a TMS calls. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (machine translation or LLM providers, CDN, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the engines and LLM providers, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every text on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, engine and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Localization Manager
The contracting entity is Hungarian — memoQ Zrt. at a Budapest address, with an EU VAT ID and registry numbers — a data processing agreement is published, ISO/IEC 27001 is stated, and a documented on-premises option installs the TMS in the customer's own infrastructure, which makes it my chain, not theirs. The gaps: the shared cloud runs on Microsoft's Azure "worldwide infrastructure" with no region stated, the subprocessor list is expressly "not exhaustive", and transfers between the EEA and the USA are acknowledged under GDPR Standard Contractual Clauses. 8 9 10 11
The App Developer
The contracting entity is memoQ Translation Technologies Ltd. (memoQ Zrt.) with a registered seat in Budapest, a Hungarian registry court, tax number and EU VAT ID, a data processing addendum is published, ISO 27001 certification is maintained, EEA–USA transfers are covered by GDPR Standard Contractual Clauses, and the public cloud runs in Microsoft's Azure infrastructure with Azure OpenAI named as the AI provider. The on-premises edition — customer-licensed software in the customer's own infrastructure, with custom private MT and LLM plugins restricted to private-server and on-premises deployments — is a genuinely sovereign path; the unresolved parts are the 'Azure worldwide infrastructure' wording without a stated region, and a service-provider list the privacy policy itself says is not exhaustive. 7 8 9 10 11
The In-House Document Translator
This is a European vendor: memoQ Zrt. in Budapest is the controller, registered at the Budapest company court with an EU VAT number, the NAIH as supervisory authority, a published data processing addendum and ISO 27001:2017 certification. The terms document an on-premises edition where we license and operate the TMS in our own infrastructure or a hosting service under our control, and custom private machine translation and LLM plugins are available on-premises, so the whole chain can be ours. In the cloud the deployment sits on Microsoft Azure's worldwide infrastructure with no EU region named, the processor list is declared not exhaustive, and transfers to the USA run on GDPR Standard Contractual Clauses — which is why I stop here rather than call it sovereign end to end. 7 8 9 10 11
The Data Protection Officer
The contracting entity is memoQ Translation Technologies Ltd., seated in Budapest with a Hungarian company registration number and an EU VAT ID, the Hungarian NAIH is named as the supervisory authority, a data processing addendum and ISO 27001 certification are published, and a documented on-premises configuration keeps the software on the customer's own servers. The cloud offering, however, is described only as running within the Microsoft Azure worldwide infrastructure with no region named, the processor list sits in an appendix and is stated to be not exhaustive with no locations given for the engines, and EEA-to-USA transfers are covered by Standard Contractual Clauses. 7 8 9 10 11
The E-Commerce Marketer
The vendor is a Budapest company with an EU VAT ID and a Hungarian registry court, the general terms contain a data processing addendum and cover EEA-to-USA transfers with GDPR standard contractual clauses, and an ISO/IEC 27001:2017 certification is published. But the cloud service runs in 'the Microsoft Azure worldwide infrastructure' with no stated region, the AI and machine-translation providers include US companies, and the processor list in the privacy policy is explicitly not exhaustive — a partly European, partly opaque chain. 8 9 10
The Skeptic
The entity is European and provable — memoQ Translation Technologies Ltd., registered in Budapest with Hungarian registry and EU VAT numbers — with a published data processing addendum and an on-premises edition the customer runs in their own infrastructure. The chain above it is murkier: cloud deployments sit in 'the Microsoft Azure worldwide infrastructure' with no region named, the AI models come from Microsoft's Azure OpenAI Service, transfers to the USA run on standard contractual clauses, and the processor list in the appendix is stated to be not exhaustive. A Hungarian company on unspecified Azure regions is not sovereignty you can point to on a map. 8 9 10
Pricing transparency
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by characters, words, keys, hosted words or seats, what happens when the volume exceeds the tier, the number of users, projects and languages included, which features (machine translation volume, AI credits, SSO, integrations, API access) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with volume, seats or features is unclear.
5 — Tiers are public with their price per volume band and main inclusions, but at least one commonly needed piece (overage, extra seats, machine translation or AI volume, SSO, connectors) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (characters, words, keys, seats), overage handling stated, add-ons and AI credits priced, the self-hosted edition's cost or licence stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given volume, seat count and feature set, with every add-on, setup, support and overage fee and the cancellation and data-return terms published.
The Localization Manager
Only the Starter tier carries a public figure — "From $3,025 / year", billed annually, with one PM license and five linguist subscriptions included — while Essential, Professional and Enterprise all say "Contact Sales" and extended storage is priced "depending on deployment". In its favour: unlimited characters in every plan, bundled linguist subscriptions per PM license, and published payment, pro-rated upgrade, grace-period and trial terms; but from these pages I cannot compute an annual cost beyond the smallest tier. 2 7 10
The App Developer
Only the Starter tier carries a public price — 'From $3,025 / year Billed annually' with 1 PM license and 5 Linguist subscriptions included — while Essential, Professional and Enterprise all say Contact Sales; on the plus side the pricing page states you may process an unlimited number of characters in any plan free of charge, a free trial and free educational licences exist, and monthly credit-card billing with a three-day grace period and pro-rated upgrades are spelled out. Extended storage is listed as 'depending on deployment' without a figure, and we found no public information on the cost of the AI translation services, the support-and-maintenance fee for perpetual licences, or VAT treatment — so an annual total for anything above Starter is not computable from the public pages. 2 7 10
The In-House Document Translator
Only the Starter tier is priced publicly — From $3,025 / year, billed annually, for one project manager license with five linguist subscriptions and 10 GB storage — while Essential, Professional and Enterprise all read Contact Sales, so the cost of the private or on-premises deployment I would actually buy is a sales conversation. Unlimited characters in every plan at no charge and no volume-based pricing are genuinely helpful, and trial, educational and 4Free editions exist. Extended storage is priced 'depending on deployment' and automated migration carries a custom fee, so the real annual cost is not computable from the public pages. 2 7 9 10
The Data Protection Officer
Only the Starter plan is priced publicly — "From $3,025 / year", billed annually, with one PM license and five linguist subscriptions and unlimited characters — while Essential, Professional and Enterprise are all Contact Sales, so the cost of additional project-manager licenses, the main scaling unit, cannot be computed from the pages. Extended storage is marked "depending on deployment" and automated migration carries a custom fee, though billing mechanics, pro-rated upgrades, the free trial and price-change notice are documented in the terms. 2 7 10
The E-Commerce Marketer
Starter is published as 'From $3,025 / year' for one project-manager license and five linguist subscriptions, with 'an unlimited number of characters' in any plan and no volume pricing — the part that protects me as the catalogue grows. But Essential, Professional and Enterprise all say 'Contact Sales', extended storage is 'Depending on deployment' and automated migration is a 'custom fee', so beyond Starter I cannot compute my annual cost from public pages; a free trial exists, limited to one per service. 2 7 10
The Skeptic
One number is public: Starter 'From $3,025 / year' with one PM license and five linguist subscriptions, and the vendor states there is no volume-based pricing — an unlimited number of characters in any plan, free of charge. Everything a growing team needs is a conversation: Essential, Professional and Enterprise all read 'Contact Sales', extended storage is 'depending on deployment', and automated migration carries a custom fee. The subscription mechanics are documented honestly (pro-rated upgrades, automatic charging, a three-day grace period), but the annual cost for a team of several project managers is not computable from public pages. 2 7 10
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined ⚠ unverified | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about memoQ
Is memoQ European?
Yes. whats-best.ai classifies memoQ as EU-Made.
Where does memoQ store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does memoQ have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to memoQ?
As of 2 Nov 2026, the panel rates SimpleLocalize (3.5/5), LILT (3.5/5) and Phrase Localization Platform (3.5/5) highest among the other 12 Translation & Localization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is SimpleLocalize (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: memoQ alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Open source, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 20 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.memoq.com Checked 1 Nov 2026 Details →
- 2 Features page (translation management) www.memoq.com Checked 1 Nov 2026 Details →
- 3 Features page (AI translation) www.memoq.com Checked 1 Nov 2026 Details →
- 4 Features page (terminology) www.memoq.com Checked 1 Nov 2026 Details →
- 5 Integrations page (content management) www.memoq.com Checked 1 Nov 2026 Details →
- 6 API documentation www.memoq.com Checked 1 Nov 2026 Details →
- 7 Pricing page www.memoq.com Checked 1 Nov 2026 Details →
- 8 Legal notice www.memoq.com Checked 1 Nov 2026 Details →
- 9 Privacy policy www.memoq.com Checked 1 Nov 2026 Details →
- 10 Terms of service www.memoq.com Checked 1 Nov 2026 Details →
- 11 Security / trust page www.memoq.com Checked 1 Nov 2026 Details →