Health, home and travel decision

Play-kurt

A technical user can build a useful local-game finder (create/list/join/search/rate) in a few months, but reproducing the product’s app-store polish, active user base, and partner relationships is not realistic as a drop-in replacement.

Visit website

Built by Alberto Ravasini ⚡, who ships 5 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

$100one-off80 h to build

$120/mo6 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

  • Users create/list local games, browse and join nearby games, invite friends, and rate players after matches.

What it still won’t have

  • App-store distribution polish and review-handling
  • Existing user base and network that surfaces local games
  • Partnerships with sports centers and local marketplace reach
  • Polished mobile UX, analytics, and moderation workflows

What remains hard

  • Brand trustKurt is the go-to hub for connecting with all the players in town.
Read the build prompt

First-year cost

No published price

Play-kurt 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 minimal clone of Play-Kurt: implement a React Native mobile app (or PWA) and Node.js (Express) backend with Postgres. Core features in scope: user auth (email + OAuth), CRUD for games (time, location, capacity, price, role), geolocation-based search and map view (Google Maps or OpenStreetMap), join/invite flows with push notifications, post-game ratings and simple per-player stats, and basic admin endpoints to manage games. Out of scope: payment processing, enterprise partnerships, advanced analytics, and large-scale matchmaking. Include input validation, error handling, unit tests for backend routes, and CI setup for deployments. Deliver Dockerfiles and terraform/Cloud Run (or Heroku) instructions for hosting.
How we checked1 sources · 3/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 3/3 assessment runs agreed+4
  • Evidence score56

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.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat quoted from the page