Health, home and travel decision

QuitCorn

A technical user can build a useful self-hosted replacement (hosts/blocklist generator + reminders) in about a week using existing open-source hosts lists; larger polished features (mobile apps, extensions, curated proprietary lists) would require more work.

Visit website
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

$50one-off30 h to build

$10/mo3 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

  • User chooses blocking preferences → app builds a curated hosts/blocklist and provides install/download instructions → optional scheduled reminders and progress emails

What it still won’t have

  • commercial polish, branding, and paid support
  • any proprietary blocking rules or curated lists the vendor may maintain
  • mobile apps, browser-extension packaging, or hosted account management dashboards
  • legal or moderated user-support channels

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

QuitCorn 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 hosted service in Node.js (Express) + React with Postgres that lets a user select blocking categories and download a curated hosts/blocklist file. Core features: (1) import and merge upstream hosts lists (use Ultimate.Hosts.Blacklist and StevenBlack/hosts as sources), de-duplicate and tag entries; (2) user-facing web UI to choose categories and generate/download a hosts file; (3) backend API endpoints to create and store a per-user preference record; (4) scheduled worker using node-cron to send reminder emails via SendGrid SMTP API; (5) deployments via Docker to a single small VPS (DigitalOcean) with TLS via Caddy. Out of scope: building browser extensions, mobile apps, paid billing, advanced analytics, or proprietary curated rules. Include error handling, input validation, basic unit tests for merge logic, and startup/deploy documentation.
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