Webiny is a self-hosted, open-source serverless CMS that deploys inside your AWS account for teams that want content infrastructure without backend servers. Headless GraphQL and REST APIs sit beside a visual website builder, file manager and publishing workflows, all running on Lambda, DynamoDB, S3 and CloudFront. With 8,048 GitHub stars and a YC W21 backer, it is an established option for AWS-centric organizations.[1][2]
Quick verdict
AWS-centric teams that want CMS infrastructure inside their own cloud account will get the most from Webiny. Its serverless stack combines headless GraphQL/REST APIs with a visual website builder under MIT-licensed Community code, scaling to zero on AWS usage billing. The price is mandatory AWS and Pulumi capacity plus paid tiers for SSO and audit controls, so non-technical teams should choose a hosted SaaS CMS instead. If you run on AWS and need governed multi-brand publishing you own, start with Community and evaluate Business separately.[1][2][3]
Key features
Deploys inside your AWS account: the whole stack runs in your cloud with data staying within your infrastructure boundary, unlike SaaS CMS hosting.[1][2]
Headless content delivery over GraphQL and REST: the Apollo B2B CMS API ships in every tier with content modelling, localization and plugins.[1][2]
Visual website builder plus AI builder: no-code page building on all tiers with an AI-assisted builder and A/B testing on paid plans.[1][2]
Enterprise governance on paid tiers: multi-tenancy, advanced RBAC, SSO and audit logs structure publishing across brands and teams.[1][2]
Serverless scale-to-zero cost model: Lambda, DynamoDB, S3 and CloudFront bill by AWS usage, and the comparison guide documents near-zero hosting on the AWS free tier.[1][2]
Infrastructure as code with Pulumi: deployment, environments and CI/CD pipelines are defined in code rather than clicked together.[1]
Editorial collaboration built in: advanced publishing workflows, release management, file manager and theme SDK organize team delivery.[1]
Open-core licensing: MIT Community core with commercial Business and custom Enterprise editions for advanced features and support.[1][2]
Who will love it
AWS-centric engineering teams: the deploy-into-your-account model plus Pulumi IaC fits organizations already standardized on AWS serverless.[1][2]
Enterprises running multiple brands: multi-tenancy, advanced RBAC and audit logs serve governed publishing across tenants from one platform.[1][2]
Cost-sensitive scale-ups: usage-based AWS billing without per-seat CMS fees suits spiky traffic where SaaS seat pricing would sting.[1][2]
Who should avoid it
Teams with no AWS skills: Pulumi deployment, AWS account ownership and serverless operations all need cloud engineering capacity a SaaS CMS would spare you.[1][2]
Buyers needing SSO or audit trails on day one: those controls sit behind the $79-per-month Business tier, not the free Community edition.[1]
Shops avoiding a single-cloud lock-in: Webiny is architected for AWS serverless primitives, so portability off AWS is not its design goal.[1][2]
Switching and coexistence
Strapi teams wanting cloud-portable Node.js: Strapi runs on Node hosting with PostgreSQL or SQLite and offers its own cloud, while Webiny trades that portability for AWS-native serverless economics.[1][2]
License boundary to confirm before migrating: Community code is MIT, but Business is commercial and Enterprise terms are custom, so audits should scope which edition is deployed.[1]
Coexistence path: keep an existing CMS for current sites and pilot Webiny for one new brand or tenant, since multi-tenancy isolates the experiment inside your AWS account.[1][2]
Questions worth asking
How much does Webiny cost per month?
The self-hosted Community tier is free forever under the MIT license for 1 project, 1 organization member and 3 tenants; you still pay AWS for the infrastructure it runs on. Business starts at $79 per month billed yearly with 3 projects, unlimited members, SSO, audit logs and support. Enterprise is sales-led with a dedicated manager, SLA and onboarding. Prices checked October 13, 2026.[1]
Can you self-host Webiny?
Does Webiny support single sign-on?
Should I choose Webiny or Strapi?
Choose Webiny when you want the CMS to live inside your own AWS account with usage-based serverless cost and multi-tenancy for several brands. Strapi fits teams wanting a Node.js CMS they can also run outside AWS with a visual content-type builder and dual REST/GraphQL output. Both demand developer capacity and self-hosted operations, so a hosted SaaS CMS serves non-technical teams better.[1][2]
Sources and editorial review
Source research. Reviewed on October 13, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Webiny official homepage
official · Observed October 13, 2026
Official homepage: open-source serverless CMS positioning, deploys inside your AWS account, scale-to-zero pricing, dev-ready CMS, 7,635 stars, 3,554 projects, 8,712 members, 147 countries, YC W21, SOC 2 Type II, SSO/RBAC/audit logs.
- Webiny pricing and plans
official · Observed October 13, 2026
Official pricing: free MIT Community tier, Business from $79/month with SSO/audit logs/VPC/support, custom Enterprise with manager/SLA/Enterprise Cloud, self-hosted all tiers, GraphQL API and builder features per tier.
- Webiny vs Strapi comparison guide
official · Observed October 13, 2026
Official comparison: Webiny versus Strapi on headless CMS delivery, AWS self-hosting with data boundary, multi-tenancy, enterprise security and usage-based versus per-seat cost, with AWS self-hosting guide.
- webiny/webiny-js on GitHub
official · Observed October 13, 2026
Repository page and README: 8,048 stars, TypeScript/React/Node.js/GraphQL, MIT Community plus commercial Business and custom Enterprise licensing, serverless AWS runtime, Pulumi deploy, headless CMS features and multi-tenancy.
Compared with these products
No explicit proprietary baseline is recorded.