Learning and careers decision

Provenideas

A competent technical user can reproduce the core product (catalog + checkout + gated access) in about a week; the vendor’s ongoing curated dataset, scoring, and monthly drops are the primary things you'd lose.

Visit website

Built by Rahul K, who ships 15 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-off36 h to build

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

  • Browse a catalog of curated idea entries, search the library, purchase one-time access, and unlock full build prompts for each idea.

What it still won’t have

  • Permanent access to the ProvenTools Library’s ongoing monthly drops and included updates
  • ProvenScore data, curated evidence records and any proprietary scoring/metadata
  • Built-in semantic search and any proprietary dataset behind it

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Provenideas 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 web app (Next.js + Postgres) deployed to Vercel (frontend) and a small managed Postgres (PlanetScale or Supabase) that implements: - a catalog of idea entries stored as Markdown in Postgres and served via a JSON API; - a simple full-text search endpoint (Postgres full-text search) for library browsing; - Stripe one-time payment for a single "ProvenTools Library" purchase flow plus webhook to create a user entitlement; - user auth (NextAuth or Supabase auth) and middleware that gates access to full build-prompt pages for entitled users; - an admin panel (protected route) to create/edit ideas and upload metadata. Out of scope: implementing any proprietary "ProvenScore" algorithm or seeded curated dataset. Include input validation, error handling for payment/webhook failures, basic automated tests for API routes, and deployment scripts for Vercel and the managed Postgres provider.
How we checked1 sources · 3/3 runs agreed · evidence score 85

How the score was reached

  • Build verdict base78
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score85

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