Learning and careers decision
Remote OK
A competent developer can build a functional job-board clone (listings, payments, feed) in about a week, but reproducing Remote OK's large audience and brand-driven reach is not feasible, so keeping the paid product is reasonable for distribution and scale.
Visit website↗Built by @levelsio, who ships 6 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.
$100one-off40 h to build
$0/mo6 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
- Publish job posts, store and serve listings, accept payments for postings, provide a JSON feed/API, allow search and apply flows.
What it still won’t have
- Immediate access to Remote OK's existing audience ("reach 11,600,000+ remote workers")
- Brand recognition implied by phrase "the #1 Remote Job Platform"
- Curation, vetting and trust signals from an established platform
- Scale, analytics and marketplace liquidity from many employers and applicants
What remains hard
- Brand trust
the #1 Remote Job Platform
- Infrastructure at scale
Post a job to reach 11,600,000+ remote workers
First-year cost
No published price
Remote OK 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 remote-job-board web app using Next.js (React) + Postgres + Prisma + Vercel (or DigitalOcean) with Stripe for payments. In scope: (1) authenticated admin UI to create/approve/edit/delete job posts, (2) public listing pages with server-side search and filters (role, region, tags) and pagination, (3) job post submission form with validation and image upload, (4) Stripe checkout and webhook to mark paid listings live, (5) JSON feed endpoint and a small read-only REST API for listings, (6) apply link support (external apply URL) and basic applicant record storage. Out of scope: large-scale ingestion, user profiles, recommendation engine, advanced fraud detection, and audience/marketing. Require error handling, input validation, webhook verification, schema migrations, unit tests for API routes, and end-to-end tests for posting+payment flow.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score54
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 productRemote OK — front page
- official productRemote Product Jobs — feature page
Integrity checks
What held up, and what did not.
