Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by lingohub GmbH · lingohub.com

Report an error on this page Is this your product? →

Link to this page

LingoHub: AI-assisted analysis on whats-best.ai LingoHub: AI-assisted analysis on whats-best.ai (dark)

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.

LingoHub at a glance

Vendor
lingohub GmbH
Headquarters
Incorporated in Austria source, captured 14 Nov 2026
Data hosting
In the EU source, captured 14 Nov 2026
Free plan
Not stated on the vendor’s pages as of 14 Nov 2026
Panel verdict
The AI panel rates LingoHub 3.5/5, the mean of 6 judges. LingoHub is a translation and localization platform from lingohub GmbH of Linz, Austria, built around a translation memory, glossary, style guide and selectable AI and machine translation engines. how scores are made
As of
Vendor pages captured 14 Nov 2026; evaluated by the panel 14 Nov 2026. all sources

LingoHub alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

LingoHub is a translation and localization platform from lingohub GmbH of Linz, Austria, built around a translation memory, glossary, style guide and selectable AI and machine translation engines. The bench scores it highest on content confidentiality and sovereignty, both at 8: translation data is stated never to be stored with third parties nor used to train external public AI models, retention is published per plan with irretrievable erasure within 90 days of termination, and the ISO 27001 and SOC 2 Type II reports are downloadable. Machine translation is weakest at 5 to 6 — many named engines with credit multipliers, but no published language list and no published quality evaluation. Sovereignty carries a caveat: the captured pages give different pictures of where services run — the security page places all services in Ireland while the privacy policy names US providers such as AWS, Stripe and Apollo.io. The flagged splits are empty; no criterion spreads more than one point. Pricing transparency sits at 7 to 8 on a public Platform price of €209 / month, billed yearly.

Report an error

Speaks for it

  • Translation data is stated never to be stored with third parties nor used to train external public AI models, and the terms bar third-party LLM training on customer data.
  • Downloadable ISO 27001 and SOC 2 Type II reports, a published sub-processor list and a self-serve data processing agreement.
  • A self-hosted edition — exclusively for Enterprise customers, on request — keeps translation assets inside the customer's own data centers.
  • A documented API in two versions with webhooks, a CLI, iOS and Android CDN SDKs for over-the-air delivery, and connectors for GitHub, GitLab, Bitbucket, Azure, SAP, Figma, Storyblok and Zendesk.
  • The Platform plan is public at €209 / month, billed yearly, with 5 Mio. chars /mo included and a 14-day trial that does not automatically convert.

Report an error

Held against it

  • We found no public information on a published language list, formality settings, document translation that keeps office layout, or a published quality evaluation for the engines.
  • We found no public information on glossary export in an open format, on exporting comments and history, or on a documented migration path from named competitors.
  • A plan downgrade permanently deletes logs and version entries that exceed the lower tier's retention window or version limit.
  • The captured pages give different pictures of where services run — the security page places all services in Ireland while the privacy policy names US providers including AWS, Stripe, Intercom, Tremendous, Apollo.io and Notion.
  • Enterprise and self-hosted pricing are quote-only, we found no public information on VAT treatment, and annual cancellation requires 90 days' notice with no refunds.

Report an error

Best for

  • You are a software team wiring localization into CI/CD and need a documented API, CLI, webhooks and over-the-air delivery to iOS and Android apps.
  • You translate sensitive content and need written no-training commitments, published retention periods and downloadable ISO 27001 and SOC 2 Type II reports.
  • You want a European vendor — lingohub GmbH in Linz under Austrian law, hosting stated on ISO 27001-certified AWS in Ireland, with a published sub-processor list — or an Enterprise self-hosted edition inside your firewall.
  • You want AI drafts steered by glossary, style guide and translation memory while keeping the option to order human translation through a marketplace.

Report an error

Avoid if

  • Your core work is translating Word or PDF documents that must keep their layout — the documented file formats are software localization formats.
  • You need your data chain European end to end — the privacy policy names US providers and the selectable engines include US providers such as OpenAI and Google.
  • You may downgrade plans later — downgrades permanently delete logs and version entries beyond the lower tier's limits.
  • You must budget the full annual cost up front — ask the vendor: the public pages we read do not show it

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Machine translation & AI quality

Show 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.

Report an error

The Localization Manager

There is a real choice of named engines — OpenAI, Mistral, Google Gemini and Claude models alongside DeepL and Google Translate — each with a published credit multiplier, workspace-wide enable/disable, permission-gated engine management, bring-your-own-provider key and a custom LLM on the Enterprise plan, plus AI drafting inside glossary, memory and QA rules. What holds me back is that the captured pages show no published language list, no quality estimation routing weak segments to review, and no published quality evaluation, so the control story outruns the quality story. 2 9 10

Report an error

The App Developer

Translation runs through a customer-selected engine — OpenAI, Mistral, Google Gemini and Claude models with published credit multipliers, plus DeepL and Google Translate — and I can disable engines workspace-wide, bring my own provider key, and have LINA draft against glossary, memory and QA rules, with an Enterprise "Custom LLM" option. We found no public information on a published language list, tone or formality settings, document translation that keeps layout, per-segment quality estimation, or a published quality evaluation with its method, so this sits above the plain engine-choice level but clearly short of the measurable-and-steerable one. 2 9 10

Report an error

The In-House Document Translator

A real choice of engines — DeepL and Google Translate plus OpenAI, Mistral, Google Gemini and Claude models with per-engine credit multipliers, workspace-wide enable or disable, and the option to bring my own provider key — with glossary and style guide as core features the AI drafts inside. For a middle score it holds up, but we found no public information on a published language list, a formality setting, or document translation that keeps the layout of Word or PDF files — the format documentation speaks of software localization formats — which is exactly what I need for contracts and operating manuals. 10 2 9 3

Report an error

The Data Protection Officer

A wide choice of named engines is published — OpenAI, Mistral, Google Gemini and Claude models plus DeepL and Google Translate — each with a credit multiplier, switchable workspace-wide, restricted to management roles, with bring-your-own provider key and a custom LLM on Enterprise, and the AI drafting works inside the glossary, translation memory, style guide and QA rules. We found no public information on the languages covered, a formality setting, document translation that keeps office layouts, custom models trained on our own corrections, or a published quality evaluation, which keeps this at the middle level. 2 9 10

Report an error

The E-Commerce Marketer

DeepL and Google Translate plus OpenAI, Mistral, Gemini and Claude models are all selectable, each named model with its own credit multiplier, switchable workspace-wide, and the AI drafts inside the glossary, memory and QA rules with a style guide in the core package — I can even bring my own AI provider key. The captured pages publish no language list, no formality setting, no document translation that keeps office formatting and no quality evaluation, and that is where the documentation stops. 2 9 10

Report an error

The Skeptic

Named engines are documented down to model and credit multiplier — OpenAI, Google Gemini, Mistral and Claude models alongside DeepL and Google Translate — with workspace-wide enable/disable, bring-your-own provider key and an Enterprise custom LLM option, and the AI drafting works inside glossary, memory and QA rules. We found no public information on a published language list, per-segment quality estimation, adaptive models trained on the customer's own translations, or a published quality evaluation with its method — so the engines are plentiful and the proof of quality absent. 2 9 10

Report an error

Translation memory, terminology & review workflow

Show 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.

Report an error

The Localization Manager

The core of a working localization process is there: a translation memory searchable across the whole workspace with project, locale, status and date filters, a central glossary and style guide, review statuses running from New to Approved, automated QA, granular and custom roles that gate engine management to Owner, Admin and Localization Manager, context images, discussions, per-segment version history, and professional translation orders through an in-product marketplace. I found no public information on progress and cost reporting per language or vendor, or a named linguistic quality framework, which is what would take this from a good team tool to an enterprise process. 2 6 7 9 10

Report an error

The App Developer

There is a workspace-wide translation memory with project, locale, date and status filters, a central glossary and style guide, automated QA, approval statuses, context images and discussions, granular and custom roles, and translator sourcing inside the product via professional translation orders and a marketplace. What keeps it below the top band: we found no public information on an in-context or visual editor, configurable blocking QA rules, style guides applied by the AI explicitly, or per-language progress and cost reporting. 5 7 9 10

Report an error

The In-House Document Translator

Translation memory drawing from the whole workspace or specific projects with status filters including an Approved stage, automated QA, context images with discussions, granular roles, premium workflows with branching, and — the part that interests me — professional translation orders through a marketplace where the contract runs directly between me and the translator. It stays below the upper band because the captured pages do not describe QA rules configurable per project with blocking, a visual editor, roles limited per language, or cost and progress reporting per language. 9 7 5 10

Report an error

The Data Protection Officer

Translation memory with workspace or per-project scope, status filters, search and export, a central glossary and style guide, automated QA, context images and discussions, granular roles, professional translation orders through a marketplace, premium workflows with branching and versioned segment history are all documented. We found no public information on configurable multi-step workflows with automation rules, a visual in-context editor, QA rules configured per project, or progress and cost reporting per language, so it sits above the middle level but not at the advanced one. 5 7 9 10

Report an error

The E-Commerce Marketer

Everything I need to fix a bad product name by hand is documented: a workspace-wide translation memory with statuses like Approved and AI Translated, glossary, style guide, automated QA, granular roles, context images with discussions, per-segment version history, and a marketplace where I can order professional translators when a language needs a human. We found no public information on configurable multi-step routing, quality scoring per segment or cost reporting per language. 5 7 9 10

Report an error

The Skeptic

The translation memory is real and governable — searchable workspace-wide, filterable by project, locale, status and creation date, storing only chosen segment statuses, exportable, with 5 to 20 versions per segment by plan — alongside glossary, style guide, review statuses, granular roles and professional translation orders through a marketplace. Automated QA appears only as a named feature, and we found no public information on which checks it runs, on an in-context or visual editor, on configurable blocking rules, or on quality assessment against a named framework. 5 6 7 9 10

Report an error

Integrations, file formats & developer tools

Show 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.

Report an error

The Localization Manager

Developers are served properly: a documented REST API (a stable V1 and a beta V2 covering workspaces, projects, files, texts, glossaries, webhooks and automation), a CLI with Shell and Python recipes, mobile CDN SDKs for iOS and Android with over-the-air delivery, and connectors for GitHub, GitLab, Bitbucket, Azure, SAP, Figma, Storyblok and Zendesk, with API key permissions configurable per key. I found no public information on documented API rate limits, a public status page, or office and browser add-ins. 1 3 4 9

Report an error

The App Developer

This is the part I care about and it is genuinely there: a documented REST API in two versions with scoped API keys, a CLI with step-by-step shell and Python recipes, iOS and Android CDN SDKs, over-the-air updates via CDN so a typo fix ships without an app store release, GitHub, GitLab and Bitbucket sync plus Figma, Storyblok, Zendesk, Azure and SAP connectors, webhooks, and on-premise CI/CD connection for the self-hosted edition. We found no public information on office or browser add-ins, a public status page, or documented API limits beyond "High-volume API rates" on Enterprise, so not quite the everything-documented top. 1 3 4 8 9

Report an error

The In-House Document Translator

A documented REST API in versions 1 and a beta version 2, a CLI, webhooks, CDN delivery with iOS and Android SDKs for over-the-air updates, and connectors for GitHub, GitLab, Bitbucket, Azure, SAP, Figma, Storyblok and Zendesk. The supported file types are described only as a wide range of localization formats without a published list, and we found no public information on documented API limits or office and browser add-ins, so it sits just under the top band. 9 3 4 1

Report an error

The Data Protection Officer

A documented REST API in two versions with webhooks, a CLI with Shell and Python recipes, iOS and Android CDN SDKs for over-the-air delivery, and connectors for GitHub, GitLab, Bitbucket, Azure, SAP, Figma, Storyblok and Zendesk are published. The supported file formats are described only generically without a published list, and we found no public information on office or browser add-ins, a public status page, or documented API rate limits. 1 3 4 9

Report an error

The E-Commerce Marketer

There is a documented API in two versions with webhooks and automation, a CLI, over-the-air CDN delivery with iOS and Android SDKs, per-format documentation, and named connectors for GitHub, GitLab, Bitbucket, Azure, SAP, Figma, Storyblok and Zendesk. As a Shopify shop I note the captured pages name no shop or storefront connector, and we found no public information on browser or office add-ins, a public status page or documented API limits. 1 3 4 9

Report an error

The Skeptic

The developer surface is broad and mostly documented: REST API V1 with authentication and error codes plus a V2 beta covering workspaces, projects, files, texts, glossaries, webhooks and automation, a CLI, iOS and Android CDN SDKs for over-the-air delivery, and named connectors for GitHub, GitLab, Bitbucket, Azure, SAP, Figma, Storyblok and Zendesk. We found no public information on a public status page, on documented API limits beyond "High-volume API rates" on Enterprise, or on office and browser add-ins, and the captured excerpts point to a formats reference without enumerating the formats themselves. 1 3 4 9

Report an error

Confidentiality of translated content

Show 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.

Report an error

The Localization Manager

This is the strongest area for a buyer with sensitive strings: the vendor states translation data is never stored with third parties or used to train external public AI models, customer data is barred from third-party LLM training, specific engines can be switched off workspace-wide, retention is documented per plan down to individual log types with erasure within 90 days of termination, and SSO, 2FA, granular roles, audit logs, ISO 27001 and SOC 2 Type II with downloadable reports, plus an on-premises edition, are all stated. For the top level I would want customer-managed encryption keys and every data flow of a translation request documented end to end, which the captured pages do not show. 5 6 8 10 11

Report an error

The App Developer

Strong and largely checkable: a published statement that sensitive translation data is never stored with third parties or used to train external AI models, terms barring LLM retention of customer data, SSL in transit and at rest, detailed per-plan retention schedules, irretrievable erasure within 90 days of termination, audit logs (1 year, 3 years on Enterprise), SSO/SAML, SCIM, granular roles, engines switchable off workspace-wide, downloadable SOC 2 Type II report and ISO 27001:2022 certificate, a published DPA, and a self-hosted option. We found no public information on customer-managed encryption keys or a documented end-to-end data flow for every translation request. 2 5 6 9 10

Report an error

The In-House Document Translator

Here is the written promise I ask for: sensitive translation data is never stored with third parties or used to train external, public AI models, and the terms state that customer data is not permitted to be used for third-party LLM training, with commercially reasonable steps against retention by those providers. Add encryption in transit and at rest, SSO with two-factor authentication, audit logs kept one to three years, detailed retention tables per plan, irretrievable erasure within ninety days of termination, downloadable ISO 27001 and SOC 2 Type II reports, and an on-premises edition where content never leaves our data centres. For a top score I would want the retention window set by the customer and zero-retention terms in writing with each named model provider. 5 10 6 9 8

Report an error

The Data Protection Officer

The pages state that sensitive translation data is never stored with third parties or used to train external public AI models, the terms bar third-party LLMs from training on customer data, retention periods are published per log type, data is irretrievably erased within 90 days of termination, and every named engine can be enabled or disabled workspace-wide. Encryption in transit and at rest, SSO and 2FA, granular roles, audit logs kept one to three years, ISO 27001 and SOC 2 Type II with downloadable report and certificate, a published DPA and an on-premises Enterprise edition complete the picture; customer-set retention windows and customer-managed encryption keys are not described. 2 5 6 8 9 10 11

Report an error

The E-Commerce Marketer

Sensitive translation data is stated never to be stored with third parties nor used to train external AI models, engines can be enabled or disabled workspace-wide, retention is published per plan with deletion on request and erasure within 90 days of termination, encryption covers data in transit and at rest, and the ISO 27001 and SOC 2 Type II reports are downloadable. We found no public information on zero-retention terms with the named LLM providers or on a retention window the customer sets. 2 5 6 10

Report an error

The Skeptic

Retention is published per plan and per log type, data is erased within 90 days of termination and on request, third-party AI can be disabled workspace-wide, the engines are named, the terms commit that no customer data trains third-party LLMs, SOC 2 Type II and ISO 27001:2022 certificates are downloadable, audit logs run to three years, and an Enterprise self-hosted edition keeps content inside the customer's own data centers. For the top level I would want retention the customer sets, zero-retention terms with the named LLM providers and customer-managed encryption keys — we found no public information on those. 2 5 6 8 9 10

Report an error

Data export, portability & self-hosting

Show 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.

Report an error

The Localization Manager

Exit is taken seriously: translation memory exports as TMX or CSV with project and status filters, resource files import and export freely, the API reads files and texts, the customer's ownership of all data is written into the terms, erasure happens on request and within 90 days after termination, and a self-hosted edition with its own deployment documentation exists for Enterprise customers with migration assistance offered. I found no public information on termbase export in TBX, export of comments and history, or a migration path from named competitors. 7 8 9 10

Report an error

The App Developer

The memory exports as TMX or CSV with project and status filters, the terms state the customer retains full ownership and that data is irretrievably erased within 90 days of termination and on request, migration assistance is offered, and there is a documented self-hosted Enterprise edition with its own deployment guide where the customer manages the servers. We found no public information on exporting the glossary or termbase in an open format, or on exporting comments and full segment history, so a loss-free move to another tool is not demonstrated. 7 8 9 10

Report an error

The In-House Document Translator

The translation memory exports as TMX or CSV with locale, project and status filters, the API can read texts and trigger exports, the terms promise irretrievable erasure within ninety days of contract termination, and a self-hosted edition exists for Enterprise customers with its own documentation. We found no public information on glossary export in TBX, on importing memory or termbases from another tool, or on exporting comments and full history, so the exit path is solid but not complete. 7 10 8 1

Report an error

The Data Protection Officer

Customers retain full ownership of their data, the translation memory exports as TMX or CSV, files, texts and glossaries are reachable through the API, data is irretrievably erased within 90 days after termination, and a self-hosted Enterprise edition with its own documentation keeps content inside our own data centres. We found no public information on glossary export in TBX, export of comments and full history, or a documented migration path from named competitors. 1 7 8 10

Report an error

The E-Commerce Marketer

The translation memory exports as TMX or CSV, the API covers files, texts and glossaries, the terms state the customer keeps full ownership, data is irretrievably erased within 90 days after termination, and an Enterprise-only self-hosted edition with its own deployment documentation exists. Glossary export in an open format, import from another tool and a documented migration path from named competitors are not described, and a plan downgrade permanently prunes version history — I would export before ever downgrading. 6 7 8 9 10

Report an error

The Skeptic

Translation memory exports as TMX or CSV, the API reads workspaces, projects, files, texts and glossaries, resource files import and export, the terms grant full customer ownership and erasure within 90 days of termination, migration assistance is offered, and a self-hosted Enterprise edition has its own documentation. We found no public information on glossary or termbase export in TBX or CSV, on a migration path from named competitors, or on exporting comments and history, so I cannot confirm that every asset leaves in open formats. 1 3 7 8 9 10

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Localization Manager

The chain is European and named: lingohub GmbH in Linz is the contracting entity under Austrian law, all services run in ISO 27001-certified AWS data centers in Europe (Ireland), a sub-processor list is published, a GDPR data processing agreement is public, ISO 27001 and SOC 2 Type II are stated, and the self-hosted edition keeps every translation asset inside the customer's own data centers. Two caveats keep this from the top: the selectable AI and machine translation engines include U.S. providers, and the captured pages give different pictures of where services run — the security page says all services are in Ireland while the privacy policy names U.S. providers such as Apollo.io and Google. 5 8 10 11

Report an error

The App Developer

The contracting entity is lingohub GmbH in Linz, Austria, all services run on AWS in Europe (Ireland) on ISO 27001-certified infrastructure, the sub-processor list and DPA are published, certifications are stated, and the self-hosted edition keeps translation assets inside the customer's own datacenters. The privacy policy itself names U.S. service providers in the chain (including Intercom, Tremendous, Stripe, Apollo.io and Notion) for support, payment and outreach, and the selectable engines include U.S. providers such as OpenAI, Google and Claude, so the chain is not European end to end. 5 8 10 11

Report an error

The In-House Document Translator

The contracting entity is lingohub GmbH in Linz under Austrian law with exclusive venue in Linz, all services run in ISO 27001-certified AWS data centres in Ireland, a data processing agreement under Article 28 is published, and a public sub-processor list exists alongside ISO 27001 and SOC 2 certifications. The privacy policy itself names US providers — Amazon Web Services, Intercom, Tremendous, Stripe, Apollo.io, Notion — and the customer-selected engines include OpenAI, Google and Anthropic, so parts of the chain sit outside Europe and the captured pages give different pictures on whether all processing stays in the EU. For our draft contracts the strongest card is the on-premises edition that keeps every asset inside our firewall. 10 5 11 9 8

Report an error

The Data Protection Officer

The contracting entity is lingohub GmbH of Linz, Austria under Austrian law with venue in Linz, the security pages state all services run in ISO 27001-certified AWS data centres in Ireland, a sub-processor list is published with Article 28 agreements, the DPA is self-serve, ISO 27001 and SOC 2 Type II are stated with downloadable evidence, and a self-hosted edition keeps content in our own data centres. The privacy policy separately names US providers such as AWS, Stripe, Intercom and Apollo.io and services hosted in the US and other countries, and the engine catalog includes US providers like OpenAI and Google that the customer selects and can switch off, so the chain is not European end to end. 5 8 9 10 11

Report an error

The E-Commerce Marketer

Contracting is with lingohub GmbH in Linz, all services run in ISO-certified AWS data centers in Ireland, a sub-processor list is published, a GDPR data processing addendum is available, and a self-hosted edition keeps every asset inside my own firewall. Two things temper it for me: the selectable engines include US providers such as OpenAI and Google, and the privacy policy itself says some services run in the US and other countries. 5 8 10 11

Report an error

The Skeptic

lingohub GmbH in Linz with Austrian law and venue, hosting stated as ISO 27001-certified AWS in Europe (Ireland), a self-serve DPA at a public URL, published certifications, and a documented self-hosted edition that keeps texts on the customer's own servers — that is the chain a European buyer asks about. Two reservations I will not wave through: the captured pages describe the chain differently, with the security page placing all services in Ireland while the privacy policy names U.S. providers including Amazon Web Services, Intercom, Stripe, Apollo.io and Notion; and the selectable engines include U.S. LLM and machine translation providers, so a cloud customer's texts travel only as far as their own engine choices allow. 5 8 10 11

Report an error

Pricing transparency

Show 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.

Report an error

The Localization Manager

A buyer can compute most of the annual bill: the Platform plan is "€209 / month, billed yearly" with a 14-day trial that needs no credit card, 5 Mio. hosted characters per month included and extra volume at "€10/mo per 1 Mio. chars", AI credits at "€6/mo per 100k credits", CDN at 5 Mio. requests included and "€3/mo per 10 Mio. requests", a monthly credit budget of €6 to €1,000 with alerts, and cancellation windows and non-refundable terms spelled out in the terms. What is missing for full computability: the self-hosted edition is quote-only via support, Enterprise terms are custom, and I found no public information on VAT treatment or how many users the published price includes. 8 9 10

Report an error

The App Developer

The Platform plan is published at "€209 / month, billed yearly" per user with "5 Mio. chars /mo" included, then "€10/mo per 1 Mio. chars", "€6/mo per 100k credits" and "€3/mo per 10 Mio. requests" for CDN overage, a €6 to €1,000 monthly budget with alerts at 80% and 100%, a 14-day trial with no credit card, and stated cancellation windows (7 days monthly, 90 days annual). The self-hosted edition is quote-only via support@lingohub.com, and we found no public information on VAT treatment or Enterprise and legacy-plan prices, so the annual cost is computable for the Platform tier but not to the last euro. 8 9 10

Report an error

The In-House Document Translator

The Platform plan is published at "€209 / month, billed yearly" with "5 Mio. chars /mo" included, "€10/mo per 1 Mio. chars" extra, "€6/mo per 100k credits" for AI, "€3/mo per 10 Mio. requests" for CDN overage, a monthly budget of six to one thousand euros with alerts at eighty and one hundred percent, and clear cancellation terms for monthly, annual and invoiced billing. What I cannot compute from the pages: how many users the price covers, the limits of the free tier and sponsored plans, VAT treatment, and anything on the self-hosted or Enterprise editions, which are quote-only through support. 9 10

Report an error

The Data Protection Officer

The Platform plan is published at "€209 / month, billed yearly" with per-user fees, 5 million hosted characters a month and "€10/mo per 1 Mio. chars" beyond that, AI credits at "€6/mo per 100k credits", CDN at "€3/mo per 10 Mio. requests", budgets from €6 to €1,000 with alerts, a 14-day trial without credit card, and cancellation terms stated for monthly, annual and invoiced billing. Enterprise and the self-hosted edition are quote-only, and we found no public information on VAT treatment, so the full annual cost cannot be computed from the public pages alone. 8 9 10

Report an error

The E-Commerce Marketer

The Platform plan is public at €209 / month, billed yearly, with 5 Mio. chars included, extra capacity at €10/mo per 1 Mio. chars, AI credits at €6/mo per 100k credits, CDN overage at €3/mo per 10 Mio. requests and a monthly budget of €6 to €1,000 with alerts — so I can roughly predict what spring catalogue growth costs. The captured pages frame billing differently, with the terms speaking of a fee per user and the pricing page showing a single monthly figure, and prices for the other plans, the self-hosted edition and VAT treatment are not public. 9 10

Report an error

The Skeptic

The public Platform price is "€209 / month, billed yearly" with "5 Mio. chars /mo (~1 Mio. words)" included, and the add-ons scale transparently: "€10/mo per 1 Mio. chars", "€6/mo per 100k credits", "€3/mo per 10 Mio. requests", a 14-day trial that does not auto-convert, and a monthly budget of €6 to €1,000 with alerts at 80 and 100 percent. Enterprise and self-hosted pricing are quote-only by email, and we found no public information on VAT treatment or how seats scale the Platform price; leaving is also priced in — annual cancellation needs 90 days' notice, invoiced plans likewise, and no refunds are given. 8 9 10

Report an error

European sovereignty — proven facts

4 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU only unverified
Why unverified?

The privacy policy separately says LingoHub uses technologies and services hosted in the EU, the US and other countries (e.g. Google, Apollo.io), so some personal data may still be processed outside the EU despite the all-services-in-Europe claim.

4/4 pts 5 Report an error
Hosting options Self-hostable unverified
Why unverified?

Self-hosted deployment is available exclusively for Enterprise customers, on request.

1/1 pts 8 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The DPA document itself is not among the excerpts, so the self-serve reading rests on the public URL cited in the Terms (and Enterprise customers get custom DPA terms per the pricing page).

1/1 pts 10 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about LingoHub

Is LingoHub European?

Yes. whats-best.ai classifies LingoHub as EU-Made. Its vendor, lingohub GmbH, is incorporated in Austria, per the vendor’s page captured 14 Nov 2026.

Where does LingoHub store data?

LingoHub stores customer data in the EU, per the vendor’s page captured 14 Nov 2026.

Does LingoHub have a free plan?

Not stated on the vendor’s pages as of 14 Nov 2026.

What are the best alternatives to LingoHub?

As of 19 Nov 2026, the panel rates Crowdin (3.5/5), SimpleLocalize (3.5/5) and LILT (3.5/5) highest among the other 22 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 Crowdin (EU-Made, Estonia). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: LingoHub alternatives.

Where this could be wrong

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.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 API documentation developers.lingohub.com Checked 14 Nov 2026 Details →
  2. 2 Machine translation & AI quality — found from sitemap help.lingohub.com Checked 14 Nov 2026 Details →
  3. 3 Integrations, file formats & developer tools — found from sitemap developers.lingohub.com Checked 14 Nov 2026 Details →
  4. 4 Integrations, file formats & developer tools — found from sitemap developers.lingohub.com Checked 14 Nov 2026 Details →
  5. 5 Confidentiality of translated content — found from sitemap help.lingohub.com Checked 14 Nov 2026 Details →
  6. 6 Confidentiality of translated content — found from sitemap help.lingohub.com Checked 14 Nov 2026 Details →
  7. 7 Data export, portability & self-hosting — found from sitemap help.lingohub.com Checked 14 Nov 2026 Details →
  8. 8 Data export, portability & self-hosting — found from sitemap help.lingohub.com Checked 14 Nov 2026 Details →
  9. 9 Pricing page lingohub.com Checked 14 Nov 2026 Details →
  10. 10 Terms of service lingohub.com Checked 14 Nov 2026 Details →
  11. 11 Privacy policy lingohub.com Checked 14 Nov 2026 Details →