Multi-tenant Localization

Give each of your customers their own translation layer without duplicating content: every tenant inherits your base and keeps only its own changes.

The problem

You have a multilingual SaaS product, and each of your customers wants their own language customizations: branded terminology, region-specific phrasing, or entirely different translations for certain strings.

Without it, teams duplicate projects, write their own override logic, or add namespaces or custom locale codes per customer. That works for a few customers; every additional one adds another copy to keep in sync or another combination to manage.

Common workarounds and where they get hard

✗

A full project copy per customer: every base change has to be copied again

✗

Extra namespaces like "customer1_common": the lookup order lives in every app's config

✗

Custom locale codes like "en-x-customer1": fine for a few customers, then customers times languages

✗

Merge scripts between projects: code you write and maintain

How Locize solves it

A parent project holds your base translations. Each tenant project inherits everything and overrides only what they need.

Parent project

Your main project contains the base translations for all languages. This is the single source of truth.

Tenant projects

Each customer gets a child project that inherits all translations from the parent. Only overridden strings are stored separately.

CDN delivery

Each tenant has its own project ID and CDN files. The published files already combine the base with the tenant's overrides, so your app loads one tenant and merges nothing.

Try it free

Key capabilities

Everything you need to manage per-customer translations at scale.

Parent/child inheritance

Tenant projects inherit all translations from the parent. New keys added to the parent appear in every tenant automatically.

Key-level overrides

Tenants override individual strings while the rest falls through to the parent. Only overridden values count as words, so inherited text is not charged twice.

Language sync options

Choose per tenant: sync languages with the parent project automatically, or let each tenant manage their own language set independently.

Isolated access control

Tenant users see only their own project. Customers cannot access each other's data or the parent project.

Billed with your base project

Tenants have no plan of their own: Growth includes 5, Professional 10, Professional Plus 20, Enterprise 50, and more come in packs. A per-tenant cost estimate helps you pass costs on to customers.

Organization access

Members of your organization reach every tenant without being added one by one, and a customer's people get access to their own tenant only. Organization-wide rules such as enforced MFA apply to every project.

Who it's for

SaaS companies

Let each enterprise customer customize product language without forking your translation setup.

White-label product builders

Deliver a fully branded language experience per client with minimal operational overhead.

Agencies managing multiple clients

Maintain a shared base translation set and let each client project inherit and override as needed.

Franchise and multi-brand businesses

Each brand or region gets their own translation layer on top of a shared corporate base.

Ready to set up multi-tenant localization?

Read the full multi-tenant documentation or start a free trial to see it in action.

Start free trial Multi-tenant docs