Kepler vs Crelate: which recruiting CRM should a boutique agency choose?

What Kepler and Crelate each are

Crelate is a long-established recruiting platform sold mainly to boutique and mid-size agencies in the United States, and as of September 2026 its home page calls it "The Strategic Recruiting Platform". It is sold in named parts: Crelate Recruit is the ATS and CRM, Crelate Hire covers onboarding and compliance, and Crelate Deliver is the optional back office for assignments, timekeeping, invoicing and payroll export. Around those sit client and team portals, a job portal, analytics, outreach and sequences, text messaging and a mobile app called Crelate Connector. Its AI is a named family: Co-Pilot for in-app chat, with Co-Screen, Co-Target, Co-Interview and Co-Create alongside it, a Discovery Agent that searches an external profile network, and an Insights Agent that continuously enriches the records you hold.

Kepler is a recruitment CRM built around one assistant and a searchable database. Rather than a family of AI features, Kepler has a single agent in a sidebar on every page with roughly fifteen tools: it reads the whole workspace — candidates, CVs, notes, emails and call transcripts — returns record sets you can save as a list, and creates or updates records once a person approves the change. Around it sit the ordinary parts of an agency desk: pipeline boards, jobs, tasks, Gmail and Outlook two-way sync, calendar and booking links, a meeting notetaker, CV parsing and formatting, a branded job board, reporting, campaigns, automations, and a public REST API with webhooks.

The two overlap on most of a recruiter's day. They diverge on two questions: where the AI should point, and how many editions a buyer should have to choose between.

The real difference: outward-facing AI versus inward-facing AI

Crelate's flagship AI capability points outward. The Discovery Agent, launched in July 2025 according to Crelate's published roadmap, searches what Crelate's home page describes as a database of up to 1 billion people and 20 million companies, using natural language rather than Boolean strings. The Insights Agent points outward too, in a different sense: Crelate's home page states that "Records stay fresh automatically as candidates change roles, skills, and contact details." The bet is that the most valuable thing AI can do for a recruiter is bring in people and facts the agency does not already have.

Kepler's assistant points inward. It has no sourcing database of its own — Kepler does not sell access to a pool of candidate profiles, and an agency that buys a CRM partly to source will find that a real gap. What Kepler's assistant does instead is read what the agency already owns: the CVs it parsed years ago, the notes a consultant typed in 2021, the email threads synced from Gmail and Outlook, and the transcripts of recorded calls. Retrieval is hybrid — semantic and keyword together — so a question phrased the way a person would phrase it reaches a CV that used different words.

Neither bet is wrong; they suit different agencies. The honest test is whether your last ten placements came from people you already knew or people you had to go and find. If it is the latter, Crelate's Discovery Agent does something Kepler cannot. If it is the former, the value is in the database you already have, which is what Kepler is built to read.

How each one searches and ranks candidates

Crelate's search over your own database is a full-text Boolean query. Crelate's help centre documents a keyword search across a candidate's résumé and notes with AND, OR, quotation marks and parentheses, and describes results scored by Elasticsearch on how closely each record matches the keywords. Crelate is not defensive about this: a post on the Crelate blog dated 14 August 2026 argues for keeping Boolean as the substrate — "Boolean is literal matching, and literal has value" — while moving it underneath an agent that writes the query. That is a coherent position with a real advantage, because a Boolean query can be shown to a regulator.

Kepler's search is hybrid semantic and keyword retrieval, and the difference that matters most is the corpus rather than the method. Crelate's documented search reads résumé text, notes and tags; Kepler's reads those plus the email threads and call transcripts attached to a record. A candidate who mentioned on a screening call that they will not relocate is findable in Kepler and is not findable by a keyword search of a CV in any product, including this one.

On ranking a shortlist for a specific job, the two do different things. Crelate ranks records by search relevance and then helps you read them: Co-Screen produces a résumé summary from a recruiter's perspective once you are looking at a person. Kepler scores every candidate in the eligible pool against criteria written for that job, and shows a verdict on each requirement with the line from the record that supports it, so a consultant who disagrees with the order can see what the system actually read. Kepler measures that ranker internally against a standing evaluation set before a change to it ships, and does not publish the figures, so this post quotes none. Crelate publishes no evaluation of its own ranking either, which is normal for the category rather than a criticism.

Where Crelate is the better product

This is the honest half and it is not short. Crelate is ahead of Kepler in at least six places, and the first of them is the largest single gap in Kepler's product.

• The back office. Crelate Deliver runs assignments, timekeeping, invoicing and payroll export inside the same platform the recruiters use, aimed at firms with lighter contractor volume and simpler pay and bill; Crelate names People 2.0, Bilflo, Ascen, FoxHire and GorillaWorks as partners for firms that outgrow it, and its roadmap lists embedded payroll, pay stubs, a Xero integration and billable-item import as coming next. Kepler has no timesheets, no invoicing, no payroll and no back office at all. If you place contractors and want pay and bill in the same system as the pipeline, Crelate is the right choice and nothing later in this post changes that.
• An external sourcing pool. Crelate's Discovery Agent searches what Crelate describes as up to 1 billion people and 20 million companies. Kepler sells no candidate database, so an agency expecting its CRM to be a source of new names is buying a different category of product from Kepler.
• Text messaging and a mobile app. Crelate lets recruiters text contacts from inside Crelate and from Crelate Connector, its iOS and Android app, with messages syncing between the two. Kepler has no SMS anywhere — its WhatsApp support is one-off sends plus templates — and no native mobile app; the web app is responsive and that is all.
• Telephony and a client portal. Crelate integrates VoIP providers including RingCentral and Zoom for click-to-call and call logging, and sells client and team portals from its Business tier. Kepler integrates no diallers and has no client-facing portal where a client comments on or rates a shortlist.
• A certification route. Crelate's pricing page lists ISO/SOC 2 compliance, advanced auditing and IP filters among the enterprise options on its Platform tier. Kepler holds no ISO 27001 certification and no SOC 2. If your clients run vendor security reviews that require a certification, that is a straightforward reason to choose Crelate today, and it is better heard here than in procurement.

Where Kepler is the better product

Four areas, and they cluster around trusting and using the database you already have rather than adding another module beside it.

• One assistant across everything. Crelate's Co-Pilot is a chat assistant whose available Skills vary with the area of the app you are in and the data on the screen, which is a sensible design for a large product. Kepler's assistant is one sidebar on every page with roughly fifteen tools and the whole workspace in scope; it returns record sets rather than text, can save a result as a list, and creates or updates records after a person approves the change.
• Provenance and reversibility. Kepler keeps history at the level of the individual field on every plan, records the source of every AI-suggested change, and supports undo with a conflict check. Crelate's audit log is a report, and its advanced auditing — the version showing changed fields on updated records — is documented as a Business Plus and Enterprise feature. Crelate's help centre also notes that undoing a spreadsheet import removes the records the import created but does not revert records it updated. Kepler additionally uses optimistic concurrency, so when two consultants edit the same record the stale write is refused rather than silently applied.
• Proposed rather than applied. Both products keep profiles current, from different directions. Crelate's Insights Agent enriches records automatically from outside data as people change roles and contact details. Kepler reads the emails, calls and messages already attached to a record and turns them into proposed field updates and tasks, with the message they came from attached, which a person accepts or rejects before anything is written. One precision: Kepler does not draft email replies and does not summarise email threads. It proposes field changes and tasks, and it writes summaries of meetings and calls, which is a different thing.
• The careers site. Kepler publishes jobs to your own domain, server-rendered and indexable, with structured data per role. Crelate's job portal is hosted at jobs.crelate.com/portal/ plus your organisation name and embedded in your site with a widget or an iframe, so search authority accrues to the vendor's domain rather than yours.

How much does Crelate cost, and how much does Kepler cost?

Crelate publishes four tiers, read on 6 September 2026: Essentials at "$85 Per user/month, paid annually", capped at up to 2 users and 20,000 contacts; Business at "$119 Per user/month", the first tier with the AI Assistant; Business Plus at "Custom Per user, paid annually", which is where automation and sequences, business-development workflows and the full API sit; and Platform, a custom user or site licence. Crelate publishes no figure for the top two tiers, so this post quotes none.

Kepler publishes one price: USD 119 per user per month billed annually, which is USD 1,428 per seat per year. One edition, every feature included, no tier above it and no feature gating. Records and storage are unlimited, migration is free on every plan, a monthly AI allowance is included, and additional AI capacity is available on request.

For a two-person firm that wants an ATS and nothing else, Crelate Essentials buys a real product. For a growing agency that wants an assistant, sequences and an API, the Crelate configuration is Business Plus, which is priced on request, and the comparison becomes one published number against a quote.

Which one is right for your agency?

Choose Crelate if you place contractors and want timesheets, invoicing and pay-and-bill inside the same system as your pipeline; if you expect your CRM to source new candidates from an external pool; if texting candidates or a native mobile app is central to how your desk works; if you want click-to-call or a client-facing portal; or if a client's security review requires ISO 27001 or SOC 2. Crelate ships all of that today and Kepler ships none of it.

Choose Kepler if your main asset is a database you cannot currently search — years of CVs, consultant notes, email threads and call transcripts a keyword query does not reach; if you want one assistant that answers across all of it and can then act on the answer with your approval; if you need to explain to a client why a candidate ranked where they did; if you would rather automatic profile updates arrived as proposals than as silent edits; or if you would rather pay one published price with everything switched on than work out which of four tiers holds the feature you were shown in the demo.

Bluntly: Crelate is the better choice for an agency that wants more of the staffing lifecycle — including the money — inside one system. Kepler is the better choice for an agency that thinks its problem is not the lifecycle but the database underneath it.

Can Kepler replace Crelate if we run timesheets and invoicing?

No, not on its own. Kepler has no timesheets, no invoicing, no payroll and no back office, and there is no version of Kepler that does; Crelate Deliver exists precisely for the firms that need them.

The only honest alternative Kepler offers is integration rather than replacement. Kepler's public REST API and outbound webhooks are included in the single price rather than gated to a higher tier, so a separate pay-and-bill or umbrella system can be driven from Kepler placements — the arrangement many agencies already run, and the reason Crelate itself names People 2.0, Bilflo and GorillaWorks as partners. But an agency that wants pay and bill inside the CRM should not buy Kepler.

Can you migrate from Crelate to Kepler?

Yes, and Kepler runs the migration for you free on every plan rather than quoting it as a project. You send an export from Crelate plus any loose CVs, spreadsheets and shared-inbox archives that never made it into the CRM. Kepler handles 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 alongside the records themselves.

The parsing engine doing that work is not new. Kepler's CV parsing and formatting are ported from RemakeCV, which is Kepler's own product and which 300+ recruitment agencies use. That is not third-party validation of Kepler — same team, same code — but it does mean the engine reading your export has been reading real agency CVs for years rather than being written for a launch. Kepler also exports the entire workspace on request at any time with no exit fee, which is the same courtesy in reverse.