Websites and hosting decision

Readymag

A single developer can build a narrow self-hosted visual site-editor that exports static sites and publishes them, but reproducing the full polished Readymag product (templates, editor polish, hosting UX, ongoing improvements) is expensive and time-consuming.

Visit website
Subscription$20/month
Initial build80 hours
Monthly upkeep10 hours + $0
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

  • A minimal useful replacement can let a user visually compose pages from components, save layouts as static HTML/CSS, and publish them to a CDN.

What it still won’t have

  • Polish of a mature visual editor (UX edge cases, advanced layout controls)
  • Built-in theme/template marketplace and curated design assets
  • Integrated hosting, CDN, and one-click publishing experience
  • Large-template library and ongoing product improvements/support

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 1 seat.

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 visual website-builder using React for the editor, Node.js + Express for an API, Postgres for project storage, and AWS S3 + CloudFront for asset hosting. In-scope: a React single-page WYSIWYG editor that supports placing text/image blocks, editing text, dragging/resizing blocks, saving page state to Postgres, exporting/serializing to static HTML/CSS, uploading assets to S3 with automatic image optimization, and a publish endpoint that writes the static files to S3 and triggers CDN invalidation. Out of scope: multi-user collaboration, integrated payments, marketplace, full template library, advanced animation toolset. Require: authentication, input validation, error handling for uploads/publish, basic unit and integration tests for editor save/export and publish pipeline, and a README with deployment steps.
How we checked3 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score64

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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page — this pricing page renders its price in the browser✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded