Websites and hosting decision

Dorik

A technical user can realistically build a narrow replacement that generates and exports AI-driven static sites, but reproducing Dorik’s full hosting, integrations, templates, editor polish, and agency features would require a larger effort or ongoing ops.

Visit website
Subscription$29/month ✓ verified
Initial build80 hours
Monthly upkeep8 hours + $50
Evidence3/3 runs agree

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.

What a replacement has to do

  • Provide a text prompt → generate a multi-page static site (HTML/CSS/images) → let user edit pages in a WYSIWYG editor → store content/collections in a DB + media in object storage → export/publish static files to a CDN-backed host

What it still won’t have

  • Hosted global CDN and managed uptime
  • Built-in forms and integrations (Zapier, Mailchimp, Airtable)
  • White-label dashboard and client billing workflows
  • Cookieless built-in analytics and DDoS/Cloudflare protections
  • Polish: 250+ UI blocks, templates, and a mature WYSIWYG editor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 3 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

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

Not run yet
Build a minimal AI-powered static-site builder using Node.js (Express), React for the editor, PostgreSQL, and AWS S3 + CloudFront for hosting. Scope in: (1) a simple API endpoint that accepts a natural-language prompt and uses OpenAI (or other LLM) + an image API to generate multi-page HTML/CSS and images; (2) a React WYSIWYG editor that can load the generated pages, allow inline text edits and block reordering, and save changes back to the PostgreSQL CMS; (3) media uploads to S3 and storage of collections/posts in Postgres; (4) an export endpoint that bundles static files and uploads to S3/CloudFront and provisions a Let’s Encrypt SSL certificate for a custom domain; (5) basic analytics (pageviews) and a simple dashboard to list sites. Out of scope: full template library, white-label client billing, extensive third-party integrations, and advanced team permissions. Include error handling, input validation, and unit/integration tests for API endpoints and editor save/load flows.
How we checked5 sources · 3/3 runs agreed · evidence score 67

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.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded