Websites and hosting decision

GetWaitlist / LaunchList

A competent developer can build and run a narrow replacement (signup widget, referral links, emails, simple admin) within a week and modest monthly cost; you lose the vendor polish, integrations, and managed hosting/scale.

Visit website
Subscription$15/month
Initial build30 hours
Monthly upkeep6 hours + $60
Evidence3/3 runs agree

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

  • Collect email signups -> generate per-user referral links -> store signups and referral counts -> send confirmation and referral emails -> display basic leaderboards/analytics in admin UI.

What it still won’t have

  • Hosted landing pages and turnkey embeddable widget templates
  • No-code platform guides and prebuilt platform-specific embeds (Carrd/Framer/Webflow/etc.)
  • Polish around email templates, domain verification, and deliverability handled by vendor
  • Built-in integrations onboarding and support (Slack/Discord/HubSpot/Airtable/Zapier)
  • SLA/uptime guarantees and managed scaling

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 5 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 self-hosted waitlist service using Node.js (Express), PostgreSQL, and a simple React admin UI. In scope: (1) public landing page + embeddable widget that POSTs email and optional referrer code; (2) backend API to create signups, generate short referral codes, and attribute referrals; (3) store data in Postgres with schemas for users, signups, referrals, and events; (4) transactional emails via SendGrid (support custom-from domain verification step documented); (5) admin UI to list signups, show referral leaderboard, and basic charts; (6) a webhook endpoint to forward new signups to Zapier/Webhooks. Out of scope: multi-tenant org billing, advanced analytics, A/B testing, and enterprise compliance. Include input validation, idempotency for signup requests, error handling, and automated tests for API endpoints and referral attribution logic. Provide Dockerfiles and a docker-compose for local development and a short deploy guide for a single DigitalOcean droplet plus managed Postgres.
How we checked2 sources · 3/3 runs agreed · evidence score 83

How the score was reached

  • Build verdict base78
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score83

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

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