Websites and hosting decision
MakeLanding
A competent engineer can reproduce the core generator+hosting and a simple editor in a week and run it cheaply, but the full commercial product (stock library, polished template catalog, analytics+support, and scale) would take more effort to match.
Visit website↗Built by Marc Lou, who ships 32 products in this index
$9/mo
$108/yr
Read off the official pricing page.
$50one-off30 h to build
$100/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 12 seats.
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 MakeLanding alternatives, with the arithmetic →
What a replacement has to do
- User provides a short project description → call LLM(s) to generate headline/body copy, call image model(s) for logo/illustrations, assemble HTML/CSS/JS (Tailwind + DaisyUI) from templates → serve the page and provide an editor and shareable link.
What it still won’t have
- Proprietary stock-photo library of 5M images and integrated licensing
- Polished, curated template library and UX refinements from the commercial product
- Built-in analytics, customer support, and multi-tenant subscription management
- Any usage quotas, SLA, and the vendor's optimizations for generation speed/consistency
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 12 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 AI landing-page generator and host using Next.js (React) for the frontend, a small Node/Express API backend, Postgres for user/pages metadata, and Vercel (or Netlify) for static hosting. Core features in scope: 1) prompt UI to collect project description and metadata, 2) call an LLM to generate structured copy (title, subtitle, features, CTAs), 3) call an image-generation API for logo/illustrations and store results in S3 (or provider storage), 4) assemble and render static Tailwind+DaisyUI HTML pages from templates, 5) simple browser editor to edit text and swap images, 6) publish flow that writes static files to a CDN-backed host and issues a shareable link, 7) basic analytics (page views) and custom domain setup. Out of scope: built-in 5M stock photo library, multi-tenant billing UI, full WYSIWYG page-builder parity, and advanced SEO automation. Include error handling, input validation, API retry/backoff, tests for API routes and generation pipeline, and deployment scripts (Terraform or provider CLI) to stand up storage, DB, and hosting.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- Evidence score63
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 pricingMakeLanding — homepage (product + pricing)
- official productMakeLanding — product page (features)
- open sourcewebstudio-is/webstudio
- open sourcenotionnext-org/NotionNext
Integrity checks
What held up, and what did not.
