Websites and hosting decision

Umso

A competent developer can build a usable, template-driven static site generator + publish pipeline and forms/analytics in about a week, but matching Umso's full polish, integrated domain workflows, multilingual management, cookie solution, and support would require substantially more effort or ongoing ops.

Visit website
You pay

$14/mo

$168/yr

Read off the official pricing page.

You’d pay instead

$50one-off30 h to build

$10/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 2 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 Umso alternatives, with the arithmetic →

What a replacement has to do

  • Generate a site from a template, edit pages, publish static site to a host, collect form submissions, and view simple analytics.

What it still won’t have

  • Polished WYSIWYG editor and UX refinements
  • Integrated domain purchase/transfer flow
  • Built-in GDPR cookie solution with settings UI
  • Multilingual site management UI
  • Official support, backups, and managed hosting guarantees

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 2 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 static website builder using Astro (or Next.js) + SQLite/Postgres, Node.js, and a simple React admin UI. In scope: (1) a template-based site generator that creates multi-page static sites from a JSON spec; (2) an admin UI for editing page content (Markdown or structured fields) and triggering builds; (3) a static build/publish pipeline that deploys to Vercel or S3+CloudFront; (4) a forms endpoint that stores submissions in Postgres and sends email via SMTP/SendGrid; (5) basic pageview analytics (client-side beacon + server aggregator) and a dashboard. Out of scope: domain purchasing UI, full-featured WYSIWYG editor, GDPR cookie management UI, and multi-language management UI. Include error handling, authentication for the admin, and automated tests for generator, publish pipeline, and forms endpoints.
How we checked4 sources · 2/3 runs agreed · evidence score 63

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.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded