What Alphie reads

• Your open jobs and their requirements, so shortlists are scoped per role.
• Candidates and their attached CVs, including everyone who applied to older roles.
• Application status and pipeline stage, so it never re-contacts someone mid-process.
• Existing notes and scorecards, so it doesn't repeat a screen your team already ran.

What Alphie writes back

• A ranked shortlist of the five strongest fits for each open role.
• A screening report per candidate after a 15-minute voice interview, attached to their record.
• Stage and status updates as candidates move, so your pipeline stays accurate.
• A record of the approval or rejection email that was sent.

Greenhouse vs Ashby: what differs

Functionally, very little from your side — both are API-first systems with full coverage of jobs, candidates, applications and scheduling, which is exactly what Alphie needs.

• Greenhouse. Access runs through Harvest API credentials scoped by permission. Structured stages and scorecards mean Alphie's screening reports slot straight into the review workflow your interviewers already use.
• Ashby. Access runs through an API key on your workspace. Ashby's richer candidate search means Alphie can be more surgical when mining an older applicant pool for a newly opened role.

On both, credentials are scoped to only what the automation needs — read the pipeline, write back results — and can be revoked from your side at any time.

What your recruiters actually change

Nothing about where they work. They open Greenhouse or Ashby as usual and find a shortlist waiting, each candidate with a screening report attached and interviews already on the calendar. The work that disappears is CV triage, first-call scheduling and the reply backlog. Every hiring decision stays with your team.

Data, security and control

Your ATS remains the system of record. Data Alphie handles — including interview recordings and reports — is stored on encrypted servers, processed and stored in the EU only, covered by a signed Data Processing Agreement, and never shared outside your company or added to any shared candidate pool. Every API call Alphie makes into your instance is audit-logged.

If your policy is that candidate data must never rest on a vendor's servers, a zero-storage, in-memory-only architecture can be scoped as a separate enterprise engagement.

Setup and pricing

One 30-minute onboarding call to scope the connection and the roles it covers, then the integration is built against your instance. Any ATS with a documented API can be supported — Greenhouse and Ashby are the two we integrate with most often. Commercially: a one-off setup fee plus a monthly subscription scoped to hiring volume. No per-seat charges, no listing limits.

Common questions