Question 1

What does “scales by default” actually mean?

Accepted Answer

Webiny is built on a serverless architecture, so capacity isn’t something you size upfront.

Instead of fixed overprovisioned and overpriced servers, you get:
Automatic horizontal scaling
Elastic compute and storage
Pay-for-what-you-use economics

Whether you’re serving hundreds of requests or millions, the system adapts without manual intervention.

Question 2

What happens as content and users grow?

Accepted Answer

Growth doesn’t change how the system behaves.

Webiny is already used in environments with:
Hundreds of millions of content records
Petabytes of assets
Thousands of editors working concurrently
Thousands of isolated tenants in one platform

There’s no “enterprise tier” unlock — the architecture is already there.

Question 3

How does scaling impact cost?

Accepted Answer

Because Webiny is serverless and self-hosted:
You don’t pay for idle capacity
Costs scale with real usage
You can optimize at the infrastructure level

You avoid the “fixed pricing + overage penalties” common in SaaS CMS platforms.

Question 4

Why doesn't everyone use serverless architecture?

Accepted Answer

Adopting a serverless architecture is a complex undertaking as many of the more "traditional" approaches of how you architect your solution and how you write your code don't apply.

Existing solutions can't migrate from a "server" based architecture to the serverless architecture as they would need to rewrite most of their code-base for their solution to just run, and even more to run effectively.

When we started building Webiny the only thing you could do on the severless architecture was just resizing images, and we were one of the first solutions to go all in on this approach and since then we've come a long way. Our platform has matured and we've proven that this approach scales really. Today large enterprises feel confident about using Webiny and the serverless architecture to power their critical workloads.

Loading...

Built to scale — without re-architecting later

Scale without risk. Traffic spikes shouldn’t become outages. Growth shouldn’t become a bottleneck.

Frequently Asked Questions

Want to scale without surprises?