Websites and hosting decision
Carrd
A narrow replacement (static templates + simple editor + hosting) is realistic for a small team to build and host; reproducing Carrd's full polish, template library, connectors, and Pro account features is larger and better left to the hosted product.
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 Carrd alternatives, with the arithmetic →
What a replacement has to do
- Create and publish simple one-page sites from templates and optional forms/widgets.
What it still won’t have
- Polished WYSIWYG editor and UX polish
- Built-in catalog of dozens of templates
- Integrated one-click third-party form/payment connectors
- Hosted analytics, ready SSL provisioning, and domain management UI
- Pro account features like no-branding and multi-site management
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 13 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 self-hosted one-page site builder using Next.js + React + Tailwind, deployable to Vercel or Netlify. In scope: (1) a template catalog with 5 editable templates, (2) a lightweight in-browser editor to change text, images, colors, and responsive layout settings, (3) a static-site build & publish pipeline that deploys to a hosting provider with HTTPS, (4) a simple form endpoint that forwards submissions to an email address and supports Mailchimp via webhook, (5) admin UI to manage up to 3 published sites. Out of scope: a full WYSIWYG drag-and-drop canvas, payments integration, multi-account/team features, and billing. Include server-side tests for publish and form endpoints, front-end unit tests for editor components, basic error handling, CI for automated builds, and instructions to deploy and configure a custom domain and SSL.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Evidence score60
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 · 4
Every page the run actually retrieved.
- official productCarrd - home
- official docsCarrd - Docs
- open sourcewebstudio-is/webstudio
- open sourcePlanetable/Planet
Integrity checks
What held up, and what did not.
