webiny-js

webiny/webiny-js

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.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
20 Nov 2026
today
Ship score
73/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
8.1K
Forks
685
Open issues
394
Watchers
68
Primary language
TypeScript
License
Other
Created
9 Jan 2018
Owner
webiny · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 309 startups in the directory ship primarily in TypeScript.

Topics

#ai-assisted-development#aws#aws-lambda#cms#graphql#headless-cms#lambda#lambda-functions#mcp#multi-tenant#nextjs#nodejs#open-source#react#serverless#serverless-architectures#typescript#white-label

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 19 Nov 2026 — os_startup 97%, self-hostable 80%, hosted offering 73%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 19 Nov 2026, found by the weekly discovery job at confidence 0.96. Answered by jev-1.14.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 20 Nov 2026This is the badge for webiny/webiny-js, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/webiny/webiny-js.svg)](https://ossean.com/webiny/webiny-js)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.