Question 1

What is Multi-Tenancy?

Accepted Answer

Multi-tenancy allows you to operate several different projects under the same Webiny instance.

A project is what we refer to as a tenant in Webiny.

Every tenant is fully isolated meaning each tenant has its own:
Content
Assets
Users and permissions
Publishing workflows
Settings and configuration

A tenant would typically represent a:
- website
- regional brand page
- marketing landing page
- mobile app backend
- SaaS project instance

Question 2

How is this different from multi-site or multi-project setups?

Accepted Answer

Most CMS platforms bolt multi-tenancy on top of single-site assumptions.

Webiny is different:
Multi-tenancy is a first-class concept, not a workaround
Tenants are not folders, tags, or environments
You don’t need to duplicate infrastructure or deploy separate instances

This makes Webiny ideal for SaaS platforms, agencies, enterprises with many brands, or global organizations with regional sites.

Question 3

How is the data between tenants separated?

Accepted Answer

Every tenant is fully isolated by default. Every tenant is like a brand new Webiny instance with its own assets, theme, users, pages, roles, api keys, ...

By default nothing is shared between tenants, but if your business requires that specific data or assets flow freely between tenants, that can easily be achieved via the Webiny Framework and lifecycle events.

Architecturally all tenants share the same infrastructure - but since Webiny runs on top of AWS serverless services one tenant won't have much impact on another tenants performance, which is typically on of the challenges in a more traditional systems.

Question 4

Can tenants share or inherit content?

Accepted Answer

They can — but only when you explicitly allow it.

Using code and lifecycle events, you can:
Propagate global content from a “root” tenant to child tenants
Selectively push updates to specific tenants
Allow local teams to override or extend shared content
Keep global consistency without blocking local flexibility

This is especially useful for global brands, franchises, and regional marketing teams.

Question 5

Can tenants be created and managed programmatically?

Accepted Answer

Yes, you can use Webiny's GraphQL API to create and manage your tenants - this is a convenient approach to create tenants as part of your existing SaaS application.

You can:
Create tenants via API or during user onboarding
Attach custom attributes like region, plan, brand, or customer type
Trigger logic using lifecycle events (before/after create, update, delete)
Enforce business rules or automate downstream systems

Tenant management becomes part of your application logic, not a manual admin task.

Question 6

What's the tenant hierarchy?

Accepted Answer

This is the concept of parent child tenant setups - one tenant can be "placed" under another tenant. Having this child/parent hierarchy opens a lot of possibilities in terms of organizing your tenants and controlling things like content inheritance, permissions and similar.

By default Webiny has a "root" tenant - which is the one you get when you first install the system.  All other tenants are placed under the root tenant.

This structure can programmatically be extended into more complex configurations to suit your business requirements. Typically we see organizations having Brands, Region and similar concepts between the root tenant and the child tenants, but many more structures are possible.

Question 7

How does multi-tenancy scale?

Accepted Answer

Webiny’s multi-tenancy runs on a serverless architecture, designed to scale horizontally without operational overhead.

In practice, this means:
Thousands of tenants in a single deployment
No per-tenant infrastructure to manage
Predictable performance even under heavy editorial load
Shared infrastructure costs without shared data risk

Question 8

Who is multi-tenancy designed for?

Accepted Answer

Multi-tenancy in Webiny is built for:
SaaS companies embedding content capabilities into their products
Enterprises managing many brands, regions, or business units
Agencies running multiple client projects on one platform
Platform teams that want governance without fragmentation

If you need isolation and efficiency, this is what it’s designed for.

Loading...

Multi-Tenancy

Complexity without chaos. Multi-tenancy isn’t about cramming everything into one system. It’s about designing for growth from day one.

Frequently Asked Questions

Want to see how Webiny can help you manage a multi-tenant site?