Uncategorised decision

Sunset.io

The retrieved site contains only a domain and contact email, so a small static site with a contact form fully replaces the visible surface; it's straightforward for a single technical user to implement and maintain.

Visit website

Built by François Rejeté, who ships 6 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$20one-off4 h to build

$0/mo1 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • A smallest useful replacement is a static marketing site with a working contact/lead form and simple analytics.

What it still won’t have

  • Any undisclosed SaaS features (no product pages were retrieved to document them)
  • Built-in dashboards, integrations, or paid features if they exist
  • Vendor hosting, uptime SLA, and support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Sunset.io does not publish a price we could read, so there is nothing to compare against. What building costs is below.

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 small static marketing site using Hugo (or Next.js) deployed to Netlify: include a responsive landing page, an /about and /contact page, a serverless function for the contact form that sends messages to a configurable email (use SendGrid or SMTP), integrate Google Analytics (or Plausible) for basic metrics, configure DNS and HTTPS, include automated deployment from Git, add error handling for form submissions and unit/HTTP tests for the contact endpoint. Out of scope: recreating any unknown backend SaaS features not present on the retrieved site.
How we checked1 sources · 2/3 runs agreed · evidence score 78

How the score was reached

  • Build verdict base78
  • Evidence score78

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

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