Webiny: a TypeScript CMS framework that deploys into your own AWS account
Open-source, self-hosted CMS platform on AWS serverless (Lambda, DynamoDB, S3). TypeScript framework with multi-tenancy, lifecycle hooks, GraphQL API, and AI-assisted development via MCP server. Built for developers at large organizations.
At a glance
- What is it?
- Webiny is a self-hosted CMS built on Lambda, DynamoDB, S3 and CloudFront, extended through TypeScript code in an extensions folder. This piece covers the deploy flow, the four extension types, multi-tenancy and the AWS dependency that comes with all of it.
- Who is it for?
- Webiny suits a developer team that is already on AWS, wants a CMS it can extend with typed code, and needs tenant isolation from one deployment. It is a poor fit for anyone who wants a CMS without an AWS account or who prefers to configure everything through a UI.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- webiny/webiny-js8,053 ★ · +18
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| webiny/webiny-js | 8k | 8.1k |
18 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Everything runs inside your AWS account, provisioned by Pulumi
Webiny is an open-source content platform that runs on Lambda, DynamoDB, S3 and CloudFront inside an account you own. Infrastructure is provisioned through Pulumi in a single deploy command, and the infrastructure templates are open source, so you can change Lambda memory, add CloudWatch alarms, adjust VPC configuration or attach custom AWS resources. The architecture sketch shows Lambda for the API and business logic, DynamoDB for content storage, S3 for assets and CloudFront as the CDN, with OpenSearch marked optional. The stack is TypeScript, React, GraphQL, Node.js, Pulumi and AWS serverless services. The trade is clear: you do not manage servers, patching, scaling or capacity planning, but the bill, the IAM setup and the AWS service limits are yours.
Three commands to a deployed admin, after a 5 to 15 minute provision
The prerequisites are Node.js 22 or newer, Yarn, and an AWS account with programmatic access. Creating and deploying a project takes three commands:
npx create-webiny-project my-project
cd my-project
yarn webiny deployThe first deploy takes 5 to 15 minutes while AWS provisions resources. When it finishes you get an admin panel URL, and you create the first admin account there. The consequence is that there is no way to try Webiny's full stack without cloud credentials; a laptop-only evaluation is limited to the local development commands described next, and those still target an API and admin you have set up through this flow.
Local development splits into an admin dev server and a local Lambda runtime
Two watch commands cover day-to-day work:
yarn webiny watch admin
yarn webiny watch apiThe first starts the React dev server on localhost:3001, and the second runs a local Lambda execution environment for the API. A new team member clones the repository and runs yarn, and the README says they are then ready to develop. The root workspace of the Webiny repository itself is a private Yarn monorepo with packages/*, e2e, extensions/theme and several scripts packages, plus webiny.config.aws.tsx and webiny.config.standalone.tsx next to the main webiny.config.tsx. If you are only building a project on top of Webiny, you work in your generated project, not in this monorepo.
Four extension types and one lifecycle hook example
All customization lives in the extensions folder and is registered in webiny.config.tsx. API Extensions add GraphQL schemas, resolvers, lifecycle hooks and business logic. Admin Extensions add custom React components, white-label branding, new views and tenant-specific themes. Infrastructure Extensions change AWS resources through Pulumi, such as Lambda functions, S3 buckets and CloudWatch alarms. CLI Extensions add commands for deployment workflows, data migrations and code generators. The sample in the README is a class named NotifyOnPublish that implements CmsLifecycleHook.Interface, takes a SlackService in its constructor and sends a Slack message from an afterPublish method. The framework offers lifecycle hooks, dependency injection, GraphQL schema extensions and admin UI extension points, which is why the project calls itself programmable rather than merely configurable. The cost is that customization is code you must write, test and keep compatible across upgrades.
Multi-tenancy is native, but tenants are managed through the API
One deployment can host thousands of tenants, each isolated in data, users, assets and permissions. Tenants are created and managed programmatically through the GraphQL API, and the hierarchy can be nested, for example Root, then Brand, then Market, or Root, then Client, then Site. For a SaaS that white-labels a CMS inside its own product, that avoids standing up one stack per customer. The consequence is that tenant lifecycle becomes something you build: onboarding, offboarding and any billing logic call the GraphQL API from your own code. All tenants also share one deployment, so a bad release or an AWS limit reached by one tenant affects the whole instance.
What ships in the box: headless CMS, page builder, assets and approvals
The Headless CMS has custom content models, a GraphQL API, field-level permissions, localization and versioning, and models can be defined in the admin UI or in code. The Website Builder is a drag-and-drop page editor with a Next.js SDK, so pages render through your own frontend on Vercel, CloudFront or elsewhere, and custom page elements are React components. The File Manager handles digital assets with CDN delivery, folders, tagging and search. Publishing Workflows add multi-step approval with draft states, reviewer assignments, scheduled publishing and audit trails. A Next.js frontend is therefore a separate project you host and maintain, since the Website Builder supplies the editing and an SDK, not the hosting of your public site.
The MCP server gives AI agents the framework's types, but setup is per tool
Webiny ships an MCP server and AI skills so coding agents such as Claude Code, Cursor and Kiro have context about its architecture and extension points. The suggested tasks include creating content models, building lifecycle hooks, extending the GraphQL API, scaffolding admin extensions and configuring multi-tenancy. The argument for it is that the framework is strongly typed with explicit extension points, so generated code either fits the type system or does not compile. The setup snippet in the README contains only comments saying the server runs locally inside your project and that tool-specific steps are in the docs, so there is no copy-ready command to quote here. Expect to follow the AI-Assisted Development Guide for your editor. The repository also carries .mcp.json, skills/, ai-context/, AGENTS.md and CLAUDE.md at the top level.
AWS lock-in, an unresolved license field and a fast release rhythm
Webiny's own description is a CMS for enterprises hosting on AWS, and the sections above show why that is not incidental: the runtime, storage, CDN and infrastructure code all assume AWS. Moving to another cloud would mean replacing most of what the platform provides. GitHub reports the license as NOASSERTION, and the README badge points at a LICENSE file, so read that file before deciding whether your use, especially an embedded white-label product, is covered. The default branch is next, the repository is not archived, and the last push landed on 2026-10-30. Recent tags are v6.5.1 on 2026-10-28, v6.5.0 on 2026-10-20 and v6.4.11 on 2026-09-11, so minor versions arrive within weeks and upgrades are a recurring task for any extension-heavy project.
Editorial conclusion
Webiny suits a developer team that is already on AWS, wants a CMS it can extend with typed code, and needs tenant isolation from one deployment. It is a poor fit for anyone who wants a CMS without an AWS account or who prefers to configure everything through a UI. Before adopting it, read the LICENSE file yourself because GitHub reports the license as NOASSERTION, and budget for AWS costs and a first deploy of 5 to 15 minutes.
Frequently asked questions
Is Webiny a free CMS?
Webiny is open source and self-hosted in your own AWS account, with no recurring platform fee stated, but you pay AWS for the infrastructure. GitHub lists its license as NOASSERTION, so check the LICENSE file.
What do I need to deploy Webiny?
Node.js 22 or newer, Yarn, and an AWS account with programmatic access. Then run npx create-webiny-project my-project and yarn webiny deploy; the first deploy takes 5 to 15 minutes.
Can AI coding agents work with Webiny?
Webiny ships an MCP server and AI skills for tools such as Claude Code, Cursor and Kiro. Tool-specific setup steps are in the AI-Assisted Development Guide in the Webiny docs.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/webiny-webiny-js)Star history chart for your README
[](https://hysenlabs.com/projects/webiny-webiny-js)Was this useful?