Open Source Webflow Alternatives: The License Bench
By the SoftSea editorial team
Photo: Daniil Komov / Pexels
Two jobs are hiding in this query
A visual builder and a headless CMS both get called Webflow alternatives, and they are not the same purchase. The builder job: a canvas where pages are designed visually, published as a site, and editable by the person who designed them, with the code open and the hosting yours. The headless job: a content backend with an API, where the frontend is a separate thing your team designs and builds in code, and the visual editing happens in an admin panel, not a canvas. Webflow refugees split evenly between the two and rarely know it: the designer who wants their canvas back without the subscription, and the team that discovered their real need was structured content with an API. This bench grades the builder job first (Webstudio, Silex, GrapesJS), places WordPress and Ghost as the open source publishing answers, names the headless field honestly (Strapi and Payload are graded in the developer bench on this site), and states every license exactly, because in this category the license is the feature list's foundation.
Project
Job
License
Deciding strength
Webstudio
Visual builder
AGPL-3.0
The closest open shape to Webflow's canvas, with data from your own sources
Silex
Visual builder for static sites
AGPL-3.0
Publishes static output you host anywhere; the simplest self-host shape
GrapesJS
Embeddable editor framework
BSD-3-Clause
Not a site builder: the editor you put inside your own product
WordPress
Publishing platform
GPLv2 or later
The open source incumbent with the deepest ecosystem
Ghost
Publishing platform
MIT
The writer-first open source publication, self-hosted free
Directus
Headless CMS
Monospace Sustainable Core License (source-available, not open source)
The correction: excellent software, a license with conditions
Webstudio: the canvas, opened
Webstudio is the bench's reference because it answers the Webflow complaint most directly: a visual builder in the Webflow lineage whose code is open under AGPL-3.0, whose cloud free tier covers small sites, and whose design treats content as data that can come from your own CMS or API rather than only from a built-in collection. The dataset carries its paid cloud price as an honest null (it was not read to the dataset standard), because the open source point is that the cloud is optional: the builder can be self-hosted, and the sites it produces are not hostages to a plan ladder. The AGPL terms deserve one plain sentence: if you offer the builder itself as a network service to others, the license asks you to share your changes; running it for your own sites is the ordinary case the license permits. Grade Webstudio as the exit for the designer whose requirement is the canvas plus an exit guarantee. The comparison below puts Webstudio, WordPress, and Webflow side by side from the dataset.
Interactive tool
Comparison Builder
Pick two or three products and see them side by side on the numbers that decide the purchase.
Measure
Webstudio
WordPress
Webflow
Starting paid price
Free
$4 per month, flat
$15 per month, flat
Free option
Free plan: the builder is free and open source; the cloud free tier covers small sites
Free plan: the software is free and open source; WordPress.com has a free plan with ads and a subdomain
Free plan: Starter with a webflow.io subdomain, 2 static pages, and 50 CMS items
Webflow users who want an exit that stays open, developers who self-host, sites fed by an external CMS or API
blogs and content sites at any scale, sites that need one specific plugin-shaped feature, owners who want to be able to move hosts
marketing sites with a blog, agencies shipping client sites, designers who think in CSS
Strengths
Your site is not hostage: export and self-host the project; Visual canvas modeled on the Webflow workflow; Connects to external data sources instead of one built-in CMS
The deepest plugin and theme ecosystem in the field; Your content and database are portable to any host; A hiring and help market larger than every rival combined
The strongest visual design canvas in this set; CMS and hosting in one bill; Clean semantic markup compared with drag-and-drop rivals
Watch out for
Smaller ecosystem and template library than Webflow or Framer; Self-hosting makes performance and updates your job; Cloud Pro pricing was not verified for this dataset
Self-hosting means updates, backups, and security are yours; Plugin quality varies and plugin conflicts are a real cost; The block editor still divides its own users
Two bills: a site plan per site plus a workspace plan per team; Full code export needs a workspace tier and still excludes CMS content; Bandwidth overages and AI credits stack on top of the sticker
Lowest entry price: Webstudio at Free per month flat. Real free plan: Webstudio, WordPress, Webflow. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.
All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.
Silex and GrapesJS: the static builder and the framework
Silex (AGPL-3.0) is the narrower, older answer: a free visual builder whose output is a static site you host anywhere, which makes its self-host story the simplest on the bench (there is no application server to run; the builder produces files). For marketing and portfolio sites that are genuinely static, that shape beats a hosted CMS on cost, security surface, and longevity: the site outlives the tool. GrapesJS (BSD-3-Clause) is routinely mislisted in this field, including by incumbents this teardown read, so the bench states its job plainly: GrapesJS is a framework for building editors, the canvas component inside newsletter tools, page builders, and SaaS products. It is the right answer for a developer building a product with an editor inside it, and a category error for a site owner who wants to publish a website this week. The BSD-3-Clause license is the most permissive on the bench, which is exactly why product teams embed it.
WordPress, Ghost, and the correction the field keeps missing
WordPress (GPLv2 or later) and Ghost (MIT) are the publishing answers: both free software, both self-hostable, graded in full in the WordPress cluster on this site. Their presence here matters because many open source builder searches end at a publishing platform once the reader admits the site is a publication. Then the correction. Directus appears on open source Webflow lists across the field, and it is not open source: it ships under the Monospace Sustainable Core License, a source-available license with conditions, which its own project states. The same flattening catches Plasmic in the teardown reads (an MIT builder over an AGPL platform folder) and, in the WordPress field, Statamic and Craft. None of this makes Directus bad software; it makes the label wrong, and a bench that cannot get the label right cannot be trusted with the rest of the comparison. Source-available can be the right purchase. It is graded here as what it is.
What to check before you self-host a builder
Four checks, in order. Job check: write down whether you need a canvas or a content API; half the field is the wrong job for you and no license fixes that. License read: open the repository and read the license file yourself, checking for the source-available shapes (MSCL and custom licenses) that listicles flatten into open source. Output test: build one real page and inspect what ships (semantic markup, your classes, your assets) and where it can be hosted. Activity check: read the commit and release history for the last ninety days; an open source builder you self-host is a dependency you now maintain, and a quiet repository is a roadmap answer.
The verdict
The canvas without the cage: Webstudio, AGPL-3.0, cloud optional. Static sites with the simplest possible hosting: Silex, whose output is files. An editor inside your own product: GrapesJS, BSD-3-Clause, chosen as a framework because that is its job. A publication: Ghost (MIT) for writers, WordPress (GPL) for ecosystem depth. And the standing rule of this bench: when a list calls a source-available product open source, it has told you how carefully it read everything else on the page.
Interactive tool
The open source builder checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 6 complete
0% done
Related guides
The shortlist does not end here. These related guides cover the sibling tools, matchups, and pricing questions closest to this one.
What is the best open source alternative to Webflow?
Webstudio: a visual builder in Webflow's lineage, open under AGPL-3.0, with a cloud free tier and a self-host path. Silex (also AGPL-3.0) is the answer for static sites. If the real job is publishing rather than building, Ghost (MIT) and WordPress (GPL) are the open source answers.
Is Directus open source?
No. Directus is source-available under the Monospace Sustainable Core License, which carries conditions the open source licenses do not. It is capable software and appears on this bench as the standing correction, because the field keeps listing it as open source.
What does AGPL-3.0 mean for my website?
For sites you build and run for yourself, AGPL-3.0 permits the ordinary case. Its distinctive term triggers when you offer the software itself as a network service to others: then your changes to it must be shared under the same license. Building client sites with Webstudio or Silex is not that case; reselling the builder as a hosted service is.
Is GrapesJS a website builder?
No. GrapesJS is a framework for building editors, BSD-3-Clause licensed, embedded by product teams inside newsletter tools and page builders. A site owner who wants to publish a website needs Webstudio or Silex; a developer building a product with an editor inside it needs GrapesJS.
Can I self-host Webstudio for free?
Yes: the builder is free and open source, and self-hosting moves the cost to your own infrastructure. The cloud free tier covers small sites if you prefer not to operate anything. The dataset carries the paid cloud price as a null because it was not read to its verification standard, not because it is hidden.
Photo credits: Daniil Komov (Pexels). Photos are served from this site; follow the credit to the library page for the original.