Creator and commerce decision

Mediavinecalculator

A capable technical user can build and maintain a useful replacement in about a week since core functionality is a small form, a deterministic estimator and simple hosting; the vendor's claimed proprietary AI and brand are the main things you won't replicate.

Visit website

Built by 两万焦, who ships 8 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

$50one-off29 h to build

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

  • Collect monthly sessions and traffic attributes via a web form -> apply niche & seasonality RPM mapping -> compute session-RPM and monthly/quarterly/annual earnings -> display downloadable results and scenario comparisons.

What it still won’t have

  • Vendor-trained proprietary AI model and any opaque dataset advantages
  • Brand recognition, curated badges/testimonials, and existing user traffic
  • Any advanced ML-backed accuracy claimed by the site (if they use proprietary models)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Mediavinecalculator 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 lightweight Mediavine earnings calculator: use Next.js for frontend, Node/Express (or Next API routes) for server logic, Postgres (Supabase) for optional run storage, and deploy to Vercel. In scope: responsive input form (sessions, niche, region, device, engagement, seasonality), a maintainable niche-to-RPM JSON dataset, a deterministic calculation engine that outputs session-RPM, monthly/quarterly/annual forecasts and scenario comparison sliders, result export (CSV), basic input validation, error handling, unit tests for calculation logic, and CI for deployments. Out of scope: training or hosting large ML models, paid LLM inference, user accounts, payment flows, or advanced analytics dashboards. Provide integration tests for the API, and add documentation for how to update RPM mappings and deploy.
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.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded