Ezekia is built for retained executive search. Kepler is built around the database underneath it.

Ezekia models the search assignment end to end — a client portal, off-limits flags, organisation charts, retainer billing. Kepler does none of that. What Kepler does is make everything you already own searchable in plain English, including the email threads and call notes sitting on each record, and show its working when it ranks someone against a brief.

The short answer

If your firm runs retained executive search and the assignment is the unit of work, Ezekia is very likely the better product and this page will not pretend otherwise: Ezekia ships a client-facing portal, off-limits flags, organisation charts, GDPR consent records and retainer invoicing with fee splits, and it holds ISO 27001 certification. Kepler has none of those. Kepler is the stronger product underneath the workflow — plain-English search across your CVs, notes and conversations, a meeting notetaker that files the full transcript on the record, matching with a verdict and a source for every requirement, per-field history with undo, and one published price of USD 119 per user per month with the migration done for you.

Choose Kepler if
Your desk is mixed — search alongside contingency, interim or in-house hiring — your real asset is years of CVs, email threads and call recordings that no keyword search reaches, and you would rather read one published price than wait for a scoped quote.
Choose Ezekia if
You run retained executive search or leadership advisory. You need a portal your client logs into to follow a shortlist, off-limits flags with an expiry date, organisation charts, consent records with a lawful basis, retainer invoicing with fee splits, or ISO 27001 for a client security review. Ezekia ships all of that today, Kepler ships none of it, and no amount of AI makes up the difference. Buy Ezekia.

Last checked 6 Sep 2026 · Written from Ezekia's own public documentation and pricing pages. Tell us if we have something wrong and we will correct it.

01

Search reads the conversations too

Kepler’s plain-English search is semantic and keyword together across candidates, CVs, notes and conversations — the email threads and call notes attached to a record, not only its structured fields. The notetaker joins the call and files the summary, the next steps and the full transcript against the right record, so what someone actually said is in the corpus rather than in a folder.

02

A verdict for every requirement

Kepler ranks your database against a job and shows a verdict and the supporting evidence for each criterion, rather than a single number. Criteria are per-job and editable, so when the brief changes you edit the brief and re-run it.

03

One published price

Kepler is USD 119 per user per month billed annually — USD 1,428 per seat per year — with every feature included, unlimited records and storage, and migration done for you on every plan. Ezekia does not publish pricing; its plans are scoped and quoted individually.

Side by side

Where Kepler is the stronger of the two.

These are the dimensions Kepler wins. Ezekia is ahead of Kepler on most of what a retained search firm buys a platform for — the client portal, off-limits handling, organisation charts, consent records, retainer billing and ISO 27001 — and the blog post lists every one of them in full.

Kepler compared with Ezekia
Kepler Ezekia
Asking your own database a question
What plain-English search readsThe corpus, not the ranking. Candidates, CVs, notes and conversations — semantic and keyword retrieval together Vector search and Query Builder over Ezekia records, with Microsoft 365 mail, files and chats through Sidekick connectors
Recorded calls and meeting notesWhether the transcript is in the product or in another subscription. A notetaker joins the call and files the summary, next steps and full transcript on the record Integrates third-party AI notetakers — Metaview, Carv, CoRecruit and HireLogic — plus voice transcripts on researcher notes
Approval before anything is writtenWhat happens when the AI decides to act. The assistant creates and updates records only after a person approves the change; runs can be paused and resumed AI automations trigger an agent from an event, and an MCP server lets Claude or ChatGPT update records and progress assignments
Matching a person to a brief
Evidence for each requirementWhether a consultant can see why someone ranked where they did. A verdict per criterion — met, partial, missing or not stated — with the line from the profile it rests on Job-spec matching and semantic search with must-have, important and exclude filters; per-criterion evidence is not described in their published material
Where the criteria liveA brief that survives the search that produced it. Criteria sit on the job, stay editable, and the shortlist re-runs against them Search parameters refined per search and saved as Query Builder searches
Where the CV parsing comes fromWhether the engine has read real agency CVs before. RemakeCV’s engine — our own product, which 300+ recruitment agencies use — used for bulk drops and old-system exports A choice of traditional or AI parsing at import, with AI producing more natural-sounding summaries
Trusting what is on the record
Field-level historyWhat changed, who changed it, and from what. Per-cell history with the source of every AI-suggested change, and undo A Journal View gives a unified activity timeline per record; per-field history and undo are not described in their published material
Two people, one recordThe quiet data-loss bug in most CRMs. Optimistic concurrency, so a stale edit is refused rather than silently applied Not described in Ezekia’s published material
Keeping a profile currentApplied, or proposed for review? Emails, calls and messages become proposed field updates and tasks that a person approves or rejects Outlook emails, meetings, contacts and tasks sync automatically, and machine learning augments incomplete data
The rest of the desk
Which mailbox it connects toNot every search firm runs on Microsoft. Gmail and Outlook two-way sync, with threads linked to the right record Microsoft 365 and Outlook throughout; Google Workspace is not named in their published material
Your own careers siteFor the leadership-advisory and in-house half of the market. A branded job board on your own domain, SEO-indexed, with applicants parsed and scored on arrival No careers site or job board appears in Ezekia’s published feature list
Seeing what runs by itselfAutomation you can audit rather than discover. A register of every automation — what it reads, what it writes, when it last ran, and a switch to turn it off AI automations triggered from events, plus Zapier and Integrately for everything else
Getting in and paying
Published priceWhether you can budget before a sales call. USD 119 per user / month billed annually, printed on the website Does not publish pricing — a 30-day free trial at £0, then an Enterprise plan scoped and quoted individually
Records and storageWhat happens as the database grows. Unlimited records and storage, with no per-record or per-contact charge Not published; plans are scoped per firm
MigrationWho does the unglamorous half. Done for you and free on every plan — extraction, mapping, de-duplication, and fifty of your own records to check before the full load Migration services with free onboarding and training, scoped as part of the quote
What Kepler does better

Ask the whole database, then act on the answer.

Kepler’s assistant is a sidebar on every page with roughly fifteen tools. It searches candidates, CVs, notes and conversations, ranks a shortlist against a job, answers questions about your desk, explains where any fact on a record came from, and drafts messages — and it writes nothing until you approve it.

Active data engineers in London who have used Kafka in production, available within a month

Found 4 candidates. Three mention Kafka on their CV; one said it on a recorded call last week.

4 candidates
Search results with the source of each match.
CandidateCurrent employerNoticeWhy it matched
Sophia BennettMonarch Analytics1 monthKafka streaming for card transactions at Halcyon CV
Amir HassanNorthwind Capital2 weeksKafka feed for the risk platform CV
James OkaforJuniper Systems3 monthsRebuilt the Kafka clickstream pipeline CV
Oliver ChenNorthwind CapitalImmediateMentioned running Kafka on the 2 Sep call Call note · 2 Sep
The longlist, and why

A verdict on every requirement, with the line it rests on.

Ezekia matches against a job spec with must-have, important and exclude filters, and returns candidates ranked by relevance. Kepler returns the same ranked list and then opens under any row into the reasoning: for each criterion on the brief, whether it is met, partial, missing or not stated, and the sentence from the profile that decided it.

Senior Data EngineerNorthwind Capital · London · Open
Criteria · 4 Re-run
Example matches for a Senior Data Engineer brief. Select a row to read its evidence.
CandidateMatchRole titleCurrent employerSkills
Sophia Bennett92StrongSenior Data EngineerMonarch AnalyticsPython, Spark, AWS, Terraform, dbt
Amir Hassan81GoodData EngineerNorthwind CapitalPython, Spark, EMR, SQL, Airflow
James Okafor74GoodSenior Data EngineerJuniper SystemsSpark, Azure, Databricks, Kafka, Scala
Mei Tan68WeakEngineering Manager, DataAtlas CloudAWS, Leadership, Python, Snowflake
Elena Rossi55WeakAnalytics EngineerFormadbt, SQL, Python, Looker
Oliver Chen49Off specPlatform EngineerNorthwind CapitalAWS, Kubernetes, Terraform, Go

Sophia Bennett

1 of 6

Assessment

A strong fit for the brief. Sophia has run a production Spark platform on AWS and has managed a team through a migration. Financial services exposure is via a payments client rather than a bank.

EmployerMonarch AnalyticsLocationLondonStatusScreeningLatest degreeMSc Computer ScienceEmailsophia.bennett@monarch.exampleProfile

Criteria · 3 of 4

  • Financial services“Two years on a payments client; no bank or fund experience stated.”
  • Python & Spark in productionmust“Built the ingestion platform in Python and Spark, processing 40 TB a day.”
  • AWS data platform“Ran the platform on AWS: Glue, Redshift and S3, with Terraform.”
  • Led a team“Managed four engineers across two squads through the warehouse migration.”

Decision

↑ ↓ next candidate · Esc close

Proposed, not applied

A conversation changes a record. A person still signs it off.

A start date in an email, a resignation over WhatsApp, a salary on a recorded call. Kepler reads them and proposes the change on the field, with the message it came from attached, and you accept or reject it. Every field keeps its own history, so you can see what a value was before and put it back.

Three candidates · this week

Sophia Bennettto me
Today, 09:12

Re: Senior Data Engineer at Northwind

Thanks for sending the details over. The role sounds great, and I can start on 3 October if the timing works for them.

Amir Hassanonline
WhatsApp

Are you still keeping half an eye out?

10:41

I handed my notice in this morning, so I am actively looking now.

10:46
Catch-up call · 14 minJames Okafor · Today, 11:20
Zoom

James · 11:26For my next move I am looking for £105,000. I would want a step up for a move.

ListsData engineers · London Assistant
All candidates Search candidates... Filter Sort Import / Export
Example candidate records. Three cells carry an AI suggested update from the conversations beside them.
CandidateAvailable fromStatusExpected salaryNotice periodCompanyOwnerSkills
Sophia BennettNot setPassive£90,0001 monthMonarch AnalyticsPriya NairPythonSparkAWS+1
Amir Hassan14 Oct 2026Passive£85,0002 weeksNorthwind CapitalPriya NairPythonEMRSQL
James OkaforImmediateNew£100,0003 monthsJuniper SystemsTom ReillySparkAzureKafka+1
Mei TanNot setPassiveS$160,0002 monthsAtlas CloudTom ReillyAWSLeadership
Elena RossiNot setActive€78,0001 monthFormaTom ReillydbtSQLPython+1
Oliver ChenImmediateNew£88,000NoneNorthwind CapitalPriya NairAWSKubernetesTerraform+1
Rahul Menon2 Nov 2026Active£92,0001 monthJuniper SystemsPriya NairPythonAirflowSnowflake
Yuki TanakaNot setPassive¥14,000,0003 monthsAtlas CloudTom ReillyScalaKafkaGCP
Hafiz Rahman20 Oct 2026ActiveS$145,0002 weeksMeridian PartnersPriya NairSQLdbtLooker
Clara NowakNot setNew€84,0001 monthFormaTom ReillyPythonDatabricksSpark+1
Daniel OkonkwoImmediateActive£78,000NoneNorthwind CapitalPriya NairSQLFivetran
Ana Ferreira8 Dec 2026Passive€96,0003 monthsJuniper SystemsTom ReillySparkAWSTerraform
Tomas NovakNot setActive€71,0001 monthMonarch AnalyticsPriya NairPythonSQLAirflow
Grace Adeyemi27 Oct 2026Active£105,0002 weeksAtlas CloudTom ReillyLeadershipAWSKafka+1
Ivan PetrovNot setPassive€88,0002 monthsFormaPriya NairGoKubernetesGCP
Leila HaddadImmediateNew£82,000NoneMeridian PartnersTom ReillyPythondbtBigQuery
Marcus Reid16 Nov 2026Active£98,0001 monthMonarch AnalyticsPriya NairSparkDatabricksAzure
Nadia KaurNot setPassiveS$172,0003 monthsNorthwind CapitalTom ReillyLeadershipPythonSQL
Where the engine comes from

Not a first attempt at parsing CVs.

Kepler's CV parsing and formatting are ported from RemakeCV, our own product, which 300+ recruitment agencies use. The migration that fills your database on day one runs on an engine that has been reading real agency CVs for years, not on something written for this launch.

RemakeCV is a Kepler product. It is the same team and the same code, which is why we are willing to point at it — and it is the only outside evidence on this page, because Kepler itself is new and has no customer stories yet.

Migration

Get migrated in days.
We handle the whole move.

  1. 1. Send us the export

    Whatever your current system gives you, plus any loose CVs and spreadsheets sitting in folders. If you are not sure how to get the export out, we will walk you through it.

  2. 2. We build the migration

    Extraction, mapping, de-duplication and validation — the unglamorous half most vendors leave on your desk. Your custom fields are recreated rather than flattened into notes.

  3. 3. You look at a sample

    Fifty of your own records, fully parsed — your people, not a demo set. Tell us what we got wrong and we fix it and re-run, as many times as it takes.

  4. 4. Everything loads

    The full database goes in, mailboxes and calendars connect, and history backfills onto the right records. We stay on it until your team is working in Kepler.

Pricing

What each one costs.

Kepler

£89 per user / month, billed annually

  • Every feature included — there is no edition above this one
  • Unlimited records and storage
  • Migration done for you, on every plan
  • Monthly AI allowance included; more capacity available on request

Ezekia

Does not publish pricing

Ezekia’s pricing page, checked 6 September 2026, lists a 30-day free trial at £0 with dedicated onboarding support, and one paid tier shown as CUSTOM — “Per user. Monthly. No annual commitment”. Alongside it Ezekia states “No fixed plans. No per-search fees. No hidden charges” and “All plans are scoped and quoted individually”. There is no published seat price, so there is none printed here; any figure you see for Ezekia on a review-aggregator site did not come from Ezekia.

Their model has a real advantage over ours and it is worth saying: Ezekia sells monthly with no lock-in, so a firm that wants to leave in month three can. Kepler’s published USD 119 is billed annually, with a USD 149 monthly option. What Kepler gives back is that you can work out your bill without a sales call, and that there is no edition above the one you bought.

Questions, answered.

Is Kepler or Ezekia better for an executive search firm?

For a firm doing retained executive search, Ezekia is very likely the better fit, and Kepler would rather say so here than in a demo. Ezekia is purpose-built for the assignment: it models Lists, Opportunities and Assignments as distinct project types, ships a client-facing portal, off-limits flags with time limits and notes, organisation charts and relationship diagrams, GDPR consent management, and billing with fee splits and multi-currency invoicing. Kepler has none of those. Kepler is the stronger product on the layer underneath — plain-English search across CVs, notes and conversations, matching with per-criterion evidence, per-field history with undo, and one published price — which matters most to a firm whose desk is mixed rather than purely retained.

Does Ezekia publish its pricing?

No. As of 6 September 2026, Ezekia’s pricing page shows a 30-day free trial at £0 and a single paid tier listed as CUSTOM, described as “Per user. Monthly. No annual commitment”, with the note that “All plans are scoped and quoted individually”. Ezekia publishes no seat price, so a comparison cannot honestly print one. Kepler publishes USD 119 per user per month billed annually — USD 1,428 per seat per year — with every feature included, unlimited records and storage, free migration, and additional AI capacity on request.

Does Kepler have a client portal like Ezekia’s?

No. Ezekia ships a client portal where a client sees candidate shortlists, reports, interview feedback, project updates and search activity in real time, with the firm controlling exactly which candidates, documents, custom fields and confidential project details are visible, and the ability to archive a portal when the search closes. Kepler has no client-facing portal at all. If your clients expect to log in and follow a search, that alone should decide this comparison in Ezekia’s favour.

What does Kepler’s search read that a normal CRM search does not?

Kepler’s search is hybrid semantic and keyword retrieval across candidates, CVs, notes and conversations rather than structured fields alone, so a plain-English question can surface someone because of a line in a CV, a researcher’s note, an email thread or something said on a recorded call. Kepler’s notetaker joins the call and files the summary, the next steps and the full transcript against the right record, which is what puts spoken conversation into that corpus in the first place. Ezekia offers vector search and a Query Builder over its own records, and its Sidekick connectors reach Microsoft 365 mail, files, chats and calendars; call transcription in Ezekia comes from a connected notetaker such as Metaview, Carv, CoRecruit or HireLogic.

Does Ezekia work with Gmail, or only Microsoft 365?

Ezekia’s integration and MS 365 pages describe Microsoft throughout — Outlook, Teams, OneDrive, Excel, SharePoint, Microsoft To-Do, Power BI and Copilot — and synchronise emails, meetings, contacts, tasks and calendars between Outlook and Ezekia. Google Workspace is not named anywhere in Ezekia’s published material as of 6 September 2026. Kepler syncs two-way with both Gmail and Outlook, with threads linked to the right record, and also does calendar and scheduling with booking links. If your firm runs on Google, check that point with Ezekia directly before you shortlist either product.

Is Kepler ISO 27001 certified like Ezekia?

No. Ezekia states it is certified to ISO 27001:2022 and publishes its certificate number on its own site. Kepler holds no ISO 27001 certification and no SOC 2 report. For a search firm whose clients run vendor security reviews — which in executive search is most of them — that is a straightforward reason to choose Ezekia, and it is not something product depth compensates for.

How hard is it to move from Ezekia to Kepler?

Kepler runs the migration for you, free, on every plan. You send an export from Ezekia along with any loose CVs, spreadsheets and shared-inbox archives that never made it into the system; Kepler handles the extraction, mapping, de-duplication and validation, and rebuilds your custom fields as real fields rather than flattening them into notes. Before the full load you review fifty of your own records fully parsed — your people, not a demo set — and anything wrong is corrected and re-run. Activity, stages and history come across, not just names and email addresses. Kepler also exports your whole workspace on request at any time with no exit fee.

See it run on your own database.

Bring your hardest search to a 15-minute call. We will run it live, on real records, and talk through what a migration would look like.