Kepler Features
Bring 40,000 CVs.
Search them on day one.
The same parser 300+ agencies already run. Migration handled by us, free on every plan.
Inside Kepler
How it works.
Every CV becomes fields
Parsing isn't an import filter bolted onto Kepler — it's the RemakeCV engine, reading every document the way it did for millions of CVs before yours. Scans, jumbled layouts and two-column PDFs included.
Mar 2023 → present3 yrs 2 mos
Handles the ugly ones
Scans, jumbled layouts, two-column PDFs — OCR fallback included. Tenure is even computed from the dates rather than left for you to work out.
Supersedes the value set in June 2025 · nothing writes until you accept
You review before it writes
A new CV on an existing record arrives as a diff against what's there now — accept or reject line by line, never a silent overwrite.
The original stays
Fields are extracted, but the document clients actually ask for stays on the record — send the CV itself, not a re-typed summary.
The archive you already own
Everything you've collected goes through the engine before your team logs in — duplicates collapse on the way in, your own attributes fill themselves, and our team runs the migration until go-live.
Duplicates collapse on the way in
The same person in three exports arrives as one record — the fullest version of each field kept, the rest shown to you struck through.
Custom attributes autofilled
Day rate, clearance, right to work — the fields your market actually runs on are pulled out of the documents, not left blank for someone to chase.
You send the export from your current ATS. Any format, any state.
Every source field mapped to Kepler and reviewed with you before anything moves.
Your archive runs through the parser in a migration environment; results validated with your team.
Final review together, then switch-over with no downtime. Free on every plan.
We do the migration
Send the export; we map, validate and stay on it until go-live. You're never handed a CSV and wished luck.
A team you already know
Built by the team
behind RemakeCV.
Kepler comes from the makers of RemakeCV, the CV parsing and formatting platform agencies have run for years. These numbers belong to that engine.
- 300+ agencies supported. The engine reading your CVs in Kepler is the same one RemakeCV already runs for 300+ recruitment agencies.
- Thousands of recruiters daily. This parser works live desks all day, every day — it isn't a demo model built for this page.
- Millions of CVs processed. Scans, ancient formats, jumbled two-column layouts — most of what your archive throws at it has been seen before.
- Migration handled by us, free on every plan. You send the export from your current ATS; we handle extraction, mapping and validation until go-live.
Questions,
answered
What agencies ask before handing over an archive they spent a decade building.
How good is the CV parser?
It is the RemakeCV engine, which already runs for 300+ recruitment agencies across millions of CVs. Scans, jumbled layouts and two-column PDFs are handled, OCR fallback included, and tenure is computed from the dates rather than left for you to work out.
What happens when a new CV lands on a candidate who already exists?
It arrives as a diff against what is on the record now — accept or reject line by line. Never a silent overwrite. The original document stays on the record too, so you can send the CV itself rather than a re-typed summary.
Do you charge to migrate from my current ATS?
No. Migration is free on every plan. You send the export and we handle extraction, mapping and validation, and stay on it until go-live — you are never handed a CSV and wished luck.
Will importing my archive create duplicates?
Duplicates collapse on the way in. The same person appearing across three exports arrives as one record, with the fullest version of each field kept and the rest shown to you struck through.
Explore Kepler
Discover more features
See it run on your own database
A 20-minute call. We load a slice of your data and you search it yourself — no slide deck, no pretend company.