May 22, 2026
Greenhouse vs Lever vs Ashby: Which ATS Fits AI-Era Hiring (2026)
Greenhouse vs Lever vs Ashby for AI-era hiring: API openness, MCP, native AI, and pricing compared. See which ATS fits your team and what AI layer to add.
Every greenhouse vs lever vs ashby comparison ranks the same three things — features, UI, price. That was the right scoreboard in 2021. In 2026 it misses the decision that actually matters.
The job that breaks an ATS now is AI throughput, not record-keeping. Greenhouse's own data puts applications per recruiter up 412% since 2023, while fewer than 7% of applicants receive an interview. Volume like that doesn't get solved by a tidier pipeline view. It gets solved — or not — by what AI tooling your ATS can safely run.
So this is a genuinely neutral three-way read. No vendor wrote it, and it judges Greenhouse, Lever, and Ashby on the criteria the comparison pages skip: API openness, MCP support, native-AI maturity, and what you can layer on top without ripping out your system of record. We'll cover the three platforms at a glance, then API and MCP, native AI, pricing and fit, the candidate-trust crisis driving all of it, and why the smart 2026 move is compose, not replace.
Greenhouse vs Lever vs Ashby: who each ATS is actually for
These three platforms are not three flavors of the same thing. They were built for different buyers, and the AI-era pivot has sharpened the differences rather than blurred them.
Greenhouse is the structured-hiring incumbent. 7,500+ customers including HubSpot, Anthropic, and Coinbase, and it was ranked the #1 ATS in G2's Winter 2026 reports. Its strengths are compliance, global scale, and a deep integration marketplace — the things a 1,000-person company with a real RecOps function actually needs.
Lever is the candidate-experience and CRM hybrid. It has been owned by Employ Inc. since August 2022, alongside JazzHR and Jobvite, and installed a new CEO and CTO in February 2026 with an explicit AI-acceleration mandate. The honest caveat in the lever vs greenhouse matchup: users report slower releases and renewal price increases since the acquisition. Lever still suits relationship-driven, high-touch talent teams that nurture pipelines over months.
Ashby is the analytics-first, AI-native challenger. Founded in 2019, it reports 2,700+ customers and 135% YoY revenue growth, with $128M raised across four rounds. Its enterprise base is thinner — far fewer reviewers come from 1,000+ employee orgs than Greenhouse's — but it ships AI features faster than anyone here.
| Platform | Customers | G2 score | Best for |
|---|---|---|---|
| Greenhouse | 7,500+ | 4.4 / 5 (3,759 reviews) | Compliance-heavy scale-ups and enterprise |
| Lever | mid-market base | 4.3 / 5 (2,102 reviews) | Relationship-driven, high-touch TA teams |
| Ashby | 2,700+ | 4.7 / 5 (~100 reviews) | Analytics-led teams that want native AI early |
One note on that table: Ashby's 4.7 sits on roughly 100 reviews, against thousands for the other two. Treat it as a strong early signal, not a settled verdict.
API openness and MCP — the 2026 buying criterion nobody ranks
Here is the structural gap in every greenhouse vs lever vs ashby article on the SERP: not one of them weighs API openness as a decision factor. They rank what the ATS does. They never ask what you can build on it.
That question is now the one that matters. In May 2026, both Greenhouse and Ashby shipped MCP servers — a governed connection layer that lets external AI tools and agents act inside the ATS with permissions and audit trails intact. Lever has not. That is a concrete, datable differentiator, and it changes the calculus more than any feature on a comparison chart.
Why it matters: 30% of job seekers already use AI agents to search, apply, and schedule. Both sides of the hiring market are going agentic. An ATS without a governed agent layer forces you to choose between brittle scraping integrations and no AI extension at all.
There's also a migration deadline to plan around. Greenhouse's Harvest API v3 becomes mandatory on August 31, 2026 — if you run custom integrations against an older version, that work is already on your roadmap whether you've scheduled it or not.
The framing worth owning: don't just ask what the ATS does — ask what you can safely build on top of it. That seam is exactly where how imast layers on top of your ATS lives. An ATS with an open API and an MCP server lets a specialist AI agent plug in cleanly; one without forces a worse trade-off. Score all three platforms on this, not just the feature list.
Native AI features compared — and a maturity reality check
Every vendor here now markets native AI. The honest question is how much of it has actually shipped.
Greenhouse acquired Ezra AI Labs for voice interviewing, framing it as structured-hiring rigor pushed to the front of the funnel. The catch: the deal closes in Q2 2026 — as of this writing it is a definitive agreement, not a shipped product.
Ashby is furthest along, with 15+ native AI features live, from AI Talent Rediscovery to AI-assisted review, and a reported 46% lift in reply rate from AI personalization in outreach. But its headline AI Interviewer, built on the acquired Talent Llama, is still in private beta.
Lever ships "AI Companions" — an Interview Companion (formerly Pillar) credited with a 32% drop in first-year attrition in vendor-reported data, and Talent Fit matching built on IBM watsonx.governance. Its Sourcing Companion is still listed as "upcoming."
Read that honestly: native ATS AI in 2026 is assistive, ATS-bounded, and roadmap-paced. A good chunk of it is beta, unclosed, or pending. It helps a recruiter move faster inside the ATS — it does not go out and find people who never applied. That is a different job from what a dedicated AI candidate screening agent does: evaluate candidates against the criteria you set and show its reasoning per criterion, rather than surfacing a bare fit number inside a record system. Useful native AI and a specialist screening layer are not competitors. They are different layers of the stack.
Pricing and who each platform fits
Start with the uncomfortable truth: all three vendors gate full pricing behind a sales quote. Any single number you see online is a data point, not a fact — treat the figures below as ranges, not price tags.
Ashby is the most transparent of the three. It publishes a Foundations entry tier at roughly $400/month for teams under 100 employees and offers a free trial, then moves to headcount-based pricing above that. Greenhouse and Lever publish nothing. From third-party aggregators, Greenhouse lands in a rough $6,000–$25,000+/year band, and Lever around $12,000 base climbing to $18,000–$25,000 with add-ons. Those numbers are unverified by definition — the vendors won't confirm them — so use them to size a budget conversation, not to sign one.
Fit guidance, stripped of vendor spin:
- Greenhouse — compliance-heavy scale-ups and enterprise. If you need structured hiring, audit trails, and global scale, the price premium buys real maturity.
- Lever — relationship-driven, high-touch TA. If your pipeline is nurture-heavy and CRM-shaped, Lever's model fits, with the post-acquisition release pace as the open question.
- Ashby — analytics-led, fast-moving teams that want native AI early. The most transparent pricing and the fastest AI cadence, against a thinner enterprise track record.
For the ashby vs greenhouse decision specifically, pricing transparency itself is a signal: Ashby's published entry tier tells you something about how it wants to sell, and to whom.
The candidate-trust crisis driving the whole AI race
Here's the reframe the SERP avoids entirely. The AI arms race between these platforms is not a feature checkbox contest. It is a response to a trust collapse on the candidate side, and ignoring that misreads the whole comparison.
Greenhouse's research is blunt. Alongside the 412% jump in applications per recruiter, 74% of candidates now use AI in their job search, 46% report decreased trust in hiring, and only 20% believe employers use AI responsibly. Both sides are now pointing AI at each other, and the candidate side has largely stopped trusting the process.
That makes an ATS choice in 2026 partly a bet on governance. Each vendor has staked out a position: Greenhouse with its AI Principles Framework, Ashby with FairNow bias audits on its AI features, Lever with IBM watsonx.governance underneath Talent Fit. None of these is marketing fluff you can skip — they are the controls that decide whether your hiring stays defensible at volume.
Whatever ATS you land on, the responsible AI in hiring question follows you to whatever AI layer you add on top. Fair, explainable evaluation — a score you can interrogate, not just inherit — is the bar. A tool that hands you a ranking with no reasoning behind it doesn't survive an audit, and increasingly doesn't survive a candidate's questions either.
Native ATS AI vs. a dedicated AI layer — compose, don't replace
By now the line in 2026 should be clear. The ATS is the system of record. Native AI is assistive and bounded — it speeds up work happening inside that record system. A dedicated AI HR agent does something categorically different: end-to-end sourcing, screening, and outreach across the open web, reaching the people who never applied to your req at all.
Those are not the same product, and you do not have to choose one over the other. The honest recommendation, from a company that builds the AI layer: pick the ATS for its system-of-record strengths — Greenhouse for compliance and scale, Lever for relationship-led TA, Ashby for analytics and native AI — then layer a specialist AI agent on top via API or MCP. Composition, not replacement.
This is exactly where imast sits. It is not an ATS, and it does not replace one. It works above your ATS — sourcing candidates across the web, evaluating them against your criteria with visible reasoning, and drafting outreach — then hands the results back into the system of record you already trust. The open API and MCP support you screened for in section two are what make that clean instead of brittle. If you want to see it directly, see how imast sources and screens candidates.
Conclusion
There is no single winner in the greenhouse vs lever vs ashby decision, and any article that crowns one is selling something. The three takeaways:
- Pick the ATS for system-of-record strengths. Greenhouse for compliance and scale, Lever for relationship-led TA, Ashby for analytics and the fastest native-AI cadence.
- Score all three on API openness and MCP, not just features. Greenhouse and Ashby shipped MCP servers in May 2026; Lever has not. For the best ATS 2026 decision, that gap matters more than any feature chart.
- The real 2026 question isn't "which ATS" — it's "which ATS, plus what AI layer." Native AI is assistive and roadmap-paced; a dedicated agent is a different category.
If you want to see what an AI layer on top of your ATS actually does — sourcing, screening, and outreach with reasoning you can interrogate — see how imast sources and screens candidates. Bring a real req.
FAQs
Q: Is Ashby better than Greenhouse for startups? A: Often, yes. In the ashby vs greenhouse matchup, Ashby's published Foundations tier (~$400/month for teams under 100), free trial, and fast native-AI cadence fit early-stage teams well. Greenhouse's edge — deep compliance and global scale — matters more once you cross into enterprise headcount.
Q: Does Lever support MCP? A: Not as of May 2026. Greenhouse and Ashby both shipped MCP servers — a governed way to connect AI tools and agents to the ATS — while Lever has not announced one. If running AI agents against your ATS is on your roadmap, that gap belongs in your evaluation.
Q: Which ATS is cheapest? A: Pricing is the murkiest part of any greenhouse vs lever vs ashby comparison — all three gate full pricing behind sales quotes. Ashby is the most transparent, with the lowest published entry point (~$400/month under 100 employees). Greenhouse runs roughly $6,000–$25,000+/year and Lever around $12,000 base; both figures are third-party estimates the vendors won't confirm.
Q: Can I use an AI sourcing tool with any ATS? A: It depends on the ATS's API. An open API — and ideally an MCP server — lets a dedicated AI sourcing and screening agent like imast plug in cleanly and push results back into your system of record. ATS platforms without a governed connection layer make that integration brittle, which is why API openness now belongs in any ATS comparison.