Transit
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by STAR AG · www.star-group.net
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.
Transit at a glance
- Vendor
- STAR AG
- Headquarters
- Incorporated in Switzerland source, captured 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Transit 2.5/5, the mean of 6 judges. Transit is STAR AG's translation and localization suite, spanning Transit, TermStar, CLM WebEdit and STAR machine translation. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Transit is STAR AG's translation and localization suite, spanning Transit, TermStar, CLM WebEdit and STAR machine translation. The most consistent strength is workflow and review, with scores clustering at 6 and no variation: a company-wide terminology pool that dynamically highlights disallowed terms, and browser-based review with approval, segment comments, page-layout PDF context and documented revision history. Machine translation follows at 5 to 7, crediting its own engine, controlled gateways to DeepL, Google and Microsoft Translator, and a system trained on the customer's own texts and terminology; lower scores note no published language list or quality evaluation. Sovereignty scores spread from 2 to 4: higher scores credit STAR AG in Ramsen, Switzerland as contracting entity, a data protection officer at STAR Deutschland in Sindelfingen and a privacy statement under both the Swiss revDSG and the GDPR; lower scores cite no public information on hosting of translated texts, a data processing agreement or engine locations. Content confidentiality sits at 4, integrations and formats at 4 to 5, portability and exit at 3 to 4; buying runs through a non-binding quote request.
Speaks for it
- Company-wide terminology pool in TermStar, with dynamic highlighting of disallowed terms and term suggestions on the fly
- Browser-based translating and reviewing in CLM WebEdit, with reviewer approval, segment comments, synchronized page-layout PDFs and a documented revision history
- Own machine translation plus controlled gateways to DeepL, Google and Microsoft Translator, including a dedicated system trained on your own texts, translations and terminology
- The vendor states that customer texts are used only for the customer's own translations, with single sign-on support
- Licensing models include on-site installation alongside floating, IaaS and SaaS, so the software can run on infrastructure you control
Held against it
- We found no public information on where translated texts are hosted or processed, on a data processing agreement, or on the locations of the machine translation engines in the chain
- We found no public information on export of translation memory or termbases in open formats such as TMX or TBX, or on what happens to data when a contract ends
- Connectors are named for enterprise content systems — Adobe Experience Manager, Salesforce and CMS transfer under the COTI standard — and we found no public information on a documented REST API, SDKs, a CLI or Git synchronization
- Confidentiality evidence is statement-based: we found no public information on retention of translated texts, encryption at rest, or ISO 27001 or SOC 2 certification
- Every captured buying path ends in a non-binding quote request, with licence models named but no published prices, tiers or free tier
Best for
- You centralize company-wide terminology and need browser-based review with approval and comments — workflow and review scores cluster at 6
- You translate manuals, contracts and documents in Office, layout or PDF formats and want machine translation trained on your own texts with a choice of engines
- You want to run the software on your own infrastructure and prefer an on-site or floating licence over SaaS
- You already run Adobe Experience Manager or Salesforce and want connectors for automated translation workflows
Avoid if
- You translate software strings in JSON, Android XML or xcstrings — the listed formats are Office, layout, PDF, HTML and XML, and we found no public information on SDKs, a CLI or over-the-air delivery
- You run an online storefront and need a connector for it — the published connectors serve Adobe Experience Manager, Salesforce and COTI-standard CMS transfer
- You must verify hosting locations and a data processing agreement for the translation chain before signing — the public privacy statement names subprocessors for the website (Brevo, Google Ireland for video, InnoCraft for Matomo)
- You need a published price or free tier before talking to sales — every public buying path ends in a non-binding quote request
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3 of 5 |
| Translation memory, terminology & review workflow | 3 of 5 |
| Integrations, file formats & developer tools | 2 of 5 |
| Confidentiality of translated content | 2 of 5 |
| Data export, portability & self-hosting | 2 of 5 |
| European sovereignty | 1.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
Machine translation is clearly in the portfolio: support for neural and statistical MT, controlled gateways to DeepL, Google and Microsoft Translator, a web-based rough-translation tool for whole documents, and a dedicated system trained on the company's own texts, translations and terminology. We found no public information on a published language list, glossary or formality controls applied during translation, layout-preserving document translation, quality estimation or published quality evaluations. 2 3 1
The App Developer
STAR publishes its own neural and statistical machine translation plus a dedicated system trained on the company's own texts, translations and terminology, with controlled gateways to DeepL, Google and Microsoft Translator, web-based gisting via STAR Translate and post-editing through established QA functions in Transit. That is a genuine custom-engine story on top of named third-party engines. We found no public information on a published language list, per-segment quality estimation, or a quality evaluation with its method, which is what would lift this further. 2 3
The In-House Document Translator
The pages show neural and statistical machine translation with controlled gateways to DeepL, Google and Microsoft Translator, plus a dedicated system trained on our own texts, translations and terminology — that is the engine choice and the company-language control I need for French, Italian, Polish and Chinese manuals. Office, layout and PDF formats are listed as supported, so documents can come back shaped the way they went in. I found no published engine language list, no quality estimation per segment and no published quality evaluation. 2 3
The Data Protection Officer
The vendor documents its own machine translation with neural and statistical engines, controlled gateways to DeepL, Google and Microsoft Translator, and a dedicated system trained with the customer's own texts, translations and terminology; a web-based tool translates individual texts or whole documents, and common office and layout formats are supported. We found no public information on a published language list per engine, quality estimation, or a translation quality evaluation with its method. 2 3
The E-Commerce Marketer
The pages show an own machine translation offer plus controlled gateways to DeepL, Google and Microsoft Translator, and a dedicated system trained on my company's own texts, translations and terminology — engine choice and custom training are real. Translation memory and machine translation suggestions both flow into the browser editor, and common document formats are supported. We found no public information on a published language list for translation, glossary or formality settings applied during machine translation, or any published quality evaluation, so I cannot judge German-to-Italian output before buying. 2 3 5
The Skeptic
The vendor documents machine translation both as its own offering — with a dedicated system trained on company texts, translations and terminology — and as controlled gateways to named third-party engines (DeepL, Google, Microsoft Translator), plus a web tool for gisting whole documents and post-editing through Transit's QA functions. But the captured pages give no language list, no glossary or tone application during machine translation, and no published quality evaluation, so I cannot place it higher. 1 2 3
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
TermStar gives me a company-wide terminology pool with forbidden-term highlighting, term suggestions on the fly and import/synchronisation across terminology databases, and CLM WebEdit adds translation-memory and machine-translation suggestions, a review-and-approval step, segment comments, synchronized page-layout PDFs for context, segment-level teamwork, a documented segment history and flexible rights configuration. We found no public information on configurable multi-step workflows with automation rules, style guides applied by the AI, ordering human translators or agencies inside the product, or progress and cost reporting per language. 4 5 2
The App Developer
The browser-based review environment shows translation memory and machine translation suggestions, reviewer check-and-approve, segment-level commenting, synchronized page-layout PDFs for context, a documented per-segment history with revision comparison, and flexibly configurable rights; TermStar adds a company-wide terminology pool, dynamic disallowed-term highlighting, term suggestions on the fly, and complex import and synchronization. We found no public information on configurable multi-step workflows with automation rules, QA checks configurable per project, or ordering translators and agencies inside the product, so this is solid process management but not the enterprise-configurable level. 4 5 2
The In-House Document Translator
TermStar gives a company-wide terminology pool with dynamic highlighting of disallowed terms and term suggestions on the fly, and CLM WebEdit adds checking and approval by reviewers, segment commenting, a documented segment history and configurable rights — enough for my contracts and manuals without translation-management bureaucracy. The pages name established QA functions in Transit but describe no checks for placeholders or terminology in detail, and I found nothing on multi-step workflows or ordering translators and agencies. 3 4 5
The Data Protection Officer
TermStar gives a company-wide terminology pool with term suggestions, disallowed-term highlighting and import and synchronisation of terminology databases, and CLM WebEdit adds review and approval, segment commenting, a documented segment history, translation-memory and machine-translation suggestions, synchronized terminology and layout PDFs for context, under flexible rights configuration. Quality assurance in Transit is described only as established QA functions, and we found no public information on multi-step workflow automation, agency ordering inside the product, or progress and cost reporting. 4 5 2
The E-Commerce Marketer
TermStar gives a company-wide terminology pool with disallowed terms flagged dynamically, and CLM WebEdit adds browser-based translating and reviewing with approval, segment comments, a documented revision history, flexible rights and synchronized page-layout PDFs for context — enough for me to hand-correct a bad product name. Transit's established QA functions support post-editing. We found no public information on multi-step workflow automation, in-context editing of a storefront, or progress and cost reporting per language. 2 4 5
The Skeptic
Terminology is clearly managed: a company-wide pool, disallowed-term highlighting, term suggestions on the fly, entry verification, import and synchronization of terminology databases, and morphological support for over 80 languages; the web review tool adds memory and machine-translation suggestions, reviewer approval, segment comments, page-layout PDF context, revision history and configurable rights. I found no public information on configurable multi-step workflows with automation rules, on ordering translators or agencies inside the product, or on progress and cost reporting per language. 2 4 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
Common office, layout, PDF, HTML, XML and localization formats are supported, STAR builds connectors for named systems such as Adobe Experience Manager and Salesforce, a COTI level 3 interface automates transfer to and from content systems, and third-party CAT environments can be integrated via API. We found no public information on a documented REST API with CLI or SDKs, Git repository or CI synchronisation, over-the-air delivery, webhooks or browser and office add-ins. 3 6 2 4
The App Developer
Support for all common formats (Office and layout formats, PDF, HTML, XML, localization) is stated generically — no word on JSON, Android XML or xcstrings, the files I actually ship — and there is an API into third-party CAT environments plus connectors for Adobe Experience Manager, Salesforce and COTI-standard CMS with automated transfer to and from STAR CLM. We found no public information on a documented REST API, a CLI, SDKs, Git repository sync, CI pipelines or over-the-air updates for mobile apps, which is exactly the toolchain my apps need, so a typo fix would still mean a manual file round-trip. 3 6 2
The In-House Document Translator
The pages document connectors to Adobe Experience Manager, Salesforce and CMS systems under the COTI standard, API integration into third-party translation environments, numerous terminology interfaces, and support for common Office, layout, PDF, HTML and XML formats — the document formats I live in are covered. The API itself is not described in detail, and I found no information on repository synchronisation, webhooks, command-line tools or developer kits. 2 4 6
The Data Protection Officer
Common office, layout, PDF, HTML, XML and localisation formats are listed, integration into third-party CAT environments runs via API, and connectors exist for the COTI standard as well as between Adobe Experience Manager, Salesforce and STAR CLM. We found no public information on Git synchronisation, continuous-integration pipelines, SDKs, webhooks, or a documented REST API with its limits. 3 6 2
The E-Commerce Marketer
Common formats including Office, layout, PDF, HTML and XML are supported, an API integrates third-party CAT environments, and named connectors exist for Adobe Experience Manager, Salesforce and CMS transfer via the COTI standard. That reads enterprise-CMS rather than e-commerce: we found no public information on a Shopify or WordPress connector, Git synchronization, a CLI, SDKs or a JavaScript snippet for translating a live storefront, so as a shop with no developer I see no documented path in. 2 3 6
The Skeptic
Support for all common formats (Office and layout formats, PDF, HTML, XML, localization) is claimed, an API into third-party CAT environments is named, and connectors exist for Adobe Experience Manager, Salesforce and COTI-standard transfer to and from content management systems. I found no public information on REST API documentation, a CLI, SDKs, Git repository or CI sync, webhooks, or connector limits and synced fields. 2 3 4 6
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 captured pages state that customer texts are used only for the customer's own translations, the third-party machine translation engines are named as controlled gateways, single sign-on is supported, and TLS/SSL encryption is described for the website. We found no public information on retention or deletion of translated texts, encryption at rest, audit logs, ISO 27001 or SOC 2 certification, or a data processing agreement for the product. 2 3 7 8
The App Developer
The vendor states that customer texts are used only for the customer's own translations, supports single sign-on, and offers an in-house deployment, with a privacy statement grounded in the Swiss revDSG and the EU GDPR plus a directly contactable data protection officer. We found no public information on retention of translated texts, encryption at rest for product content, audit logs, ISO 27001 or SOC 2 certification with scope, or a data processing agreement, so confidentiality rests on statements rather than verifiable controls. 2 3 7 8
The In-House Document Translator
For a draft contract I want it in writing, and the pages state plainly that texts are used only for the customer's own translations, with documents uploaded for a quote used exclusively for preparing that quote; single sign-on is supported too. Retention and deletion of translated texts, encryption at rest, audit logs and a data processing agreement are not described on the pages I read, so the promise stops short of the whole chain. 2 7 8
The Data Protection Officer
The vendor states that customer texts are used only for the customer's own translations, names DeepL, Google and Microsoft Translator as third-party engines behind controlled gateways, and supports single sign-on plus an in-house deployment. Beyond TLS on the website we found no public information on retention or deletion periods for translated texts, encryption at rest, a data processing agreement, audit logs, or ISO 27001 or SOC 2 certification. 2 3 8
The E-Commerce Marketer
The vendor states my texts are used only for my own translations, names the engines a gateway can reach (DeepL, Google, Microsoft Translator), supports single sign-on and publishes a privacy statement under the Swiss data protection act and GDPR with a directly reachable data protection officer. We found no public information on retention of translated texts, encryption at rest, ISO 27001 or SOC 2 certification, or a data processing agreement, so confidentiality rests on a promise rather than audits. 2 7 8
The Skeptic
There is one sentence I actually like — "Your texts will only be used for your own translations" — plus single sign-on, an in-house deployment option and third-party engines named up front (DeepL, Google, Microsoft Translator). But the captured privacy statements govern the website (Matomo, newsletter, Brevo, payment providers), not the translation pipeline: I found no public information on how long translated texts are kept, encryption at rest, a data processing agreement, audit logs, or ISO 27001 / SOC 2 certification. 2 3 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
Terminology databases can be imported, merged and synchronised, common file formats are supported for exchange, and licensing models that include an on-site option mean the assets can sit on our own infrastructure rather than only the vendor's. We found no public information on translation-memory export as TMX or glossary export as TBX or CSV, a documented migration path from named competitors, or the return and deletion of data on termination. 4 3 2
The App Developer
Numerous interfaces for terminology extraction, transfer and use, complex import and synchronization of terminology databases, common-format file support, and licensing models that include on-site installation mean the translation assets can live on the customer's own machines. We found no public information on translation memory export as TMX, glossary export as TBX or CSV, a documented migration path from named competitors, or the return and deletion of data on termination — having hand-merged translation files once, I want those exit paths named before I commit. 2 3 4
The In-House Document Translator
Terminology databases can be imported, consolidated and synchronized, and licensing exists for an on-site installation, which would keep our translation assets on our own machines. The pages show no export of translation memory or terminology in open formats such as TMX or TBX, and no statement of what happens to the data when a contract ends. 2 4
The Data Protection Officer
Terminology databases can be consolidated and merged through documented import and synchronisation functions, and licensing models include an on-site option. We found no public information on export of translation memory or glossaries in open formats such as TMX or TBX, a migration path from named competitors, or the return or deletion of data on termination. 4 3
The E-Commerce Marketer
Licence models include on-site and in-house deployment alongside IaaS and SaaS, so the software can run on infrastructure I control, and terminology databases can be consolidated through complex import and synchronization functions. We found no public information on exporting translation memory or termbases in open formats such as TMX or TBX, a documented migration path from another tool, or what is returned or deleted when a contract ends. 2 4 5
The Skeptic
The terminology pages describe complex import and synchronization functions for terminology databases, and on-site and floating licences exist, which suggests assets can be consolidated rather than typed back in. I found no public information on exporting translation memory or termbases as TMX, TBX, XLIFF or CSV, on exporting all projects and files, or on what is returned or deleted at termination — a six-year memory should be able to leave as more than a spreadsheet, and nothing here says it can. 2 3 4
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
STAR AG is the controller and contracting entity in Ramsen, Switzerland, with a data protection officer at STAR Deutschland in Germany and statements based on the Swiss Data Protection Act and the EU GDPR; website analytics run on a server in Germany and website subprocessors are named (Google Ireland for video, Brevo for the newsletter, InnoCraft in New Zealand for Matomo). We found no public information on where translated texts and the product are hosted, on a published data processing agreement, or on the locations of the machine translation engines the gateways call, so the chain beyond the website is not evidenced. 7 8 1 2
The App Developer
STAR AG in Ramsen, Switzerland is the controller, the declaration follows both the Swiss revDSG and the EU GDPR, a German subsidiary provides the data protection officer, and website subprocessors are listed with locations (Brevo, Google Ireland, InnoCraft in New Zealand). The hosting location of the product and of the machine translation chain is not stated on the captured pages, and we found no public information on a published data processing agreement or certifications; the documented in-house deployment option lets a customer keep texts on their own servers, which partially compensates. 3 7 8
The In-House Document Translator
STAR AG in Ramsen, Switzerland is named as controller, the data protection officer sits at STAR Deutschland in Sindelfingen, the privacy statement is drawn up under both Swiss and EU data protection law, website subprocessors are named with their locations, and an in-house deployment is offered. I found no public information on where the hosted variant processes texts, on a published data processing agreement, or on the locations of the machine translation engines in the chain. 2 7 8
The Data Protection Officer
The contracting entity is STAR AG in Ramsen, Switzerland, the data protection officer sits at STAR Deutschland GmbH in Sindelfingen, and the privacy statement is written for both the Swiss and EU regimes, with website subprocessors (Brevo, Google Ireland, InnoCraft in New Zealand) listed by location. Where translated texts are hosted and under what data processing agreement is not stated, and the third-party machine translation gateways can route text to Google and Microsoft, so parts of that chain sit outside the EU without a stated safeguard. 7 8 2
The E-Commerce Marketer
The contracting entity is STAR AG in Ramsen, Switzerland — European but outside the EU — with a data protection officer at STAR Deutschland in Sindelfingen and a privacy statement written for both the Swiss act and the GDPR; website subprocessors such as Brevo, Google Ireland and the Matomo provider InnoCraft are named, with analytics data stored on a server in Germany. We found no public information on where translated texts are hosted or processed, on a published data processing agreement, or on the locations of the machine translation engines in the chain. 1 7 8
The Skeptic
The controller is STAR AG in Ramsen, Switzerland, with a data protection officer at STAR Deutschland in Sindelfingen, and the machine translation gateways name their engines (DeepL, Google, Microsoft). But where translated texts are hosted or processed is not stated, I found no public information on a data processing agreement, and the only listed subprocessors serve the website — Brevo for newsletters, Matomo's InnoCraft in New Zealand, Google Ireland for video — while the subprocessors of the translation chain itself are not listed. 2 3 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
Licensing models are named — on-site, floating, time-limited, IaaS and SaaS — but every captured path to a price runs through a non-binding quote request or a direct contact for a quote. We found no public price figures for any tier or edition and no free tier with stated limits, so an annual cost cannot be computed from these pages. 1 3 4 6
The App Developer
The captured pages name flexible license models (on-site, floating, time-limited, IaaS, SaaS) but every buying path ends in a person: a non-binding translation quote request on the main page and 'contact us... if you require additional information or a quote' on the connectors page. We found no public prices, tiers, volume rules or free tier, so a buyer cannot compute an annual cost from these pages alone — for a start-up budget that alone rules it out of a shortlist. 1 3 6
The In-House Document Translator
The pages name flexible licence models — on-site, floating, time-limited, IaaS and SaaS — and offer a non-binding quote request, but no price figure appears on any page I read. I cannot estimate an annual cost from public information alone; it starts with a conversation and a quote. 1 3 4
The Data Protection Officer
No prices are published; the captured pages name licensing models (on-site, floating, IaaS, SaaS) and direct buyers to a non-binding quote request, so an annual cost cannot be computed from public pages. We found no public information on per-seat or volume pricing, a free tier, or what machine translation volume costs. 1 3
The E-Commerce Marketer
The public pages offer only a non-binding quote request and a contact-for-quote email; licence models (on-site, floating, IaaS, SaaS) are named, but no tier prices, volume metrics, user limits, free tier or overage terms appear anywhere. From public information alone I cannot even estimate a monthly cost, let alone one that stays flat as my catalogue grows. 1 3 6
The Skeptic
Every captured page routes the buyer to a "non-binding translation quote" request or an email to the vendor; I found no public prices, no tiers and no scaling rule for volume or seats. The licence models — on-site, floating, time-limited, IaaS and SaaS — are named, which is the only pricing structure a buyer can see before the sales call. 1 3 4 6
European sovereignty — proven facts
1 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 CH
unverified
Why unverified?STAR AG itself is named as controller and appears to be the group parent ("STAR Group headquarters"); no commercial register entry is cited. |
2/2 pts | 7 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited 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 Transit
Is Transit European?
Not determined: the vendor’s pages as captured do not say where Transit is based. Its vendor, STAR AG, is incorporated in Switzerland, per the vendor’s page captured 17 Nov 2026.
Where does Transit store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Transit have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Transit?
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: Transit alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 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. STAR AG itself is named as controller and appears to be the group parent ("STAR Group headquarters"); no commercial register entry is cited.
- 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.
- 3 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
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.star-group.net Checked 17 Nov 2026 Details →
- 2 Machine translation & AI quality — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →
- 3 Machine translation & AI quality — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →
- 4 Translation memory, terminology & review workflow — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →
- 5 Translation memory, terminology & review workflow — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →
- 6 Integrations, file formats & developer tools — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →
- 7 Confidentiality of translated content — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →
- 8 Confidentiality of translated content — found from sitemap www.star-group.net Checked 17 Nov 2026 Details →