Our take
Activeregular commits and releases- Activity
- 79
- Community
- 69
- Issues
- 21
- Pull requests
- 45
+8 stars in the last 30 days
- Merges more pull requests than 80% of the projects we track
- Slower to merge pull requests than 91% of the projects we track
Webiny is an actively maintained, broad AWS CMS framework with a substantial contribution base, but its AWS-only architecture and developer-focused setup make it a specialized choice.
Good fit if
- Your team is committed to AWS and wants to own the CMS infrastructure and data.
- You need multi-tenancy, custom TypeScript extensions, or a white-label content platform.
- You can meet the Node.js 24+ requirement and have TypeScript and React development capacity; the project reports regular commits and releases, with contributions from 76 contributors.
Look elsewhere if
- You need to run on GCP, Azure, or on-premises, which Webiny does not support.
- You want a simple blog, a plug-and-play SaaS CMS, or a no-code setup.
- Your team does not want to adopt TypeScript and React for extensions and customization.
All health signals
| Last commit | 2026-10-27 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 19 (latest v6.5.0, 2026-10-20) |
| Contributors | 76 (top contributor: 54% of commits) |
| Issues closed, last 90 days | 0+ |
| Pull requests merged, last 90 days | 67 (typically merged in 6 days) |
| Project age | 8 years |
Checked on 2026-10-28 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
8,054Forks
683Change since Nov 13, 2026: +2 stars·0 forks
Overview
Webiny is an AI-programmable, self-hosted CMS framework built with TypeScript on AWS serverless services, including Lambda, DynamoDB, S3, and CloudFront. It gives developer teams a content platform they can extend with code and deploy into their own AWS account, rather than relying on a hosted CMS or managing servers themselves.
It combines a headless CMS and GraphQL API with a visual Website Builder, asset management, publishing workflows, and native multi-tenancy. Its extension framework covers API logic, admin UI, infrastructure, and CLI commands. That makes it most relevant to organizations building complex content systems or embedding a white-label CMS, rather than teams looking for a simple blog or a no-code SaaS product.
Key Features
- Define content models in the admin UI or in code, with GraphQL access, permissions, localization, and versioning.
- Build and render pages with the visual Website Builder and its Next.js SDK.
- Manage digital assets with folders, tagging, search, and CDN delivery.
- Configure multi-step publishing approvals, reviewer assignments, scheduled publishing, and audit trails.
- Isolate tenants, users, assets, and permissions within one deployment, including hierarchical tenant structures.
- Extend the platform with TypeScript lifecycle hooks, GraphQL resolvers, React admin components, and Pulumi infrastructure changes.
- Use its MCP server and AI skills to give coding agents platform-specific context for generating extensions and configurations.
- Deploy AWS infrastructure through the Webiny CLI and Pulumi, with local watch commands for admin and API development.
Use Cases
- An enterprise content team needs a self-hosted CMS with custom models, permissions, and approval workflows on AWS.
- A SaaS company wants to embed and white-label a CMS for multiple customers, with tenant isolation managed by the platform.
- A team wants to build custom business logic around content events using TypeScript hooks and GraphQL extensions.
- A developer team needs a visual page-building experience but wants to render pages through its own Next.js frontend.
What you need
Detected in the repository
- Node.js >=24.0.0 (from package.json)
- A test suite and automated checks on GitHub Actions
Getting Started
Create a project and deploy it to AWS:
npx create-webiny-project my-project
cd my-project
yarn webiny deploy
The first deployment provisions AWS resources and requires an AWS account with programmatic access. See the README and documentation for prerequisites and setup details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Considerations
- Webiny runs on AWS only. Deployment provisions resources in your account, so teams should assess AWS architecture, costs, and operational requirements before adopting it.
- The repository requirements specify Node.js 24 or later. The README's quick-start prerequisites mention Node.js 22+, so check the current project documentation and package requirements when setting up.
- It is a developer platform, not a turnkey no-code CMS. Customization is centered on TypeScript and React, and infrastructure changes use Pulumi.
- The project is active, with recent commits and releases and contributions from many developers. Its reported top contributor share is substantial, though the project health data does not flag it as concentrated.
- The README describes a Community Edition under MIT and separate commercial Business and Enterprise editions. Confirm which edition and licensing terms cover the capabilities your deployment needs.
Found this useful?
Share it with someone who would like webiny-js.