Where it can source. When it can call.
And what one seat is allowed to spend.
Recruiting touches licence numbers, salaries and personal phone numbers. Kandidate bounds all of it at organisation level and enforces the boundary at search, enrichment and contact rather than only the first. Every action is logged and replayable.
Can I stop it sourcing outside my market?
Yes, at organisation level, and it holds at all three points that matter: search, enrichment and contact. A candidate outside your permitted regions isn't quietly filtered from a list; the platform won't enrich them or message them either.
Can a junior burn through our credits?
Not if you cap them. Every seat can carry a hard spend limit per provider, drawn from the organisation's pool, and the pool is always the ceiling. Enforcing a seat can never let the organisation overspend. You can set limits for visibility only, or make them binding.
What keeps us the right side of the rules?
AI disclosure on every call, opt-outs honoured across the whole organisation and enforced before a message is even drafted, calling windows in the candidate's own timezone, and carrier attestation on outbound numbers. None of these are switches — they're the floor.
An opt-out applies to every job in your organisation, permanently, and is checked before a draft is written, not filtered at send time.
Click through it yourself.
A guided walkthrough of the real screens. No signup, no sales call: follow the prompts, or skip ahead with the dots.
Control
And what one seat is allowed to spend.
3 steps · about a minuteEverything else buyers ask
Can I control who on my team sees what?
Partly, today. Honestly, not enough. Right now there are two roles, admin and recruiter, plus a separate client-portal permission. Granular roles are in build: six prebuilt roles over a permission registry, so a junior sourcer can work a pipeline without seeing offer terms or your integration credentials. This page will say so plainly until it ships.
Where is candidate data held?
In your organisation's partition, scoped on every read. Cross-organisation access is blocked at the data layer, not in the interface.
Do you train models on our candidates?
No.
Can we get an audit trail out?
Yes. Actions are logged with actor, time and outcome, and are exportable.
Is SSO available?
Google sign-in today. SAML for Okta and Entra is a short piece of work we'll do on request. Tell us on the pilot call.
When do granular roles land?
In build now. This page is written and will publish the roles section the day it ships. We haven't listed it as done.
Explore more features
See what else the engine does across the desk.
See it on one of your own roles.
A one-month pilot runs on two real roles from your desk. The fee credits 100% toward month one, so the trial costs you nothing if you continue.