Learning and careers decision

Oaki

A technical user can implement a limited replacement (resume generation, basic matching, and form autofill) but cannot cheaply reproduce Oaki's frequently-updated job index, scale, and automated-application quality controls that the site advertises.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off86 h to build

$250/mo6 h/mo upkeep

No published price to break even against.

The code exists. It is not what you are paying for.

These 2 projects are real, published, and do the core job — and this page still says keep paying. What the subscription buys is proprietary data and infrastructure at scale, and none of that ships in a repository. Fork one anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Oaki alternatives, with the arithmetic →

What a replacement has to do

  • Discover jobs, tailor a resume/cover letter per job with an LLM, auto-fill and submit applications, and track application status.

What it still won’t have

  • Proprietary, frequently-updated job index and the ingestion pipeline that sources millions of jobs
  • Scale and reliability of hourly updates and broad company coverage
  • Any recruiting partnerships or placement/network effects that surface directly to employers
  • Polish and QA for automated application quality-control systems

What remains hard

  • Proprietary dataMillions of jobs sourced directly from company websites; updated every hour, with new companies added every day.
  • Infrastructure at scaleMillions of jobs sourced directly from company websites; updated every hour, with new companies added every day.
Read the build prompt

First-year cost

No published price

Oaki 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a self-hosted job-search + resume automation service using Node.js (Express), Postgres, a small React frontend, and a headless-browser worker (Puppeteer). Core features in scope: (1) a job ingestion pipeline that crawls and normalizes job postings into Postgres with an hourly scheduler; (2) a user profile and preference UI; (3) LLM-driven resume and cover-letter generation (callable API layer) and HTML-to-PDF export; (4) an automation worker that uses Puppeteer to autofill application forms and submits; (5) an application tracker UI and background job queue (Bull/Redis). Out of scope: building a large-scale worldwide job index or native mobile apps. Include robust error handling, retries, rate-limiting for crawlers, unit/integration tests for API endpoints and workers, and deployment scripts (Docker Compose).
How we checked4 sources · 2/3 runs agreed · evidence score 22

How the score was reached

  • Pay verdict base20
  • An open-source build was found+5
  • 4 cited sources+3
  • Hard moats found in the evidence-6
  • Evidence score22

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 · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 2 moats quoted from the page