Running a multilingual site in Drupal can feel overwhelming. You need translations to be accurate, affordable, and easy for your team to manage. The challenge is figuring out which workflow gets you there without adding more complexity than you need.

At Specbee, we’ve been evaluating Drupal’s built-in AI translation modules against other translation management solutions. Drupal now makes it possible to keep translations inside your CMS, but there are trade-offs. This post explains how Drupal AI modules actually work, how they compare with Lingotek and other connectors, and which path makes the most sense depending on your needs.

Drupal AI Modules: The practical starting point

Drupal AI translations are not a single module, but a stack. To get a working workflow, you usually combine:

• Drupal AI Module (for connecting to DeepL, Google Translate, or OpenAI)
• Drupal Workflows/Content Moderation Module (to route content through a review and approval process)
• Email/Notifications Add-on (to alert reviewers when new translations are created)

Here’s what the process looks like once this is set up:

1. A content author creates or updates a page in Drupal.
2. The AI module triggers an automatic translation using your chosen provider.
3. Drupal’s workflow module moves that translated content into a “Needs Review” state.
4. Reviewers receive an email notification and log into Drupal.
5. The reviewer edits or approves the translation inside Drupal’s editorial UI.
6. Once approved, the translation is published automatically.

Why it works: It keeps everything inside Drupal, costs scale with usage, and you can pick providers per language.
What to watch: AI translations are strong for most use cases, but you should flag high-stakes content for human review.
Cost example: Translating 10 million characters costs around $190 to $250, depending on the provider.

This setup is best if you want fast, affordable translations without sending editors into an external TMS (Translation Management System).

Lingotek: Enterprise power at a higher price

Lingotek has a Drupal connector but runs most of its processes outside the CMS. Content is exported to Lingotek’s translation management system, where either machine translation or human linguists handle the work. Completed translations sync back to Drupal.

Why it works: Enterprise-grade workflows, centralized translation memory, glossaries, and professional linguists are available.
What to watch: The workflow lives outside Drupal, licensing costs are higher, and editors will need to learn a second system.
Cost example: About $30,000 annually for licensing plus per-word service fees.

Lingotek is a better fit if your translation needs go far beyond Drupal and span multiple platforms.

Phrase (Memsource) Drupal connector

Phrase (formerly Memsource) also integrates with Drupal through a connector. Like Lingotek, most of the workflow happens outside Drupal. Content is managed in the Phrase TMS and synced back after translation.

Why it works: Combines AI and human workflows with built-in QA tools.
What to watch: Another external system, higher licensing costs, and less flexibility inside Drupal.

Phrase is useful if you need a hybrid of AI and linguists, but can handle a more complex setup.

Custom API connectors

For organizations already invested in a translation system like TransPerfect GlobalLink or XTM, Drupal can integrate through APIs.

Why it works: Full TMS functionality, central memory, and governance across platforms.
What to watch: Requires custom dev work, increases vendor lock-in, and costs are significantly higher.

Best suited for enterprises with strict compliance requirements or multi-system translation strategies.

Comparison at a glance

My recommendation

If you are running a Drupal site and want a cost-effective, straightforward way to handle translations, start with Drupal AI modules. They let you translate at scale while keeping your editorial workflow intact. Developers will appreciate that it is built with Drupal’s native workflow system, not a black box.

If your needs grow to include strict enterprise governance, cross-platform translation, or regulated content, then Lingotek, Phrase, or a custom API connector can be explored. Just know they require more investment and introduce more moving parts.

Final thoughts

Multilingual content does not have to be complicated. Drupal AI modules paired with workflows and notifications keep everything in one place, which makes your editors happy and keeps costs under control. Larger TMS solutions are still valuable when you need them, but for most Drupal sites, the Drupal-first approach is the best place to begin.

At Specbee, we help organizations set up the right Drupal translation workflows to match their goals. Not sure where to start? We’ll help you figure out what makes sense for your team. Let’s talk.