Automation and integrations decision

WasepJe.com

A capable technical user can build and run a lightweight WhatsApp link rotator (the product's core is simple routing, weighting, QR generation and counting); the hosted product provides convenience, hosting and polish but no evident durable moat.

Visit website
You pay

$7.5/mo

$90/yr

Read off the official pricing page.

You’d pay instead

$50one-off30 h to build

$10/mo3 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 WasepJe.com alternatives, with the arithmetic →

What a replacement has to do

  • Create short link with custom slug -> store phone numbers and weights -> serve redirect endpoint that selects a phone by weight (optionally delay) -> generate QR code for the link -> track clicks and show simple analytics / admin UI.

What it still won’t have

  • Hosted, maintained service and uptime guarantees
  • Built-in billing/upgrade flow and hosted payments
  • Any proprietary polish, branding, or UX refinements of the vendor product
  • Official support and automatic product updates

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 small self-hosted WhatsApp link rotator as a Node.js (Express) app with PostgreSQL. Core features in scope: create custom link slugs, add unlimited phone numbers with integer weight, produce a redirect endpoint that selects a number by weight and redirects to the appropriate wa.me URL (support optional configurable delay), generate and cache QR codes for each link, increment click counters and expose a minimal admin UI to CRUD links and view click counts. Out of scope: payment processing, multi-tenant SaaS billing, advanced analytics. Include error handling, input validation, unit tests for selection logic, and a Dockerfile + docker-compose for local deploy.
How we checked4 sources · 3/3 runs agreed · evidence score 93

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score93

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✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded