SYSTRAN
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 SYSTRAN · www.systransoft.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.
SYSTRAN at a glance
- Vendor
- SYSTRAN
- Headquarters
- Incorporated in France source, captured 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 SYSTRAN 2.5/5, the mean of 6 judges. SYSTRAN is scored as a machine translation engine, not a managed localization workflow, and that division runs through the bench. 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
SYSTRAN is scored as a machine translation engine, not a managed localization workflow, and that division runs through the bench. It is strongest on content confidentiality and sovereignty, both scored 6 to 7: the captured pages state the translation engines do not store or use customer data, that file translations can be configured for automatic deletion, and that an on-premise edition keeps data inside the customer's information system. Sovereignty rests on a French contracting entity under French law with exclusive jurisdiction of the courts of Paris, though cloud hosting is named only as Newp in data centers across customer regions, and we found no public information on subprocessors or a data processing agreement. Workflow and review is the weak point at 1 to 2: we found no public information on a translation memory, glossary, review stages or QA checks in the product itself, and the pages point to Trados, memoQ and other external CAT tools instead. Scores cluster tightly, with no criterion splitting the judges by more than one point. Pricing appears only as a 14-day free trial.
Speaks for it
- Own PNMT neural engine covering up to 55 languages with document translation in 30+ formats including Office, PDF, XML and IDML
- Documented REST API secured with HTTPS, a browser extension and connectors for Confluence, Adobe, Relativity and a wide range of CAT tools
- Stated that the translation engines do not store or use customer data, with configurable automatic deletion for file translations
- On-premise edition documented to run behind the customer's firewall, with data not leaving the customer's information system
- French contracting entity registered at Nanterre under French law, with exclusive jurisdiction of the courts of Paris
Held against it
- We found no public information on a translation memory, glossary, review or approval stages or automated QA checks in the product itself
- Cloud hosting described only as Newp in data centers across customer regions, with no stated location
- We found no public information on a subprocessor list or a data processing agreement
- We found no public information on exporting translation memory or glossaries in open formats, or on data return at termination
- Only a 14-day free trial is documented, with no public information on tier prices or on-premise edition costs
Best for
- You already run a CAT or TMS tool such as Trados, memoQ or Phrase and want a translation engine to plug into it
- You translate confidential documents and can deploy the on-premise edition behind your own firewall
- You buy under French law and value a French contracting entity with exclusive jurisdiction of the courts of Paris
- Your data policy requires stored file translations to be deletable automatically after a time you configure
Avoid if
- You expect translation memory, glossaries, review stages and QA checks inside one product — the pages document that work in external tools such as Trados and memoQ
- Your compliance review needs named cloud residency and a subprocessor list — hosting is described only as Newp in data centers across customer regions
- You are choosing your first localization tool and have no CAT or TMS setup to carry the review workflow
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 2 of 5 |
| Translation memory, terminology & review workflow | 1 of 5 |
| Integrations, file formats & developer tools | 2.5 of 5 |
| Confidentiality of translated content | 3 of 5 |
| Data export, portability & self-hosting | 2 of 5 |
| European sovereignty | 3 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
Their own PNMT neural engine covers up to 55 languages, and document translation handles 30-plus formats including Office, PDF, XML and IDML, which is solid engine coverage. But the captured pages say nothing about glossary or termbase application during translation, formality settings, adaptive models trained on our translation memory, or any published quality evaluation with its method — only marketing claims of the best quality on the market — so it sits above basic but well short of controlled, steerable MT. 1 3 4 7
The App Developer
Their own PNMT neural engine with document translation across 30+ formats including Office, PDF, XML and InDesign is real muscle, and up to 55 languages with industry adaptation claimed for legal, automotive, IT and tourism — but the claim of quality "better than a non-native speaker" stands without a published method, and we found no public information on a language list, glossary use, formality settings or per-segment quality estimation. 1 3 4 7
The In-House Document Translator
Their own Pure Neural engine covering up to 55 languages, with document translation in more than thirty formats including Office, PDF and IDML, is close to what I need for manuals and contracts. But I found no public information on glossaries or company terminology being applied during translation, on a formality setting, or on any published quality evaluation with its method. 1 3 4 7
The Data Protection Officer
The vendor's own PNMT neural engine is described in some detail, with document translation in 30+ formats including Office, PDF, XML and InDesign markup into up to 55 languages, and a claim of quality adapted to legal, automotive, IT and tourism contexts. The language list itself is not published, we found no public information on glossaries, formality or tone settings, quality estimation or custom per-customer models, and the quality claim is marketing language with no published evaluation or method. 1 3 4 7
The E-Commerce Marketer
Their own Pure Neural engine covering up to 55 languages, with document translation across 30+ formats including Office, PDF and IDML, is the core of what I would need for product pages and catalogues. But I found no public information on glossaries or a formality setting that would keep my brand terms consistent across five languages, and no published quality evaluation with its method. 1 3 4 8
The Skeptic
An own neural engine (PNMT, deep learning, training phase of a few weeks) covering up to 55 languages, plus document translation across 30+ formats including Office, PDF, XML and IDML. But the language list itself is not shown, we found no public information on glossaries, formality or tone settings, custom models trained on the customer's own translations, or any quality evaluation with a method behind the claim of quality "better than a non-native speaker". 1 3 4 7
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
The pages show SYSTRAN as a machine translation engine that plugs into external tools — Across, Trados, memoQ, Smartling, Phrase and a dozen more are listed as integrations, so translation memory and review workflow would live in those tools rather than in SYSTRAN. Role-based access control is documented and stored file-translation items can be auto-deleted, but we found no public information on a translation memory, termbase, review and approval stages, or automated QA checks in the product itself. 5 7 8
The App Developer
SYSTRAN is a machine translation engine, not a localization workflow tool: we found no public information on translation memory, a termbase, review stages or automated QA checks inside the product itself. What the pages do show is a long list of integrations with external TMS and CAT tools such as Trados, memoQ and Phrase, where that work would happen. 1 5
The In-House Document Translator
The captured pages describe no translation memory, termbase, review stage or automated QA checks in the product itself; the integrations page instead names Trados, memoQ, Across and many other TMS and CAT tools as the places where that management happens, with SYSTRAN supplying the engine behind them. As a translator with no wish for a TMS that division of labour suits me, but as managed workflow the captured pages tell me almost nothing. 5 7
The Data Protection Officer
The captured pages describe a translation engine and suite, and the only workflow evidence is a long list of integrations with external TMS and CAT tools such as Trados, memoQ, Phrase and Smartling. We found no public information on a translation memory, central glossary, review or approval stages, automated QA checks or translator roles within the product itself. 1 5
The E-Commerce Marketer
The pages I read show role-based access control but no translation memory, no glossary where I could fix a bad product name by hand, no review stages and no automated checks. The long list of CAT tools like Trados, memoQ and Phrase suggests the editing workflow happens in other tools, which for a shop with no translator on staff leaves the hands-on fixing part unresolved here. 5 7 8
The Skeptic
The captured pages describe a machine translation engine whose project management is expected to live elsewhere: the vendor's own integration list points to Trados, memoQ, Phrase, Smartling and a dozen other CAT and TMS tools. We found no public information on a translation memory, a central termbase, review or approval stages, QA checks, or roles per language inside the product itself. 5
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
A REST API over HTTPS is documented, with connectors for named tools across content management (Confluence, Adobe), e-discovery (Relativity) and the TMS and CAT landscape, a browser extension for web pages, and document translation across 30-plus formats including XML and IDML. We found no public information on Git repository sync, CI pipelines, SDKs, a CLI or webhooks, so it stops short of the developer-facing depth I would need. 1 5
The App Developer
A documented REST API secured with HTTPS, a browser extension, document formats including Office, PDF, XML and InDesign IDML, and connectors to Confluence, Adobe, Relativity and two dozen TMS and CAT tools is a decent surface. For my stack, we found no public information on a CLI, SDKs, Git repository sync, CI pipelines, over-the-air updates, or software string formats like JSON, XLIFF or iOS strings. 1 5
The In-House Document Translator
A documented REST API secured with HTTPS, a browser extension for web pages, and named connectors for Confluence, Adobe and Relativity alongside the whole CAT-tool list cover my Word and PDF round trips well. I found no public information on Git repository sync, continuous integration, a command-line tool or SDKs. 1 5
The Data Protection Officer
A REST API secured with HTTPS is documented, together with a browser extension for web pages, document support in 30+ formats, and named connectors across content management (Confluence, Adobe), office, web and chat applications and e-discovery tools, compatible with both cloud and server deployments. We found no public information on a CLI, SDKs, Git repository sync, CI pipelines or webhooks. 1 5
The E-Commerce Marketer
A documented REST API, a browser extension, 30+ document formats and named connectors for Confluence, Adobe and a wide range of CAT tools are real. But I found no public information on a Shopify or other e-commerce connector, Git sync, a CLI or SDKs — with no developer on staff, that would leave me wiring up the API myself. 1 5
The Skeptic
A documented REST API over HTTPS, client-server architecture queried from fixed and mobile devices and dozens of third-party office, web or chat applications, a browser extension, and named connectors spanning Confluence, Adobe and Relativity alongside a long CAT-tool list, with document translation in 30+ formats. We found no public information on a CLI, SDKs, Git or CI sync, webhooks, over-the-air delivery, or documented API limits. 1 5
Confidentiality of translated content
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 pages state their translation engines do not store or use your data, offer configurable automatic deletion of stored file translations, name HTTPS and TLS, role-based access, regular penetration tests and an ISO 27001 audit of facilities, teams, policies and procedures, plus an on-premise option where data never leaves our system. We found no public information on encryption at rest, single sign-on, audit logs or a data processing agreement, which keeps it below the top band. 5 7 8
The App Developer
The security pages are unusually concrete: engines stated not to store or use customer data, configurable automatic deletion for file translations, role-based access control, regular pentests at major and minor releases, HTTPS/TLS encryption, ISO 27001 stated, and an on-premise edition where "client data, confidential information and trade secrets do not leave your information system". We found no public information on audit logs, single sign-on, encryption at rest, or the certification's scope. 2 5 7 8
The In-House Document Translator
This comes close to the written promise I ask for: the engines "do not store or use your data and are compliant with all local privacy laws", file translations can be configured for automatic deletion after a time I choose, and the on-premise server is described so that confidential information and trade secrets never leave our own system, with HTTPS and TLS, role-based access, ISO 27001 and regular penetration tests besides. I found no public information on a data processing agreement, single sign-on, audit logs or encryption at rest, and the automatic deletion is described only for file translations. 5 7 8
The Data Protection Officer
For letters to our members this is the decisive page: it states the translation engines do not store or use customer data, that file translation storage can be configured for automatic deletion after a specified time, and it documents an on-premise edition where confidential information and trade secrets never leave the customer's information system. Role-based access control, HTTPS/TLS encryption, regular penetration tests and an ISO 27001 claim are also stated, though the certification's scope is not given, and we found no public information on retention defaults for the cloud service, encryption at rest, audit logs, single sign-on or a data processing agreement. 2 5 7 8
The E-Commerce Marketer
For my customer data this reads well: the engines are stated not to store or use data, file translations can be set to auto-delete after a time I configure, encryption via HTTPS and TLS, role-based access, ISO 27001 named, and an on-premise edition where data never leaves my information system. I found no public information on audit logs, single sign-on, a data processing agreement, or the scope of the ISO 27001 certification. 5 7 8
The Skeptic
Encryption via HTTPS and TLS, role-based access control, configurable automatic deletion for file translations such as PDFs, regular penetration tests on major and minor releases, a statement that the translation engines "do not store or use your data", an ISO 27001 claim without a stated scope, and a private or on-premise deployment where client data does not leave the customer's information system. We found no public information on retention for translations generally, single sign-on, audit logs, encryption at rest, or a data processing agreement. 2 5 7 8
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
The strongest exit story is SYSTRAN Server, an on-premise deployment behind our own firewall or in their private cloud with unlimited user access points and translation volumes — on that path the assets sit on our infrastructure. We found no public information on exporting translation memory as TMX or glossaries as TBX, import from another tool, or data return and deletion on termination; the REST API is described for calling translation services rather than for reading stored assets. 1 5 7
The App Developer
The on-premise SYSTRAN Server edition and a REST API give a real path for the engine itself, and documents in 30+ formats can be downloaded; but we found no public information on exporting translation assets in open formats like TMX or TBX, a migration path from named competitors, or data return and deletion on termination. Their open-source participation is described as sharing know-how with a community, not product code we could run. 1 4 5 7
The In-House Document Translator
Documents translated in more than thirty formats come back to me as files I keep, and the on-premise server edition runs on our own infrastructure, which is my preferred exit route. I found no public information on exporting translation memory or terminology, on importing from another tool, or on what is returned or deleted when a contract ends. 1 7
The Data Protection Officer
The strongest exit story is the on-premise server edition, documented to run behind the customer's firewall with data not leaving the customer's information system, plus translated documents produced in 30+ formats. We found no public information on export of translation memory or glossaries in open formats, import from another tool, or the return or deletion of data on termination. 1 7 8
The E-Commerce Marketer
Document translation across 30+ formats and an on-premise edition that keeps everything inside my own system give me something to hold onto. But I found no public information on exporting translation memory or glossaries in open formats, importing from another tool, or what happens to my translations if I terminate. 1 7 8
The Skeptic
Documents come back translated across 30+ formats, and the on-premise server edition — behind the customer's firewall or in a private SYSTRAN cloud, with unlimited users and volumes — keeps everything in the customer's own environment. We found no public information on export of translation memory or termbase in open formats such as TMX or TBX, on termination and data-return terms, or on a documented migration path. 1 7 8
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
The contracting entity is French — SYSTRAN under ChapsVision, registered at Nanterre under French law — hosting runs with Newp in data centers across customer regions, and translation runs on their own PNMT engine rather than a third-party MT chain. The documented on-premise edition keeps every text on the customer's own servers and ISO 27001 is stated, but cloud data residency is not named, no subprocessor list with locations is published, and we found no public information on a data processing agreement. 1 2 3 7 8
The App Developer
The contracting side is solidly French — Nanterre trade register, French law, Paris courts, parent ChapsVision — with a documented on-premise edition that keeps every text on the customer's own servers and ISO 27001 stated. Hosting is named only as Newp with location unstated, cloud residency is described as "data centers across customer regions", and we found no public information on a published data processing agreement or a subprocessor list with locations. 1 2 4 7 8
The In-House Document Translator
The contracting side is clearly French: the legal notice names ChapsVision as publisher, registered at Nanterre, with French law and the exclusive jurisdiction of the Paris courts, translation runs on their own neural engine rather than a third-party provider, and an on-premise edition is documented to keep every text on our own servers. The cloud chain stays vague — hosting named as Newp with data centres only described as "across customer regions" — and I found no public information on a data processing agreement or a list of subprocessors. 1 2 4 7 8
The Data Protection Officer
The contracting footprint is French — Nanterre trade register, French governing law, exclusive jurisdiction of the courts of Paris — one captured page states SYSTRAN belongs to ChapsVision, the translation engine is the vendor's own rather than a named third-party provider, and a documented on-premise edition keeps every text on the customer's own servers. Cloud hosting is described only as data centers across customer regions under a host named Newp without a stated location, no subprocessor list is published, and we found no public information on a data processing agreement. 1 2 3 7 8
The E-Commerce Marketer
As a Munich shop I like what I see: a French contracting entity under French law with Paris jurisdiction, hosting by Newp in data centres across customer regions with GDPR cited, and a documented on-premise edition that keeps every text on my own servers. I found no public information on a data processing agreement or a subprocessor list with locations, and the cloud hosting regions are only vaguely described. 1 2 4 7 8
The Skeptic
A French contracting entity registered at Nanterre under French law with exclusive jurisdiction of the courts of Paris, an own neural engine so no third-party machine translation or LLM provider is named in the chain, and an on-premise edition documented to keep every text on the customer's own servers. Against that, the hosted chain leaves data residency stated only as "data centers across customer regions", the host Newp's location is not stated, subprocessors are not listed with locations, and we found no published data processing agreement. 1 2 7 8
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
The only pricing-adjacent information is a 14-day free trial. We found no public prices, tiers, volume or seat scaling, or terms for the on-premise edition, so a real annual cost for a fourteen-language operation cannot be computed from the captured pages. 2 3 8
The App Developer
The only pricing fact on the pages is a 14-day free trial; we found no public information on tier prices, per-character or per-seat scaling, volume limits, what machine translation volume costs, or what the self-hosted edition costs. A real annual cost cannot be computed from these pages. 2 3 8
The In-House Document Translator
All the captured pages give me is a 14-day free trial; I found no public information on tier prices, per-character or per-seat rates, volume limits or overage, so I cannot begin to compute an annual cost before talking to sales. 2 3 8
The Data Protection Officer
Only a free trial, stated at 14 days, is documented. We found no public information on tier prices, how cost scales with volume, what machine translation volume or features cost extra, or the licence and support cost of the on-premise server edition, so an annual cost cannot be computed from the captured pages. 2 8
The E-Commerce Marketer
All I can find publicly is a 14-day free trial — no tier prices, no word on how cost scales with catalogue size, languages or users, and no term or setup conditions. I cannot compute a monthly figure for the spring season from these pages. 2 8
The Skeptic
The only pricing-adjacent fact on the captured pages is a 14-day free trial. We found no public information on tier prices, how cost scales with characters, words or volume, included users or languages, add-on costs, or the price or licence of the on-premise edition — a buyer has no way to estimate an annual cost from these pages. 2 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 |
Incorporated in FR
unverified
Why unverified?The legal notice names Chapsvision as the website publisher; no excerpt explicitly states Chapsvision owns SYSTRAN, though the site is branded "Systran By ChapsVision". |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 7 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about SYSTRAN
Is SYSTRAN European?
Not determined: the vendor’s pages as captured do not say where SYSTRAN is based. Its vendor, SYSTRAN, is incorporated in France, per the vendor’s page captured 10 Nov 2026.
Where does SYSTRAN store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does SYSTRAN have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to SYSTRAN?
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: SYSTRAN 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 — Legal entity. The legal notice names Chapsvision as the website publisher; no excerpt explicitly states Chapsvision owns SYSTRAN, though the site is branded "Systran By ChapsVision".
- 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.
- 37 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
- 12 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
- 8 pricing 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
- 6 support 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
- 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
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.systransoft.com Checked 10 Nov 2026 Details →
- 2 Privacy policy — found from the homepage www.systransoft.com Checked 10 Nov 2026 Details →
- 3 Machine translation & AI quality — found from sitemap www.systransoft.com Checked 10 Nov 2026 Details →
- 4 Machine translation & AI quality — found from sitemap www.systransoft.com Checked 10 Nov 2026 Details →
- 5 Integrations, file formats & developer tools — found from sitemap www.systransoft.com Checked 10 Nov 2026 Details →
- 6 Integrations, file formats & developer tools — found from sitemap www.systransoft.com Checked 10 Nov 2026 Details →
- 7 Confidentiality of translated content — found from sitemap www.systransoft.com Checked 10 Nov 2026 Details →
- 8 Confidentiality of translated content — found from sitemap www.systransoft.com Checked 10 Nov 2026 Details →