Websites and hosting decision
Webflow
A small team can build a narrow replacement (visual editor + CMS + hosting) over several weeks, but reproducing Webflow's polish, marketplace, AI/AEO features, and enterprise platform is impractical without the vendor platform and ecosystem.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Webflow alternatives, with the arithmetic →
What a replacement has to do
- Create and publish web pages with a visual editor, manage CMS content, and host/publish the site.
What it still won’t have
- Polished visual editor UX and design-system features
- Large template marketplace and 'Made in Webflow' ecosystem
- Native AI/AEO features and analytics integrated into the platform
- Enterprise collaboration, governance, and scale features
- Official hosting SLA, backups, and platform maintenance
What remains hard
- Brand trust
300,000+ brands move the needle with Webflow
- Brand trust
Trusted by teams at
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal hosted visual site-builder on Node.js + React (Next.js) with: a React WYSIWYG page editor that saves page JSON to Postgres; a composable CMS (CRUD REST API + admin UI) for pages and media; a deploy pipeline that builds static HTML/CSS/JS and publishes to a CDN (Netlify/Vercel); form handling that stores submissions and can POST to webhooks; a simple SEO metadata editor and page analytics collector. Out of scope: AI/AEO features, enterprise SSO, template marketplace, and billing. Include error handling, validation, deployment scripts, CI tests (unit + basic integration), and docs for local setup and a one-click deploy to Vercel.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productWebflow homepage
- official pricingWebflow homepage (pricing area)
- open sourcewebstudio-is/webstudio
- open sourcehalo-dev/halo
- official pricingWebflow pricing
Integrity checks
What held up, and what did not.
