Webflow open source alternatives

The one thesis that will save you a week

The real question is not “which open-source Webflow clone has the nicest landing page?” There is no obvious clone in this candidate set, and pretending otherwise is how you end up evaluating a database as a page builder. Ask instead which part of Webflow you are trying to reclaim: visual design control, content management, hosting ownership, or the ability to ship without another SaaS meter running in the background. Pick the tool that replaces that dependency, then accept that an open stack may mean two or three focused tools instead of one glossy dashboard.

Why people are leaving Webflow in 2026

Webflow’s Basic site plan starts at $25/mo when billed monthly, or $15/mo billed yearly. That is the entry paid tier, not the total cost of running a real team. The Free Starter tier exists, but it only gives you a webflow.io subdomain, which is useful for poking around and less useful for a serious marketing site.

The bill gets more complicated once the site becomes an actual business asset. Site plans stack with Workspace seats and add-ons, including Localize from $9/mo and Optimize from $299/mo. Bandwidth overages are billed separately. None of that is automatically unreasonable, but the final number is no longer the number printed on the first pricing card.

The bigger issue is control. Webflow’s visual builder produces markup you cannot self-host or move off Webflow’s hosting. You can export code in some contexts, but exporting a pile of HTML and CSS is not the same thing as exporting the editing system, CMS workflow, hosting configuration, and future content pipeline. For agencies and design-led teams, that distinction matters more than another animation preset.

So the Webflow refugee has to choose between convenience and ownership with open eyes. A self-hosted stack gives you portable files, infrastructure control, and fewer vendor-specific constraints. It also gives you deployment work, maintenance, and the deeply unglamorous responsibility of making backups before Friday afternoon.

The alternatives that matter

Supabase

Supabase is not a Webflow replacement in the visual-builder sense. It is a Postgres development platform for web, mobile, and AI applications, with databases, authentication, storage, and related backend capabilities. That makes it useful when the Webflow site has outgrown “marketing site” status and now needs accounts, structured application data, forms, gated content, or custom product behavior. You still need a frontend and a deployment path, but you own the application architecture instead of trying to make a page builder impersonate one.

Live GitHub metrics: 108996 stars, Apache-2.0 license, 1126 open issues, last push 2026-09-09.

Pick Supabase if Webflow is currently serving as an accidental application backend, or if you want a durable data layer behind a custom frontend. The official cloud is available, and the entry tier starts at $0 and then bills purely on volume; the supplied data does not specify the free allowance, so there is no honest allowance number to quote. Skip it if your requirement is “let a marketer drag a section onto a page and publish it” because Supabase will respond to that request with a database schema and an uncomfortable silence.

Strapi

Strapi is the closest practical fit here for teams replacing Webflow’s CMS layer. It is a developer-first, fully customizable headless CMS built with JavaScript and TypeScript. Content editors manage structured content in Strapi, while the frontend can live wherever you want: a static host, your own server, or an application framework selected for the project. This separates content from presentation, which is liberating when you have several sites or channels and mildly annoying when you wanted one button called “publish website.”

Live GitHub metrics: 73104 stars, NOASSERTION license, 556 open issues, last push 2026-09-09.

Pick Strapi if your Webflow project is really a content operation: collections, authors, locations, case studies, documentation, or reusable marketing content. It supports self-hosting and official cloud, with the official SaaS entry price at $15 monthly according to the supplied data. Skip it if the team has no developer available to build and maintain the frontend, because Strapi does not replace Webflow’s visual layout system. It replaces the content engine and gives you an API; somebody still has to make the site look good.

Coolify

Coolify is the infrastructure piece for people who want to stop renting their entire deployment workflow from a website platform. It is an open-source, self-hostable PaaS that deploys static sites, databases, full-stack applications, and 280+ one-click services on your own servers. In a Webflow migration, that makes it a home for a static export, a custom frontend, Strapi, or the supporting services around them. It is not a CMS or design tool, but it can replace the hosting lock-in that prompted the move.

Live GitHub metrics: 61619 stars, Apache-2.0 license, 653 open issues, last push 2026-09-09.

Pick Coolify if you have a developer or technical agency that wants a repeatable deployment surface without handing every project to Vercel, Netlify, or another managed platform. The official SaaS entry price is $5 monthly, and self-hosting is also supported. Skip it if you are trying to avoid operations entirely. Coolify makes deployment more approachable; it does not abolish DNS, server capacity, TLS, backups, or the consequences of clicking “upgrade” on a production machine without reading the screen.

Penpot

Penpot is an open-source design and prototyping platform for design and code collaboration. It does not publish Webflow sites, manage production CMS content, or provide a visual HTML hosting workflow. What it does provide is a way to keep the design system and prototype process under your control, particularly for teams that use Webflow because designers need more authority over the result than a traditional developer-only workflow provides.

Live GitHub metrics: 59797 stars, MPL-2.0 license, 769 open issues, last push 2026-09-09.

Pick Penpot if the part of Webflow you value most is collaborative visual design, reusable components, and a tighter handoff between designers and developers. The entry tier for its official cloud is $0 monthly, and it supports both self-hosting and official cloud. Skip it if you need a single tool that takes a design and turns it into a production-ready, editable marketing site. Penpot is a design tool, not a secretly rebranded Webflow competitor. That limitation is also why it is a sensible piece of an owned stack.

Decision framework

• If you need structured content with a custom frontend → pick Strapi.
• If you need application data, authentication, or Postgres → pick Supabase.
• If your main objection is hosted deployment lock-in → pick Coolify.
• If designers need an open design and prototyping workspace → pick Penpot.
• If you need a no-code visual builder with hosted publishing → keep Webflow or evaluate a dedicated site builder not represented in this list.
• If you want full ownership and can operate a stack → combine Strapi, Penpot, and Coolify as needed.

What to watch for

The first migration trap is confusing exported output with a portable project. A Webflow export can give you site files, but it does not magically recreate the editor, CMS models, content relationships, form handling, localization workflow, optimization features, or deployment setup. Inventory the actual site before choosing a replacement: static pages, CMS collections, assets, forms, redirects, integrations, scripts, and any content that currently depends on Webflow-specific behavior.

The second trap is assuming that “open source” means “free to run.” The data here shows different licensing and hosting models: Strapi is marked NOASSERTION, Penpot uses MPL-2.0, Supabase uses Apache-2.0, and Coolify uses Apache-2.0. Self-hosting moves the bill from a vendor invoice to infrastructure and maintenance. That can be a very good trade for an agency or technical team, but it is still a trade. The practical replacement for Webflow is usually an owned stack with clear boundaries, not one mythical open-source clone that handles design, content, deployment, analytics, localization, and every new request from marketing.