I built an in-browser resume ATS checker to test if anyone still wants a one-time purchase

Jobscan charges $49.95/month, and its free tier cuts you off after five scans. For someone applying to jobs full-time for a couple of months, that subscription adds up fast. More importantly, uploading a complete work history, phone number, and address to a remote server just to parse text layout felt unnecessary.

I wanted to see if the core utility could be delivered entirely on the client side.

How it works

The tool is packaged as a single HTML file. It uses Mozilla's PDF.js to extract text and layout coordinates locally inside your browser:

• Zero backend: No server, no database, no telemetry. The PDF never leaves your machine.
• 12 layout risk checks: Scans for elements that notoriously break older ATS parsers (multi-column layouts, tables, text embedded in canvas/images, weird glyphs, and missing standard section headers).
• JD keyword matching: Computes coverage against a pasted job description, flagging missing skills and frequency gaps.
• Scoring: Produces a 0–100 score based on layout hygiene and keyword overlap.

In automated testing on two synthetic resume fixtures, it scored 91 on a standard single-column tech resume and 63 on a heavily stylized two-column designer resume, flagging the exact column-parsing and header issues expected.

Why it isn't live yet

The tool is completely built and functional, but I haven't released it. Too many side projects launch into an empty room.

Instead of deploying a paid product right away, I'm validating real demand:

• Target pricing: $19 one-time (lifetime use, offline file, no account required).
• The rule: I've put up a simple waitlist at alapha888.github.io/resume-ats-waitlist. If it gets 10+ signups before October 29, 2026, I will polish the packaging, documentation, and release it. If it doesn't hit 10, I'll shelf the project and keep it as a personal utility.

No launch date promises, no roadmap hype.

Two questions for developers and job seekers

1. What ATS check do you actually care about when applying—layout compatibility, or pure keyword density against the job description?
2. Does a $19 one-time local file make sense for someone hunting for a job every few years, or is the subscription model standard for a reason?