Webstudio: an AGPL builder with one proprietary package in the same repo
Open source website builder and Webflow alternative. Webstudio is an advanced visual builder that connects to any headless CMS, supports all CSS properties, and can be hosted anywhere, including with us.
At a glance
- What is it?
- Webstudio is a TypeScript visual site builder that connects to any headless CMS and can be hosted on your own infrastructure. The core is AGPL-3.0-or-later, one optional package inside the same repository is proprietary, and the front page is a list of links rather than a setup guide.
- Who is it for?
- Webstudio suits a team that wants a visual builder it can host itself and connect to a headless CMS it already runs, and it moves fast enough that a pinned version matters. It does not suit a project that needs uniform licensing across every package, because the optional animation package is proprietary under a separate EULA.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- 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
- webstudio-is/webstudio9,169 ★ · +192
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| webstudio-is/webstudio | 9k | 9.2k |
192 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
AGPL covers the core, and one package in the same repo is proprietary
The licence section splits the repository in two. Webstudio core, described as all functionality in this repository, is free and open source under AGPL-3.0-or-later. The sdk-components-animation package is marked optional, is proprietary, and requires accepting a Webstudio, Inc. EULA at packages/sdk-components-animation/LICENSE before use. The consequence is that self-hosting the entire tree does not mean every part of it is AGPL, and a compliance review that reads the top level licence and stops has missed a second grant inside the same packages/ directory. The answer to whether one licence covers everything is yes for the core and conditional for the animation package, and the condition is an accepted EULA rather than an open licence.
The root package is private at 0.0.0 while releases ship as 0.3xx
The root package.json is named webstudio-root, is marked private, and its version field reads 0.0.0. The numbers that actually ship are elsewhere: releases 0.307.0 on 2026-10-24, 0.308.0 on 2026-10-26 and 0.309.0 on 2026-10-30, three versions in seven days. The top level also carries release.sh and a vercel.json. Consequence: the version in the root manifest tells a consumer nothing about the code they are running, and a project that tracks tags has to accept a release train that moves every few days. The last push is dated 2026-11-02 and the repository is not archived, so the churn is a fact about the release pace rather than a signal about the project's health.
The build command deliberately leaves the fixtures out
Webstudio is a pnpm workspace with apps/, packages/, docs/ and fixtures/ at the top level, and the build script is a single line:
"build": "pnpm -r --filter='!./fixtures/*' build",The filter excludes everything under fixtures/ from the recursive build, which is why that directory sits in the tree next to a check:fixture-sizes script running tsx scripts/check-fixture-sizes.ts. Consequence: a green build is not proof that every directory compiled, and anyone who expects a plain recursive build over the whole tree gets a different result. The workspace also has a check:package-boundaries script calling node scripts/check-package-boundaries.mjs, so the package layout is something the repository enforces on itself.
The front page has no setup command, the workspace scripts do
The README is a set of links: a blog, documentation at docs.webstudio.is, a contributing page, a builder issues tracker and a roadmap published as a GitHub project. There is no install command and no configuration file in it. The commands that exist sit in the root package.json:
"webstudio": "node packages/cli/local.js",
"dev": "pnpm --filter=@webstudio-is/builder dev:local",The same manifest pins packageManager as [email protected], and the repository holds pnpm-lock.yaml and pnpm-workspace.yaml. Consequence: you cannot get from the front page to a running instance without leaving the repository for the documentation site, and the local entry point is a Node script inside packages/cli rather than an installed command. A team on npm or yarn has to translate that setup by hand.
Generated API contracts are committed and checked for drift
Much of the root script list exists to prove that committed files still match their generators. The check:generated-api script regenerates runtime operation contracts in the project-build package and server-only api metadata in the builder, then hands two paths under __generated__ to check-clean-files.mjs. The check:generated-docs script repeats that pattern for docs.generated.ts in two packages. Consequence: a contributor who edits a generated file by hand fails the check, and one who changes a generator has to run several filtered pnpm commands before pushing. The checked-in tree therefore contains derived TypeScript that has to stay in step with the code producing it, a cost the front page never mentions.
Lint is oxlint with warnings denied, and formatting has its own config
The lint script reads oxlint --deny-warnings, configured by .oxlintrc.json, and formatting is handled separately through .oxfmtrc.json. No eslint or prettier configuration appears in the tree. Type checking shows up as tsc --noEmit -p scripts/docs/tsconfig.json inside the docs scripts, and linting is not the same command as formatting even though both are configured at the root. Consequence: a contributor arriving with the usual defaults gets different answers from these tools and may argue with the configuration instead of reading it. The repository does carry .editorconfig, .nvmrc and a .devcontainer/ directory, so the expectations are pinned, just not in the README.
The builder holds no content, so the CMS you pick is the real decision
The project describes itself as an open source website builder and a Webflow alternative that connects to any headless CMS, supports all CSS properties, and can be hosted anywhere, including by Webstudio. The framing is that you own the data, the components and the infrastructure, and that you can use the hosted version or roll out your own. Consequence: this is a builder and not a content store, so what a site looks like and where its content lives are decided by whatever you connect to it, and the repository does not ship the answer. The tree does include a fixtures/ directory and an https/ directory, and check:fixture-sizes measures something in that area, but the README says nothing about what either one holds.
Editorial conclusion
Webstudio suits a team that wants a visual builder it can host itself and connect to a headless CMS it already runs, and it moves fast enough that a pinned version matters. It does not suit a project that needs uniform licensing across every package, because the optional animation package is proprietary under a separate EULA. Before you commit, read packages/sdk-components-animation/LICENSE, check that the 0.3xx release you pin includes the fixes you need, and confirm your CMS is reachable from wherever the builder runs.
Frequently asked questions
Is WebStudio free?
The core, described as all functionality in this repository, is free and open source under AGPL-3.0-or-later. The hosted version is a separate option, and the optional sdk-components-animation package is proprietary and requires accepting a Webstudio, Inc. EULA before use.
How much does Webstudio cost?
The front page states that the core is free and open source under AGPL-3.0-or-later, and that you can use the hosted version or roll out your own. No price list appears in the repository itself, so the repository does not state the cost of the hosted option.
What is webstudio?
It is an open source visual development platform for developers, designers and cross-functional teams, described as a Webflow alternative. It connects to any headless CMS, supports all CSS properties, and can be hosted anywhere, including with Webstudio.
How do I install webstudio?
The README carries no install command and routes you to the documentation at docs.webstudio.is. In the repository the root package.json defines a webstudio script that runs node packages/cli/local.js and a dev script that runs pnpm --filter=@webstudio-is/builder dev:local, with [email protected] pinned as the package manager.
How do I use webstudio day to day?
The front page sends usage questions to the documentation at docs.webstudio.is and points at a roadmap published as a GitHub project. The repository is a pnpm workspace holding apps, packages and docs, so it is laid out as source rather than as a task guide.
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/webstudio-is-webstudio)Star history chart for your README
[](https://hysenlabs.com/projects/webstudio-is-webstudio)Was this useful?