“Self-hosted” and “SaaS” sound like simple opposites. In multilingual WordPress work, they rarely describe the whole system.
A WordPress-managed plugin may store translations in the client database while sending selected content to an external AI provider. A SaaS platform may host translation memory and workflow data while publishing completed translations back to WordPress. Both can use external services; both can require ongoing maintenance.
Agencies therefore need to compare architecture and responsibility, not labels. This guide explains how to evaluate self-hosted WordPress translation against a SaaS-led workflow.
Define the terms for the specific project
Before comparing products, draw the actual data path.
Ask four questions:
- Where is the source content stored?
- Where are translated versions stored?
- Which service processes content during translation?
- Which system controls URLs, rendering, metadata and publication?
A WordPress-managed solution normally keeps the publication workflow and translated records inside the site. It may still call DeepL, OpenAI, Claude, Gemini or another API. A SaaS solution normally places more workflow, memory or delivery logic in a vendor platform, although the exact boundary varies.
Avoid saying “all data stays on the server” unless the configuration genuinely performs translation without sending content to an external processor.
Compare the complete architecture
Use a matrix based on the client’s needs.
| Area | WordPress-managed approach | SaaS-led approach |
|---|---|---|
| Content control | Translations and publishing are usually managed in WordPress | Workflow may depend on a vendor dashboard or synchronisation layer |
| Processing | May use external APIs chosen by the agency | Usually uses the platform’s processing and provider model |
| Cost | Plugin licence plus provider/API and maintenance costs | Subscription, usage, word or traffic-based pricing may apply |
| Updates | Agency maintains the WordPress integration | Vendor maintains more of the hosted platform |
| Portability | Database-level records may be easier to inspect, depending on implementation | Export quality and platform exit process are critical |
| Collaboration | WordPress roles and workflows can remain central | Dedicated translation-management features may be stronger |
| SEO | Routing, canonicals and metadata depend on the WordPress implementation | Proxy or synchronised delivery may add another technical layer |
| Resilience | Site depends on WordPress and any configured provider | Site may depend on vendor availability and integration state |
Compare total cost, not the headline price
Calculate the expected annual cost at realistic volumes.
Include:
- plugin or platform licence;
- machine-translation or language-model usage;
- minimum subscription commitments;
- per-word, per-character or traffic charges;
- human review and project management;
- glossary and translation-memory administration;
- implementation, QA and staff training;
- support and migration work;
- staging and additional site allowances.
A self-managed workflow may reduce platform fees but require more agency ownership. A SaaS platform may reduce maintenance while charging for scale or advanced collaboration. Neither model is automatically cheaper.
Run low, expected and high-volume scenarios. Multilingual costs can change quickly when a client adds products, languages or frequent content updates.
Examine privacy and processor relationships
Translation content may include names, support messages, unpublished commercial material or other personal and confidential data.
WordPress’s plugin privacy guidance recommends privacy by design, data minimisation, transparent documentation and careful review of external APIs. Apply those principles to the complete translation chain.
Ask:
- what content is transmitted;
- which provider receives it;
- where processing and storage occur;
- how credentials are protected;
- whether prompts or content are retained;
- what logs contain;
- who can access translated data;
- how data can be exported or erased;
- whether the client’s legal documentation and contracts cover the setup.
This is not a legal conclusion. The client should obtain appropriate legal advice for its markets and data. The agency’s responsibility is to describe the architecture accurately and implement the approved controls.
Evaluate multilingual SEO as a system
Google recommends separate URLs for different language versions and hreflang annotations to connect them. It also uses visible page content to determine language.
Whichever architecture you choose, verify:
- each real translation has a stable, crawlable URL;
- language versions reference themselves and corresponding alternates correctly;
- canonical URLs do not collapse genuine translations into the source page;
- untranslated fallbacks are not presented as complete translated pages;
- titles, descriptions and social metadata can be translated;
- sitemaps advertise the intended language URLs;
- users can choose a language without forced, opaque redirects;
- translated slugs and internal links remain maintainable.
Do not choose a translation platform solely because it produces text quickly. Publication and discovery controls determine whether the translated experience works as a website.
Compare editorial workflow and quality control
Map the real sequence from source update to approved translation:
- Detect new or changed source content.
- Decide which languages require an update.
- Apply glossary and brand rules.
- Generate or assign the translation.
- Review high-risk content.
- check layout, links, forms and dynamic elements.
- approve metadata and URL changes.
- publish and verify the public page.
- retain status and reviewer evidence.
SaaS tools may offer mature assignment and review features. WordPress-managed tools may keep editors closer to the rendered page. The better fit depends on team size, client involvement and content risk.
Test portability before committing
Ask for a practical exit demonstration, not only an assurance that data is exportable.
Confirm:
- what file or database format is available;
- whether translations remain visible if a licence expires;
- whether translated URLs keep working;
- how media, metadata and structured fields are represented;
- whether translation memory and glossaries can be exported;
- how much reconstruction another system would require.
Portability is part of client ownership. A low-cost workflow can become expensive if leaving it requires rebuilding the multilingual site.
Understand the WpAgencyKit model accurately
WpAgencyKit Translate manages WordPress content translation, language routing, strings and multilingual SEO integration inside WordPress. It supports several external translation providers, so configured content may be sent to the chosen provider for processing.
That makes it a WordPress-managed translation engine, not a promise that every translation operation happens entirely on the hosting server. Agencies should document the provider, credentials, data path and review process for each client.
Choose by operating requirements
A WordPress-managed approach may suit agencies that want:
- publication and translated records controlled inside WordPress;
- direct access to site-level configuration;
- provider choice and API-level cost control;
- a consistent workflow across maintained client sites;
- fewer external editorial dashboards.
A SaaS-led approach may suit projects that need:
- large translator teams and specialised assignment features;
- vendor-managed infrastructure and synchronisation;
- enterprise translation-management integrations;
- central workflow outside individual WordPress installations.
Hybrid approaches are valid. The important requirement is that the boundary is understood and supportable.
Make the decision auditable
Record the chosen architecture, reasons, data path, provider, cost assumptions, SEO model, review ownership and exit plan. Revisit the decision when languages, content volume, regulation or client teams change.
The best translation system is not the one with the most impressive automation demonstration. It is the one the agency can operate transparently, verify on the real site and hand back to the client without surprises.