Wordbee
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Wordbee S.A. · www.wordbee.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.
Wordbee at a glance
- Vendor
- Wordbee S.A.
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates Wordbee 3/5, the mean of 6 judges. Wordbee is a translation and localization platform covering translation memory, terminology, machine translation, QA, vendor management, finance and workflow automation. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Wordbee is a translation and localization platform covering translation memory, terminology, machine translation, QA, vendor management, finance and workflow automation. Judges scored it strongest on workflow and review, a uniform 7: QA profiles at project or organization level check terminology, tags and numbers, a review-only role lets reviewers flag issues without editing text, and an exportable report carries severity. Integrations and formats sit at 6–7 on a REST API spanning projects, jobs, workflows, resources, QA and invoices, plus GitHub and GitLab sync, webhooks and a format list from XLIFF and PO to InDesign and Trados bilingual. The genuine split is content confidentiality, 4–7: the app developer and data protection officer credited AES-256, TLS 1.2+, ISO 27001, SOC 2 Type II and single sign-on, while the document translator leaned on open questions about how long translated texts are kept and whether content trains models. Machine translation held a uniform 6 on twelve named engines and LLM custom prompts, with no published quality evaluation. Sovereignty scores of 4–5 track hosting on the vendor's own EU or US cloud; no prices are published.
Speaks for it
- Workflow and review scored a uniform 7, with QA profiles checking terminology, tags and numbers and an exportable severity report
- Twelve named machine translation engines plus LLM translation steered by a custom prompt for tone, style and domain
- A REST API spans projects, jobs, workflows, resources, QA and invoices, with GitHub and GitLab sync and webhooks on status changes
- Documented security includes AES-256 at rest, TLS 1.2+ in transit, ISO 27001, SOC 2 Type II, SAML single sign-on and an exportable activity log
- Termbases export to TBX version 3 (ISO 30042, 2019) with term alternatives preserved, alongside searchable, exportable translation memory
Held against it
- Content confidentiality split the judges from 4 to 7 over open questions on how long translated texts are kept and whether content trains models
- Machine translation scored a uniform 6, and we found no public information on published quality evaluation or glossaries applied during machine translation
- Hosting is a choice between the vendor's own EU and US cloud facilities, with the data processing agreement available only on request
- We found no public information on data return or deletion at termination, or on importing translation memory from another tool
- The captured pages give different entity names for the vendor — Wordbee SARL and Wordbee S.A. — with the contracting entity's jurisdiction unconfirmed
Best for
- You run localization projects with external vendors and need QA checks, vendor management and invoicing in one platform
- Your developers sync source strings through GitHub or GitLab and drive builds with a REST API and webhooks
- You translate many file formats — XLIFF, PO, JSON, InDesign, FrameMaker — and want custom extraction rules where needed
- You want wide engine choice for machine translation, including LLM translation steered by a custom prompt, wrapped in human QA
Avoid if
- You need self-hosted or on-premises deployment — the captured pages show hosting only on the vendor's own EU or US cloud
- You must certify the processing chain as European before signing — the engine list includes Microsoft and Google, and we found no public information on safeguards for that part of the chain
- You need a turnkey connector for a specific CMS, cloud store or game engine — the captured pages name only GitHub and GitLab, with the rest described as categories
- You need price figures to budget before a sales conversation — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3 of 5 |
| Translation memory, terminology & review workflow | 3.5 of 5 |
| Integrations, file formats & developer tools | 3 of 5 |
| Confidentiality of translated content | 3 of 5 |
| Data export, portability & self-hosting | 3 of 5 |
| European sovereignty | 2.5 of 5 |
Machine translation & AI quality
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
A dozen named engines from Microsoft and Google to DeepL can be configured and called at file or segment level, and LLM translation runs through dedicated profiles with custom prompts influencing tone, style and domain, plus token-limit chunking and retries. We found no public information on quality estimation that routes weak segments to human review, on glossaries applied during machine translation, or on any published translation quality evaluation. 3 4
The App Developer
Twelve named engines from Microsoft to DeepL plus Google AutoML and KantanMT, configured per profile and runnable at file or segment level, and LLM translation where a custom prompt shapes tone, style and domain — that is real engine choice, more than most. But the pages never publish a language list, show glossaries applied during machine translation, describe quality estimation, or publish any quality evaluation, so I can steer the engine but not measure the output. 1 3 4
The In-House Document Translator
Twelve named engines including DeepL, Microsoft and Google AutoML are configurable in the platform settings and can be called at file or segment level, and an LLM option accepts custom prompts for tone, style and content domain — with Word, PowerPoint and InDesign among the supported formats. The captured pages do not show a published language list beyond a marketing line about 30+ languages, any per-segment quality scoring, or a published evaluation of translation quality. 1 3 4 8
The Data Protection Officer
Twelve named engines including DeepL, Microsoft, Google AutoML and KantanMT are configurable and callable at file or segment level, and LLM translation runs through machine translation profiles where a custom prompt steers tone, style and domain, with document translation across office and DTP formats from Word and PowerPoint to InDesign and FrameMaker. We found no public information on glossaries applied during machine translation, on automatic quality estimation per segment, or on any published evaluation of translation quality. 1 3 4 8
The E-Commerce Marketer
Twelve named engines including DeepL comfortably cover my six shop languages, LLM translation accepts a custom prompt for tone and domain, and Google AutoML is on the list for custom models. What the captured pages do not describe is glossaries applied during machine translation, automatic quality scoring, or any published evaluation of quality, so I cannot judge raw output before a human eye lands on it. 3 4
The Skeptic
Twelve named engines plus LLM profiles where the customer writes a custom prompt for tone, style and domain are documented, usable at file or segment level. But the pages publish no language list, never say a glossary or formality setting is applied during machine translation, and we found no public information on quality estimation, custom models trained on the customer's own translations, or any published evaluation. 3 4
Translation memory, terminology & review workflow
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
Translation memory, terminology, vendor management and finance are on the feature list, a dedicated right turns the editor into a review-only workspace, and QA profiles configurable at project or organisation level check tags, terminology, numbers and spelling with a severity report I can hand an auditor. Automated job assignment and conditional workflow automation appear on higher plans alongside vendor performance dashboards, though we found no public information on an in-context visual editor, screenshots for translators, or QA rules that block delivery. 1 2 5 6 7 12
The App Developer
The QA suite is the strongest part: profiles configurable at project or organization level checking tags, terminology, formatting and numbers, a review panel with resolve, ignore and notes, incremental runs and an exportable report with severity. Workflow automation with conditional routing on the top tier, a review-only role that comments and moves status without touching text, 125 granular rights and vendor management with invoicing cover most of what I run daily. The pages show no in-context or visual editor, no screenshots or context for translators, and no named linguistic quality framework. 1 2 5 6 7
The In-House Document Translator
This is a full management platform: translation memory and termbases, QA profiles configurable at project or organization level checking terminology, tags, spelling and numbers, a reviewer-only right that allows commenting and status changes without altering the text, eleven ready-made profiles built from 125 granular rights, plus vendor management with invoicing, vendor performance dashboards and conditional workflow automation. I found no public information on style guides applied by the machine translation, an in-context visual editor, or linguistic quality assessment against a named framework. 1 2 5 6 7
The Data Protection Officer
Translation memory and termbases are shared resources the API can search and export, QA profiles with configurable rules for spelling, terminology, tags and numbers run at project or organisation level with severity reporting, and a dedicated review-only right lets reviewers flag issues and move segments forward without editing text, backed by eleven predefined profiles built from 125 granular rights. Vendor assignment, invoicing and conditional workflow automation are documented, including back-translation workflows and segment-level audit trails for life sciences. We found no public information on a visual in-context editor, on blocking QA rules, or on a named linguistic quality assessment framework. 1 2 5 6 7
The E-Commerce Marketer
This is a genuine project machine: translation memory and central terminology, automated job assignment, back-translation and conditional workflow automation on the upper tiers, QA profiles configurable per project with terminology, tag and number checks, a dedicated review-only role, and vendor management with invoicing built in. I found no public information on an in-context or visual editor showing my product pages as customers see them, which keeps me a step below the top of the scale. 1 5 6 2
The Skeptic
The QA machinery is real and configurable: profiles per project or organisation, rules for tags, terminology, spelling and numbers, severity reports, incremental results, a review-only right that locks the text, 125-granular-rights profiles and conditional workflow automation on the Enterprise tier. It stays below the top because we found no public information on an in-context or visual editor, screenshots and context for translators, a named linguistic quality framework, or QA rules that block delivery. 1 2 5 6
Integrations, file formats & developer tools
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
The format list is genuinely broad, from XLIFF, PO, JSON and iOS strings to Office, InDesign IDML, FrameMaker and DITA, with custom extraction rules and a presets library, backed by a REST API reaching projects, jobs, workflows, resources, QA and invoices, GitHub and GitLab connectors, webhooks and continuous push-pull with versioning. We found no public information on a CLI, SDKs, over-the-air updates, a status page or documented API limits, and the connector list names categories rather than specific tools. 1 7 8
The App Developer
The format list is everything I ship — JSON, YAML, PO, iOS strings, XLIFF, InDesign IDML, even Trados bilingual — with custom extraction rules for XML and CSV, and the REST API reaches projects, jobs, workflows, QA and invoices, plus GitHub and GitLab push-pull and webhooks into CI builds. What I reach for daily is absent from the captured pages: no documented CLI, no SDKs, no over-the-air updates, no pull requests opened for me, no public status page and no published API limits. 1 7 8
The In-House Document Translator
A REST API reaches projects, jobs, workflows, resources, QA and invoices, GitHub and GitLab sync pushes source strings and pulls translations back, webhooks fire on project and job status changes to drive CI/CD builds, and the format list is broad — XLIFF, PO, JSON, YAML, Word, Excel, PowerPoint, InDesign IDML, FrameMaker MIF and more — with custom extraction rules. I found no public information on a CLI, SDKs, over-the-air updates, named CMS or design connectors beyond a general claim, or documented API limits. 1 7 8
The Data Protection Officer
A REST API reaches projects, jobs, workflows, resources, QA and invoices, with GitHub and GitLab sync, webhooks on project and job status changes, and connectors for CMS, cloud storage and game engines; the format list is unusually broad, from XLIFF and iOS strings to InDesign, FrameMaker and Trados bilingual files, with custom extraction rules and a presets library. We found no public information on a command-line tool, SDKs, over-the-air updates, a public status page, or documented API limits. 1 7 8
The E-Commerce Marketer
The format list is enormous — XLIFF, PO, JSON, iOS strings, InDesign, even Trados bilingual — with a REST API spanning projects, jobs, QA and invoices, GitHub and GitLab sync with versioning, and webhooks on status changes. I found no public information on a Shopify connector, a CLI, SDKs or over-the-air updates, and connectors are named only as categories such as CMS platforms, so a shop owner without a developer would lean on the API. 7 8 1
The Skeptic
A REST API covering projects, jobs, workflows, resources and invoices, GitHub and GitLab push/pull with versioning, webhooks wired for CI/CD, and a format list running from XLIFF, PO and iOS strings to InDesign, FrameMaker and Trados bilingual files — the pipes exist. We found no public information on a CLI, SDKs, over-the-air delivery, a public status page or documented API limits, and the connector list names only the Git hosts while CMS, cloud storage and game-engine support stays generic. 1 7 8
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 security page shows much of what I need: AES-256 at rest, TLS 1.2+ in transit, encrypted backups, ISO 27001 and SOC 2 Type II, an exportable activity log, single sign-on, and single-tenant hosting on the enterprise tier, with a data processing agreement and a sub-processor annex available on request. The engines a translation can be sent to include US providers, the LLM providers behind the profiles are not named, and we found no public information on retention of translated texts or on whether customer content is used to train any model. 2 3 4
The App Developer
AES-256 at rest and TLS in transit, SAML single sign-on, enforceable MFA, an exportable filterable activity log, granular rights, supplier isolation, ISO 27001 and SOC 2 Type II, a subprocessor list in the DPA annex and single-tenant hosting on the enterprise tier — a serious security posture. But I found no public information on how long translated texts are retained, whether customer content trains anyone's models, or zero-retention terms with the LLM providers, and the data processing agreement is available on request rather than published. 2 9 10
The In-House Document Translator
The security documentation is solid: AES-256 at rest, TLS 1.2+ in transit, ISO 27001 and SOC 2 Type II, exportable audit logs, SSO and enforceable MFA, and a sub-processor list in the annex of the data processing agreement. But nowhere in the captured pages is there a statement on how long translated texts are kept, whether they are deleted after delivery, or whether they are used to train models — and while the engines the platform can call are named, the pages say nothing about restricting or switching off third-party processing. 2 3 9 10
The Data Protection Officer
AES-256 at rest and TLS 1.2+ in transit, SAML 2.0 single sign-on, enforceable MFA, an exportable activity log, 125 granular rights, ISO 27001 and SOC 2 Type II, plus single-tenant hosting on the enterprise tier give a strong control set, and the engines a project calls are named and configurable, with LLM credentials held in specialised profiles. My two core questions stay open: we found no public information on how long source and target texts are retained, whether any content is used to train models, or on zero-retention terms with LLM providers. 2 3 4
The E-Commerce Marketer
ISO 27001 and SOC 2 Type II are stated, AES-256 and TLS are documented, there is an exportable activity log, 125 granular rights, SAML single sign-on, and a single-tenant option at enterprise level. I found no public statement on whether customer texts train models, how long translations are retained, or whether routing text to the named engines and LLM providers can be switched off — the questions that matter before product names and margins flow through. 2 3 4
The Skeptic
The security page answers several of my standing questions: AES-256 at rest, TLS 1.2+, SOC 2 Type II, ISO 27001, SSO, MFA, an exportable activity log, a sub-processor annex in the DPA, and third-party engines named. It does not answer the ones that matter most for the text itself — we found no public information on how long translated texts are retained, whether any model is trained on customer content, zero-retention terms with LLM providers, or per-project restriction of third-party AI — and the single-tenant Enterprise option is still the vendor's cloud, not a deployment the customer controls. 2 3 4
Data export, portability & self-hosting
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
Termbases export to TBX version 3 (ISO 30042, 2019) or Excel with filters by change date, status, bookmarks and custom fields, translation memory and termbases are searchable and exportable through the API with TMX named among the endpoints, comments ride along in the Excel export, and user, vendor and client records have a documented backup. The captured hosting information states single-tenant hosting is still the vendor's own cloud with no self-hosted option, and we found no public information on data return or deletion at termination. 7 10 11 12
The App Developer
Termbases export as TBX 3 (ISO 30042, 2019) or Excel including comments and custom fields, the API can search and export translation memory and termbases, and there is a documented export wizard plus backup of internal users, vendors and clients. The flat exports and TBX version 1 drop term alternatives and most properties, so leaving cleanly means TBX 3, and I found no public information on importing a translation memory from another tool, on data return or deletion at termination, or on any self-hosted edition. 7 10 11 12
The In-House Document Translator
Termbases export to TBX version 3 (ISO 30042, 2019) or Excel with the limitation of older formats honestly documented, an export API page covers TMX, Excel, CSV, ODS and TBX, the API searches and exports translation memory, and internal users, vendors and clients can all be backed up. I found no public information on importing memory or glossaries from another tool, on data return or deletion at termination, or on a self-hosted edition — the captured pages show hosting only in the vendor's own EU or US cloud. 7 10 11 12
The Data Protection Officer
Termbases export in TBX version 3 (ISO 30042, 2019) or Excel through an export wizard that filters by status, change date and custom fields, and the API can search and export translation memory alongside project deliverables, with an HTML export that preserves inline tags for reimport. We found no public information on importing memory or terms from another tool, on the return or deletion of data when a contract ends, or on a self-hosted edition. 7 12
The E-Commerce Marketer
Termbases export to TBX version 3 under ISO 30042 or to Excel with comments and custom fields, and the API can search and export translation memory, so my glossary and memory could leave with me. I found no public information on termination and data-return terms or a documented migration path beyond Trados bilingual file support, and the captured pages show hosting remains Wordbee's own cloud. 7 12 8 10
The Skeptic
Termbases export to TBX version 3 under ISO 30042 preserving alternatives and properties, the API exports translation memory as TMX, CSV or ODS, exports filter by status, change date and custom fields, and even internal users, vendors and clients can be backed out of the system. The exit still has holes: we found no public information on a documented migration path from a named competitor or on data return and deletion at termination, and TBX version 1 strips term alternatives — take the ISO 30042 option or part of the termbase stays behind. 7 10 11 12
European sovereignty
panel opinion
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
Data residency is a documented choice between EU and US facilities on the vendor's own cloud, the copyright names Wordbee SARL as the entity, and ISO 27001, SOC 2 and a data processing agreement are in place with a sub-processor annex available on request. The chain is not shown end to end: we found no public information confirming the contracting entity's jurisdiction, the named infrastructure behind the EU region, or a published sub-processor list with locations, and the engine list includes US providers. 2 3 4
The App Developer
I can choose EU or US data residency with encrypted backups and ISO 27001-certified facilities in both regions, and a subprocessor list sits in the DPA annex — but the DPA itself is only on request, the hosting infrastructure is not named, and the contracting entity's jurisdiction is unconfirmed, with the captured pages giving different entity names (Wordbee SARL and Wordbee S.A.). The machine translation engines include US providers and no safeguard for that part of the chain is stated; single-tenant hosting is still the vendor's own cloud, with no self-hosted option. 2 4 9
The In-House Document Translator
Data residency can be set to the EU with ISO 27001-certified facilities in both regions, a data processing agreement is available on request, and a sub-processor list sits in its annex. But the pages do not state where the contracting entity is seated, and the machine translation chain runs through named US-based and European engine providers with no stated safeguard — for trade secrets in a draft contract, that chain stays unproven. 2 3 9
The Data Protection Officer
EU data residency is selectable, the ISO 27001 facilities are named as EU and US, and the legal pages name Wordbee SARL as the entity, a European company form. The sub-processor list sits in the annex of a data processing agreement available on request, with no locations stated on the public pages, and we found no public information on safeguards for the Microsoft and Google engines a project may call, on where LLM providers process text, or on a self-hosted edition. 2 3 4 9
The E-Commerce Marketer
Data residency can be set to EU facilities, the ISO 27001 certified facilities span the EU and US, and a data processing agreement with a sub-processor annex is available on request. The contracting entity's jurisdiction is not stated on the captured pages, sub-processor locations are not published, and the engine list includes Microsoft and Google with no safeguard described for those transfers, so the chain is only partly visible. 2 3
The Skeptic
EU or US hosting is selectable and ISO 27001 covers facilities in both, with a DPA and a sub-processor annex available on request — but the choice is between two of the vendor's own clouds and we found no public information on a self-hosted or on-premises edition. The captured pages give different entity names for the vendor, Wordbee S.A. and Wordbee SARL, and state no jurisdiction, no named hosting infrastructure and no locations for the engines or subprocessors, so I cannot certify any part of the chain as European. 2 3 4 9
Pricing transparency
not rated — the vendor publishes no price
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
Four plans are public with their contents and user counts, from Essential with 5 power users and 50 linguists up to Infinity with unlimited linguists, white-label branding and single sign-on, and a free trial plus a small freelance edition are mentioned for building custom rules. No price figures appear in any of the captured pages, so a buyer cannot compute an annual cost or see how seats, languages or machine translation volume scale. 1 8
The App Developer
Four tiers are public by name with their linguist counts (50, 100, 500, unlimited) and which features land where — single sign-on on Infinity, conditional automation on Enterprise — and a free trial of a small freelance edition is mentioned. But no price figure of any kind appears, so I cannot compute an annual cost for my team, and the pages say nothing about overage, extra seats, add-ons or minimum term. 1 8
The In-House Document Translator
Four tiers are named — Essential, Smart, Enterprise and Infinity — with linguist limits of 50, 100, 500 and unlimited and their headline features published, and a free trial of a small freelance edition is mentioned. But no price figure appears on any captured page, so a buyer cannot begin to compute an annual cost. 1 8
The Data Protection Officer
Four tiers — Essential, Smart, Enterprise and Infinity — are public with their linguist limits of 50, 100, 500 and unlimited and their headline features, alongside a free trial and a small freelance edition. We found no public prices for any tier, and no public information on how cost scales with volume, what machine translation or AI usage costs, or on minimum terms. 1 8
The E-Commerce Marketer
Tier names, linguist counts from 50 up to unlimited, and feature inclusions such as single sign-on and white-label branding are public, and a free trial is mentioned. But I found no public prices on any captured page — no monthly figure, no per-word or per-language cost, no overage rule — so I cannot begin to estimate what a growing catalogue would cost me each month. 1 8
The Skeptic
Four tiers are public down to their linguist limits — 50, 100, 500, unlimited — with their headline features, and a free trial or small freelance edition is mentioned. But the captured pages show no price figure for any tier and we found no public information on overage handling, add-on or machine translation volume pricing, minimum term or VAT treatment, so no buyer can compute an annual cost from what is published. 1 8
European sovereignty — proven facts
2 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
EU region selectable
unverified
Why unverified?The choice is only between vendor-operated EU and US cloud facilities; single-tenant hosting is still Wordbee's cloud, and no self-hosted or on-premises option is offered. |
1/1 pts | 2 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | On request | 0/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Wordbee
Is Wordbee European?
Not determined: the vendor’s pages as captured do not say where Wordbee is based.
Where does Wordbee store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does Wordbee have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to Wordbee?
As of 19 Nov 2026, the panel rates LingoHub (3.5/5), Crowdin (3.5/5) and SimpleLocalize (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 LingoHub (EU-Made, Austria). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Wordbee alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 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 — Hosting options. The choice is only between vendor-operated EU and US cloud facilities; single-tenant hosting is still Wordbee's cloud, and no self-hosted or on-premises option is offered.
- 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.
- We found no public information on pricing on the pages we read (wordbee.com, wordbee.com/platform/security, help.wordbee.com/wbt/which-machine-translation-engines-does-wordbee-sup, help.wordbee.com/wbt/machine-translation-with-llms, help.wordbee.com/wbt/qa-checks, help.wordbee.com/wbt/quality-assurance and 6 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 4 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
- 1 product 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
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.wordbee.com Checked 10 Nov 2026 Details →
- 2 Security / trust page — found from the homepage www.wordbee.com Checked 10 Nov 2026 Details →
- 3 Machine translation & AI quality — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 4 Machine translation & AI quality — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 5 Translation memory, terminology & review workflow — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 6 Translation memory, terminology & review workflow — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 7 Integrations, file formats & developer tools — found from sitemap www.wordbee.com Checked 10 Nov 2026 Details →
- 8 Integrations, file formats & developer tools — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 9 Confidentiality of translated content — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 10 Confidentiality of translated content — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 11 Data export, portability & self-hosting — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →
- 12 Data export, portability & self-hosting — found from sitemap help.wordbee.com Checked 10 Nov 2026 Details →