Developer tools decision
Proventools
A capable developer can reproduce the core library and purchase flow in under a week, but vendor features like evidence-refresh, agent integrations, credits and the live publishing pipeline are nontrivial to replicate and are left out.
Visit website↗Built by Rahul K, who ships 15 products in this index
$9/mo
$108/yr
Read off the official pricing page.
$50one-off19 h to build
$0/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 1 seat.
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
- Search/browse curated ideas, open an idea to read its ProvenScore and 13-section build prompt, copy or download the prompt, and (optionally) request evidence refreshes via the paid Live layer.
What it still won’t have
- Built-in evidence-refresh pipeline and metered credit system (ProvenTools Live features)
- Official MCP/CLI/REST agent integrations and any read-only beta clients
- Any server-side validated "ProvenScore" re-checks that the vendor runs
- Backlink Rocket fulfilment and the vendor-managed monthly drop publishing workflow
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
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
Build a minimal self-hosted ProvenTools clone using Next.js (React) + SQLite (or Postgres) + Vercel (or Fly) + Stripe for payments. In scope: import a JSON library of idea records (650 items) with fields for title, category, ProvenScore, subscores, evidence text, and a 13-section build-prompt; implement search and filtering, paginated idea list, idea detail page with copy-to-clipboard and downloadable prompt (Markdown), user signup and one-time Library purchase via Stripe, gated library access after purchase, and an admin script to append monthly drops (CSV/JSON import). Out of scope: implementing an evidence-refresh pipeline, MCP/CLI/REST agent integrations, metered credit system, and backlink fulfilment. Include error handling, input validation, and automated tests for import, checkout flow, and search.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Price verified on pricing page+3
- 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 · 2
Every page the run actually retrieved.
- official productProvenTools — official product page
- official pricingProvenTools Pricing — one-time Library and $9/month Live
Integrity checks
What held up, and what did not.
