Health, home and travel decision

BERACE

A small technical team can build a useful predictions-and-leaderboard replacement (web-only) in a few weeks, but reproducing BERACE's live telemetry, translated radio, native apps, polish and existing user base would be costly—so building a narrow self-hosted alternative is realistic but not a full replacement.

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

$100one-off48 h to build

$0/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

  • Allow users to submit predictions for race events, compute per-event leaderboards, create/join private teams with private leaderboards, and view basic live results/standings updates.

What it still won’t have

  • Live translated driver radio feed
  • Real-time interactive track map and live tyre/weather telemetry
  • Advanced driver & track statistics and community trends feeds
  • Polished native iOS/Android apps and existing user community/scale
  • Event activation tooling and customization services

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

BERACE 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 BERACE-like web app using Node.js (Express), Postgres, and a React + Tailwind frontend served from Vercel or Netlify. Core features in scope: user sign-up (email + OAuth), create/join teams, submit predictions against a race schedule, close submissions by scheduled deadline, background worker to compute event leaderboards and update user/team rankings, mobile-responsive UI for submitting picks and viewing leaderboards, and simple email notifications for deadlines/results. Out of scope: live telemetry (track map, tyre/weather), translated radio streams, native mobile apps, and event activation/custom branding. Include input validation, error handling, database migrations, a CI pipeline, basic unit/integration tests for API and leaderboard logic, and Docker-based deployment instructions.
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 recorded