Uncategorised decision
The Next AI Directory
A minimal, useful replacement (searchable directory + submissions) is realistic for one developer to build and run in about a week, but the full product value (audience, manual curation, and brand) is not reproduced.
Visit website↗Built by Ozgur Ozer, who ships 12 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off24 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
- Crawl or ingest AI-directory listings, store metadata, expose searchable listings, accept submissions, and provide an admin verification UI.
What it still won’t have
- Brand recognition and existing audience
- Any manual curation and editorial vetting processes the site currently applies
- Potential integrations, analytics, or paid features not replicated
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
The Next AI Directory 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 lightweight AI-directory web app using PostgreSQL, Node.js (Express or Fastify) for the API, and React for the frontend. In scope: (1) a scraper/importer that fetches a seed list and normalizes name, URL, short description, and popularity metric; (2) a Postgres schema and migrations; (3) REST endpoints for listing, search (text + tag filters), pagination, and a submission endpoint; (4) React listing page with search, filters and pagination, a submission form, and a simple admin UI to approve/reject submissions; (5) a scheduled worker (cron) that re-checks remote URLs and flags dead links. Out of scope: user accounts beyond a single admin, advanced ranking algorithms, paid tiers, analytics dashboards, and a mobile app. Include error handling, input validation, unit tests for API routes, and deployment scripts (Docker + single-node VPS).
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
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 →Integrity checks
What held up, and what did not.
