● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
KubeEra
W

Webiny

Serverless
Open source · NOASSERTION

Webiny is an open-source serverless CMS and application framework built on AWS, written in TypeScript.

updated 2026-07-01

What it is

Webiny is an open-source serverless CMS and application framework built on AWS, written in TypeScript. It bundles a headless CMS, page builder, form builder, and file manager, deployed via Infrastructure-as-Code (Pulumi under the hood) directly into your own AWS account. The pitch is: you own the infrastructure, you own the data, and you don't pay a SaaS vendor per API call — you pay AWS directly for Lambda, DynamoDB, S3, etc.

Beyond that, a formal one-line vendor description isn't publicly available, so treat the above as the practitioner summary based on what the project actually ships.

Who builds it and why

Not publicly available in terms of founding story, funding, or company backing details. What's visible: an active GitHub org with 85 contributors and a steady commit cadence through mid-2026, suggesting either a funded core team or a company sponsoring full-time maintainers rather than a purely volunteer side project. Typical of this category — vendor builds an open-core product to seed adoption, then monetizes hosting, support, or enterprise features on top. Confirm this directly with the project before assuming a business model.

Production readiness signal

  • 7,996 GitHub stars — solid community traction, not a niche experiment.
  • 85 contributors — healthy enough to survive a bus-factor problem, though concentration among top contributors is unknown.
  • Latest release v6.4.3 — mature version numbering implies years of iteration and breaking-change cycles already absorbed.
  • Last commit recent — actively maintained, not abandoned.
  • License: NOASSERTION — this is a real flag. GitHub couldn't detect a standard SPDX license identifier, which means either the repo lacks a clear LICENSE file, uses a non-standard license, or has license fragmentation across packages. Do not adopt this in a commercial product without manually verifying the actual license terms in the repo. This is the single most important thing to check before you build on Webiny.
  • CNCF maturity: not applicable — Webiny is not a CNCF project, so no CNCF sandbox/incubation/graduation signal exists here.

Who should use this

  • Teams already committed to AWS who want a CMS that lives inside their own account/VPC rather than a third-party SaaS.
  • Engineering orgs that want serverless economics (pay-per-invocation) instead of always-on CMS infrastructure.
  • Teams comfortable owning Pulumi/IaC deployments and debugging Lambda cold starts, DynamoDB single-table design quirks, and AWS service limits.
  • Organizations with compliance requirements that mandate data residency inside their own cloud account.

Who should NOT use this

  • Anyone who hasn't resolved the license question. NOASSERTION isn't a green light — verify before you ship.
  • Teams wanting a multi-cloud or on-prem CMS — this is AWS-native by design; porting off AWS later is a real rewrite, not a config change.
  • Small teams without DevOps capacity — serverless doesn't mean zero-ops. You're still responsible for IAM policies, cold-start latency, DynamoDB capacity planning, and Pulumi state management.
  • Content-heavy sites needing simple, predictable hosting costs — serverless billing can spike unpredictably under traffic bursts compared to flat-rate hosting.
  • Teams wanting a battle-tested, decade-old CMS ecosystem (plugins, themes, community Stack Overflow answers) — Webiny's ecosystem is smaller than WordPress/Drupal/Strapi's.

Alternatives

  • Strapi — self-hosted or cloud headless CMS, larger community, traditional (non-serverless) deployment model, clearer licensing (MIT core).
  • AWS Amplify — Amazon's own full-stack serverless framework; less CMS-specific but tighter first-party AWS integration and support.
  • Payload CMS — TypeScript-first headless CMS, self-hostable on any infrastructure (not AWS-locked), active development, MIT licensed.

Pricing

Webiny itself is open source and free to use — you deploy it into your own AWS account and pay AWS directly for compute, storage, and data transfer. There's reportedly a commercial/enterprise offering layered on top (support, hosting assistance), but specific pricing and tier details are not publicly available. Budget for AWS costs separately; they scale with usage, not with a Webiny license fee.

Frequently asked

What is Webiny?+
Webiny is an open-source serverless CMS and application framework built on AWS, written in TypeScript. It bundles a headless CMS, page builder, form builder, and file manager, deployed via Infrastructure-as-Code (Pulumi under the hood) directly into your own AWS account.
Who builds Webiny?+
Not publicly available in terms of founding story, funding, or company backing details. What's visible: an active GitHub org with 85 contributors and a steady commit cadence through mid-2026, suggesting either a funded core team or a company sponsoring full-time maintainers rather than a purely volunteer side project.
Is Webiny production ready?+
7,996 GitHub stars — solid community traction, not a niche experiment. 85 contributors — healthy enough to survive a bus-factor problem, though concentration among top contributors is unknown. Latest release v6.4.3 — mature version numbering implies years of iteration and breaking-change cycles already absorbed.
Who should use Webiny?+
Teams already committed to AWS who want a CMS that lives inside their own account/VPC rather than a third-party SaaS. Engineering orgs that want serverless economics (pay-per-invocation) instead of always-on CMS infrastructure.
Who should not use Webiny?+
Anyone who hasn't resolved the license question. NOASSERTION isn't a green light — verify before you ship. Teams wanting a multi-cloud or on-prem CMS — this is AWS-native by design; porting off AWS later is a real rewrite, not a config change. Small teams without DevOps capacity — serverless doesn't mean zero-ops.
What are the alternatives to Webiny?+
Strapi — self-hosted or cloud headless CMS, larger community, traditional (non-serverless) deployment model, clearer licensing (MIT core). AWS Amplify — Amazon's own full-stack serverless framework; less CMS-specific but tighter first-party AWS integration and support.
How much does Webiny cost?+
Webiny itself is open source and free to use — you deploy it into your own AWS account and pay AWS directly for compute, storage, and data transfer. There's reportedly a commercial/enterprise offering layered on top (support, hosting assistance), but specific pricing and tier details are not publicly available.