Uncategorised decision
MakerHunt
A small, hosted directory matching the apparent scope is realistic for one technical person to build and maintain; there are no evident durable moats on the site and no published pricing to force buying.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off40 h to build
$15/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
- A minimal MakerHunt replacement is a searchable directory of maker entries: submit/view maker profiles, search and filter listings, and an admin UI to curate entries.
What it still won’t have
- Brand recognition and existing user base
- Polished, productized UX and marketing
- Any proprietary integrations or paid features MakerHunt will include
- Support SLA and hosted convenience
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
MakerHunt 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
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 searchable maker-directory web app using Next.js (app router) + React for frontend, PostgreSQL (Supabase) for storage, and Node/Next API routes for backend. Core features in scope: create/read/update/delete maker profiles with markdown bios and tags; full-text search and tag filtering; public listing and individual profile pages; simple admin auth via GitHub OAuth or magic-link; continuous deploy to Vercel and automated DB backups. Out of scope: payments, recommendations, large-scale analytics, or AI-assistant features. Include input validation, server-side pagination, basic rate-limiting, error handling, and tests (unit for core logic and end-to-end for create/list/search flows).
How we checked
How the score was reached
- Build verdict base78
- 3 cited sources+3
- Evidence score81
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 · 3
Every page the run actually retrieved.
- official productMakerHunt — kljr.online
- official pricingPricing — kljr.online
- official docsFeatures — kljr.online
Integrity checks
What held up, and what did not.
