Question 1

Why embedding matters?

Accepted Answer

Embedding Webiny means integrating its admin UI and content capabilities directly into your application.

Your users:
Stay inside your product
Use your navigation and flows
See your branding, not Webiny’s
Manage content as part of their normal workflow

Webiny becomes infrastructure — not a separate destination.

Question 2

How white-label is the experience?

Accepted Answer

Fully white-label.

You control:
Branding, colors, and visual identity
Navigation structure and entry points
Which features are visible to which users

There’s no “powered by” watermark and no forced UI conventions.

Question 3

How does this work in multi-tenant SaaS products?

Accepted Answer

This is where Webiny really shines.

You can:
Map each customer to a Webiny tenant
Provision tenants automatically during onboarding
Isolate data, users, and assets per customer
Apply shared rules or global content where needed

All from a single Webiny instance — without manual setup.

Question 4

Can we control what customers are allowed to do?

Accepted Answer

Absolutely.

You decide:
Which content types customers can manage
Which components or fields are editable
What workflows apply to which users
What actions are allowed via permissions and code

This prevents accidental misuse while still giving customers flexibility.

Question 5

How is this different from building our own CMS?

Accepted Answer

Building your own CMS means:
Designing editorial UX
Solving permissions and workflows
Handling versioning, audit logs, and scaling
Maintaining it long-term

Webiny gives you:
A production-ready CMS foundation
Full extensibility via code
Control over UX and behavior
The ability to ship fast without locking yourself in

You build what’s unique to your project — Webiny handles the rest.

Question 6

Can Webiny reuse our authentication and user model?

Accepted Answer

Yes — Webiny is designed to integrate into existing auth and tenancy models.

You can:
Reuse your authentication provider
Map application users to Webiny roles
Align tenants with your product’s customers
Provide seamless SSO across systems

Users don’t need a second account — or even know a CMS is involved.

Question 7

Who is this designed for?

Accepted Answer

Embedded & white-label CMS is ideal for:
SaaS platforms adding content capabilities
Marketplaces and portals
Enterprise platforms with internal tools
Agencies building reusable client platforms
Products that need content without becoming CMS vendors

If content belongs inside your product, this is the right approach.

Loading...

An embedded CMS that feels like your product

Your CMS. Your rules.With Webiny YOU own the experience — and the evolution of it.

Frequently Asked Questions

Want to embed content management into your product?