Uncategorised decision
Launch
A small-capability discovery site (profiles + search + contact) is realistic for one technical person to build and run, but the product’s durable value likely depends on discoverability/network effects and a community that are hard to reproduce.
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-off32 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
- Put up simple public profiles for coders, allow employers/searchers to discover and message them.
What it still won’t have
- Established user base and discoverability/network effects
- Brand trust and marketplace liquidity
- Any proprietary community features or moderation tooling the vendor operates
- Polish, analytics, and continuous product improvements from a dedicated team
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Launch 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 minimal discovery web app in Next.js + TypeScript, Postgres (via Prisma), and Docker. Core features in scope: user signup (email/password), editable public coder profiles (name, bio, skills/tags, avatar), searchable listings with filters and pagination (full-text search), a contact form that sends email via SendGrid, and an admin moderation UI to approve/flag profiles. Out of scope: payments, recommendations, social feeds, mobile apps, large-scale realtime messaging. Include error handling, input validation, tests for API routes and key components, Dockerfile + simple deploy script for a single VM, and basic monitoring/logging.
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 →Cited sources · 1
Every page the run actually retrieved.
- official productLaunch — Where Vibe Coders Get Discovered
Integrity checks
What held up, and what did not.
