--- title: "Lever vs Greenhouse (2026): A CTO's Technical Comparison" slug: lever-vs-greenhouse-2026-a-ctos-technical-comparison date: 2026-06-02 author: Raaj categories: [Greenhouse, Lever] excerpt: "A technical comparison of Lever and Greenhouse for CTOs: data models, API rate limits, pricing, compliance, and migration trade-offs." tldr: "Greenhouse wins on structured hiring, analytics depth, and compliance. Lever wins on CRM-grade candidate nurturing, UI simplicity, and lower entry cost. The data model difference drives everything." canonical: https://clonepartner.com/blog/lever-vs-greenhouse-2026-a-ctos-technical-comparison/ --- # Lever vs Greenhouse (2026): A CTO's Technical Comparison Greenhouse is built for structured evaluation — rigid stages, scorecards with per-attribute ratings, and process enforcement at scale. Lever is built for candidate relationships — a unified ATS+CRM where every interaction flows through a flexible Opportunity object. The right choice depends on whether your hiring bottleneck is **process consistency** or **pipeline velocity**. This guide breaks down the architecture, API constraints, pricing, compliance posture, and operational trade-offs that matter when you're signing a multi-year ATS contract. **One-line verdict:** Choose Greenhouse if you need defensible, structured hiring across multiple business units. Choose Lever if your competitive advantage is sourcing speed and long-term candidate nurturing. ## Overview: Lever vs Greenhouse in 2026 **Greenhouse** was founded in 2012 and positions itself as the structured hiring platform for mid-market and enterprise companies. It enforces consistent, auditable interview processes through scorecards, interview kits, and approval workflows. Its primary users are TA leaders, recruiting ops teams, and engineering hiring managers who want to standardize evaluation across hundreds of open requisitions. **Lever** brands itself as LeverTRM — Talent Relationship Management — combining ATS and CRM capabilities in a single product. Its primary users are sourcing-heavy teams at growth-stage companies that compete for talent through active outreach and need to manage passive candidate pipelines over months or years. Market positioning is straightforward: Greenhouse is structured around inbound hiring — managing applications through defined stages with scorecards and structured interview kits. Lever is structured around proactive sourcing — building candidate relationships before you have open roles, with CRM tools for nurturing passive candidates. Both platforms serve mid-market and enterprise buyers. Greenhouse is ideal for mid-size to enterprise companies (100–10,000+ employees) that hire regularly and want to build a structured, data-driven, and equitable hiring process. Lever is better suited to growth-stage companies (50–2,000 employees) where recruiting velocity and relationship management matter more than compliance depth. ## Core Architecture: The Candidate vs Opportunity Data Model This is the section that should drive your decision. The data model affects everything — reporting, integrations, migration difficulty, and how your engineering team builds on top of the platform. ### Greenhouse: Application-Centric Greenhouse uses a traditional relational model. Applications associate candidates with jobs. There are 2 kinds of applications: candidates and prospects. Candidate applications always have exactly 1 job. Prospect applications can have 0 or more jobs. The hierarchy is: **Candidate → Application → Job → Scorecard**. A Candidate is the person. An Application is that person's candidacy for a specific Job. Scorecards hang off Applications, each with structured attribute ratings and an overall recommendation. This separation is rigid by design — it enforces the structured hiring process that Greenhouse is known for. If John Doe applies for a Sales role in 2024 and an Engineering role in 2026, he exists as one Candidate with two distinct Applications. This keeps data normalized and makes historical reporting straightforward — every application, scorecard, and interview is linked to a specific person-job pair. Custom Fields on the application object are only available to customers with Enterprise-level accounts. This is a gate worth knowing about before you sign. ### Lever: Opportunity-Centric Each Candidate will be represented by one or many Opportunities. On Lever's new data model, a "Contact" will have independent Opportunities for each of their Applications. This means that any current Candidate with multiple Applications will be split into several candidateIds, and represented as Opportunities and opportunityIds via new Opportunities endpoints. The hierarchy is: **Contact → Opportunity(s)**. A Contact is the person. Each Opportunity represents a candidacy through your pipeline and carries its own notes, feedback, interview schedules, and forms. A "Contact" is an object that the application uses internally to identify an individual person and their personal or contact information, even though they may have multiple opportunities. The "Contact" is exposed via the contact field, which returns the unique ID for a Contact across your account. This is excellent for CRM workflows — recruiters can move an Opportunity between different stages or jobs, and attributes like origin and source sit directly on the Opportunity. But extracting a unified "Candidate Profile" from Lever requires your engineering team to deduplicate and merge multiple Opportunities on the backend, which is non-trivial for analytics. ```text Greenhouse Candidate → Application → Job → Stage → Scorecards / Offer Lever Contact → Opportunity → Posting / Requisition → Stage → Feedback / Offer ``` ### Why This Matters for Your Engineering Team The data model difference has three practical consequences: 1. **Reporting.** Greenhouse's relational model makes SQL-based analytics straightforward — join `candidates`, `applications`, and `scorecards` tables on their IDs. Lever's Opportunity model requires you to aggregate across Opportunities to get person-level metrics, since the same Contact can appear across multiple Opportunity records. Lever also has a specific risk: if you let sources, tags, and workflow variants sprawl without governance, your reporting degrades fast. Lever offers controls for locking down tag and source creation, but it requires discipline your team may not have at scale. 2. **Integrations.** Lever supports OAuth 2.0, which means managing the full authorization code flow: redirect URLs, authorization codes, token exchange, and refresh token rotation. When a token expires, you need the refresh token to get a new pair. If the refresh fails, you need to prompt the customer to re-authenticate. Greenhouse's Harvest API (v1/v2) uses simpler Basic Auth, but v3 moves to OAuth 2.0 as well. 3. **Migration.** Moving between these two systems is a data-model translation problem, not a CSV upload. A naive export flattens the relational structure and silently drops scorecards, interview feedback, and attachment URLs. See our [Lever to Greenhouse migration guide](https://clonepartner.com/blog/blog/lever-to-greenhouse-migration-the-ctos-technical-guide/) and [Greenhouse to Lever migration guide](https://clonepartner.com/blog/blog/greenhouse-to-lever-migration-the-ctos-technical-guide/) for the full breakdown. > [!NOTE] > **Lever's deprecated Candidates endpoints still exist** alongside the Opportunities endpoints. Any new integration should use Opportunities exclusively. The `contact` field is the unique person identifier; the `opportunityId` is the specific candidacy. > [!WARNING] > If you plan to build a custom data warehouse integration, Greenhouse's relational model is significantly easier to map to standard SQL schemas. Lever's Opportunity model requires extensive transformation logic to separate the person from the application history. ## API Limits and Developer Experience If your engineering team will build custom integrations, sync data to a warehouse, or run bulk operations against either platform, API rate limits will be your primary operational constraint. ### Greenhouse Harvest API Harvest API requests for approved Greenhouse partners and customer-built custom integrations are limited to the amount specified in the returned X-RateLimit-Limit header, per 10 seconds. The commonly reported limit is **50 requests per 10 seconds** for v1/v2. For Harvest v3, this limit is applied on a fixed-window basis, meaning the counter resets at the end of each 30-second interval. To help you manage your request volume and avoid hitting the limit, we include HTTP headers in every API response. If you exceed the request limit within a 30-second window, the API will respond with an HTTP 429 Too Many Requests status code. When you receive a 429 error, the response will also include a Retry-After header. Retry-After: The number of seconds you must wait before making another request. The Audit Log API is even more constrained, with paginated requests limited to **3 per 30 seconds**. This makes real-time compliance syncing very difficult — plan for batched, delayed processing and implement exponential backoff in all your integration layers. Greenhouse offers multiple distinct APIs (Harvest, Ingestion, Job Board, Onboarding/GraphQL, etc.), each with different auth methods, pagination styles, and rate limits. The Onboarding API is GraphQL-only — a separate pattern your team will need to support if you use Greenhouse Onboarding. > [!WARNING] > **Harvest v1/v2 is deprecated and will be removed on August 31, 2026.** Harvest API v1 and v2 will be deprecated and unavailable after August 31, 2026. All integrations must migrate to Harvest v3, which uses OAuth 2.0 instead of Basic Auth. If you're evaluating Greenhouse today, build everything against v3 from day one. Any integration built on v1/v2 now is technical debt with a hard deadline. ### Lever Data API Lever enforces rate limits on the Data API — the standard limit is 10 requests per second per API key, with burst capacity up to 20 requests per second using a token bucket algorithm. There's a critical secondary limit worth knowing: Lever will return a 429 status code (TOO MANY REQUESTS) if your custom job site issues more than 2 application POST requests per second. This 2 req/sec cap on application creation is the real bottleneck for high-volume ingestion scenarios — if you're processing thousands of inbound applicants, this will gate your throughput. Lever uses cursor-based pagination with a next token in the response body rather than in headers. This is a different pattern from Greenhouse's header-based cursor in v3 — something your integration layer will need to handle if you support both platforms. Lever's documentation exposes broad admin scopes across opportunities, users, uploads, webhooks, and requisitions, making it easier to reason about for operational sync use cases. ### API Comparison Table | Dimension | Greenhouse (Harvest v3) | Lever (Data API) | |---|---|---| | **Auth model** | OAuth 2.0 (client credentials) | OAuth 2.0 (authorization code) | | **Read rate limit** | ~50–75 req / 30s window (fixed window) | 10 req/sec steady, 20 req/sec burst (token bucket) | | **Write rate limit** | Same as read | 2 req/sec for application POSTs | | **Pagination** | Cursor-based (Link header, opaque Base64 token) | Cursor-based (next token in response body) | | **Rate limit response** | HTTP 429 + `Retry-After` header | HTTP 429 | | **Webhook support** | Yes (configurable per event type) | Yes (HMAC-signed) | | **Sandbox environment** | Yes (on higher tiers) | Not publicly documented | | **API deprecation risk** | v1/v2 sunset Aug 31, 2026 | Candidates endpoints deprecated; Opportunities is current | **Lever wins on raw throughput** for typical integration scenarios — 10 req/sec steady state is meaningfully faster than Greenhouse's effective ~2–5 req/sec. **Greenhouse wins on ecosystem breadth**, developer tooling, and the BI Connector for warehouse-grade analytics. ## Feature Comparison: Sourcing, Workflows, and Analytics ### Structured Hiring and Scorecards Greenhouse is built on the premise that every hiring decision should be structured, consistent, and evidence-based. Each role gets a customized hiring plan with defined stages, interview kits (questions mapped to attributes being evaluated), and scorecards where interviewers rate candidates on specific criteria rather than giving a vague thumbs up or down. This structure reduces bias, improves consistency across interviewers, and creates a defensible hiring record. Greenhouse allows administrators to lock down the process. You can mandate that an interview cannot proceed until a specific scorecard is submitted. For enterprises, this kind of enforcement prevents the inconsistency that creeps in when recruiters have the freedom to skip steps. Lever has structured interview features, but they're materially less mature than Greenhouse's. The scorecard system is functional but lacks the competency framework depth and feedback analytics that Greenhouse offers. Companies prioritizing interview consistency and defensible hiring decisions will find Lever's structured hiring tools insufficient. **Winner: Greenhouse**, by a wide margin. If structured hiring is a priority, this alone may be decisive. ### CRM and Candidate Nurturing Lever's CRM capabilities are a key differentiator. LeverTRM lets recruiters build talent pools, send nurture campaigns to passive candidates, track relationship history, and score candidate potential — all without requiring a separate CRM tool. For proactive sourcing-heavy teams, this is valuable. Lever's Chrome extension is also superior for outbound sourcing — recruiters can scrape LinkedIn profiles and drop them directly into nurture campaigns without leaving the browser. Greenhouse has CRM features (Greenhouse CRM module) but it's historically been more focused on active candidates. The sourcing and nurturing workflow isn't as native as Lever's. Greenhouse treats sourced candidates as "Prospects" who must eventually be converted into strict "Candidates" attached to a specific job — a conceptual mismatch for teams that want to build relationships before a role even opens. **Winner: Lever.** If your recruiting model depends on long-term passive candidate engagement, Lever is purpose-built for it. ### Analytics and Reporting Business Intelligence Connector delivers a nightly ETL of your organization's Greenhouse Recruiting or Greenhouse Onboarding data. The data model relies on three main keys, on which other tables and columns are mapped. This enables data teams to run complex cross-source queries in Amazon Redshift, Google BigQuery, or Snowflake using normalized Candidate, Application, and Job keys. Lever has solid reporting for pipeline metrics, source tracking, and diversity data. Less customizable than Greenhouse's reporting for complex analytics use cases, but sufficient for most teams. Lever's Visual Insights provides excellent out-of-the-box dashboards for recruiters who don't need warehouse-level depth. **Winner: Greenhouse** for deep analytics. The BI Connector gives data teams direct warehouse access and is the most portable way to get your data out. Lever's Visual Insights covers standard pipeline reporting but won't satisfy a data-heavy engineering org. ### DEI Features Greenhouse has invested more in DEI capabilities than any other ATS. The Expert plan includes anonymized resume reviews, demographic data collection at each pipeline stage, inclusion analytics that show where underrepresented candidates drop off, and bias nudges that alert interviewers to potentially biased language in their feedback. Greenhouse leads in DEI features with anonymous resume review, inclusive job description tools, and comprehensive demographic reporting. Lever offers diversity surveys and EEO reporting but lacks Greenhouse's structured approach to reducing hiring bias. **Winner: Greenhouse.** Not close. ### Integrations Ecosystem Greenhouse integrates with 500+ tools including all major HRIS systems (Workday, BambooHR, UKG), background check providers, assessment tools, job boards, and productivity suites. The open API enables custom integrations. Lever connects to 300+ integrations. Key integrations with LinkedIn Recruiter, Slack, Google/Microsoft calendars, HRIS systems, and background check providers are all available. Greenhouse's enterprise footprint means HRIS platforms and background check providers often build their deepest, most stable integrations for Greenhouse first. If your stack includes niche assessment or compliance tools, check the marketplace before committing. **Winner: Greenhouse** on breadth. Both cover the essentials. ### Feature Comparison Table | Capability | Greenhouse | Lever | Winner | |---|---|---|---| | **Structured interviews** | Industry benchmark — kits, scorecards, per-attribute ratings | Functional but shallow | Greenhouse | | **CRM / nurturing** | Module available, not native strength | Core product (LeverTRM) | Lever | | **Analytics / BI** | BI Connector (nightly ETL to warehouse) | Visual Insights (in-app) | Greenhouse | | **DEI tools** | Anonymized review, inclusion analytics, bias nudges | Diversity surveys, EEO reporting | Greenhouse | | **Ease of use** | Steeper learning curve, requires config investment | Intuitive, faster onboarding | Lever | | **Integration ecosystem** | 500+ native integrations | 300+ native integrations | Greenhouse | | **Mobile experience** | Native iOS/Android app | Browser-based mobile | Greenhouse | | **Onboarding module** | Greenhouse Onboarding (add-on) | Not available | Greenhouse | | **Search / rediscovery** | Strong for structured data; application-centric | Opportunity-centric search with resume snippets | Lever | | **Custom workflows** | Approval chains, stage-level automation | Flexible pipelines, automation rules | Tie | ## Pricing and Total Cost of Ownership Neither platform publishes pricing. Both require a sales conversation, which puts buyers at an information disadvantage. **Greenhouse** uses tiered pricing based on company size and feature requirements. Greenhouse organizes its pricing into three main tiers. The entry-level tier targets smaller companies — typically under 50–100 employees doing up to 30 hires per year. This tier covers core ATS functionality: job posting to major boards, application management, basic interview scheduling, and standard reporting. Approximate pricing: $6,000–$10,000 per year for companies with under 50 employees. What's notably missing at the entry-level tier: API access, advanced analytics, Greenhouse's structured interview toolkits, sourcing automation, and most integrations beyond the major HRIS connectors. The features that make Greenhouse worth choosing — BI Connector, audit log, sandbox environments, and enterprise security controls — are all gated behind higher tiers. Lever plans range from $4,000 to $20,000 a year, with prices based on CRM add-ons and advanced automation features. Lever's core ATS includes applicant tracking, job posting distribution, candidate pipeline management, interview scheduling, and basic reporting. Enterprise configurations typically add advanced analytics and reporting, candidate relationship management (CRM/nurture), API access, custom integrations, dedicated customer success support, and higher user seat limits. ### Hidden Costs to Model - **Greenhouse renewal escalation:** Annual renewal increases have been consistently reported in the 8–15% range, with some customers reporting increases at the higher end after years two or three. Model 3-year TCO, not Year 1 pricing. - **Lever PE ownership:** Lever's ownership by Employ Inc. — a private equity-backed platform company — has historically been associated with price management strategies that frustrate customers at renewal. Budget predictability is a genuine risk on both sides. - **Greenhouse implementation:** Median implementation time for Greenhouse enterprise deployments is 60–90 days. That's internal team time plus potential professional services fees. - **Lever add-ons:** Features like advanced analytics, candidate nurture/CRM, and enhanced reporting may be sold as add-ons rather than included in the base platform. - **Data extraction engineering:** Greenhouse charges extra for the BI Connector. If you try to bypass it with custom Harvest API scripts, you'll hit rate limits quickly. Lever includes broader API access, but building the transformation logic to normalize their Opportunity data model into something your warehouse can use will cost internal engineering hours. ### TCO by Company Size | Company Size | Greenhouse (Annual) | Lever (Annual) | Notes | |---|---|---|---| | Startup (<50 employees) | $6K–$10K | $4K–$8K | Both may be overkill; consider lighter alternatives | | Mid-market (200 employees) | $10K–$20K | $5K–$10K | Lever cheaper at entry; Greenhouse delivers more at this scale | | Enterprise (500+ employees) | $20K–$70K+ | $15K–$25K+ | Greenhouse's structured process pays for itself | ## Security, Compliance, and Data Sovereignty Greenhouse holds annual audits against SOC 1 Type 2 and SOC 2 Type 2, and is certified for ISO 27001:2022, ISO 27701:2019, and ISO 42001:2023. It complies with GDPR, CCPA/CPRA, PCI DSS, EU-U.S. DPF, UK Extension to the EU-U.S. DPF, and Swiss-U.S. DPF. Security features include Single Sign-On (SSO), SCIM user provisioning, audit log API, permissions approvals, a dedicated security team with a 24/7/365 security operations center, malware scanning for uploaded files, encryption in transit (TLS 1.2+) and at rest (AES 256-bit). Greenhouse physical infrastructure runs atop Amazon Web Services (AWS). Virtualized infrastructure runs within AWS Virtual Private Cloud. All files (such as resumes and cover letters) are stored using Amazon S3 and are encrypted at rest. Greenhouse publishes data residency options across US, EU, and APAC regions — useful for regulated buyers who need an explicit residency story. Lever's (Employ's) security programs and practices have been independently verified against the SOC 2 and ISO 27001 framework. Lever by Employ's information security parameters comply with the General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA). Lever's public status page exposes separate Global and EU data centers, but its public documentation is less specific about architecture than Greenhouse's. **Greenhouse holds a measurably stronger compliance posture.** ISO 42001 (AI management) certification is a notable differentiator as AI-assisted hiring tools come under EU AI Act scrutiny. The audit log API matters for regulated industries — it tracks report exports, user-permission edits, API key usage, configuration changes, and PII access. Greenhouse also allows granular permission controls — you can restrict access down to specific fields on a scorecard or hide specific stages from interviewers. Lever's permission model is simpler, which works for startups but often fails compliance audits in enterprise environments where "least privilege" access is strictly enforced. Expert tier customers can purchase the audit log add-on for additional records of important user activity. Two caveats: the audit log is gated behind the highest pricing tier, and Greenhouse documents it as a rolling 30-day record unless you export it. Plan for external retention if you need long-term audit trails. For teams handling EU candidate data, see our [GDPR-compliant data migration blueprint](https://clonepartner.com/blog/blog/gdpr-compliant-data-migration-the-enterprise-blueprint/) and [ATS migration GDPR/CCPA compliance guide](https://clonepartner.com/blog/blog/ats-migration-gdpr-ccpa-compliance/). ## Migration and Lock-in Getting data **into** either platform is straightforward — both support CSV bulk import and API-based ingestion. Getting data **out** is where the differences emerge. ### Greenhouse Export Greenhouse provides CSV exports from built-in reports, plus full programmatic access via the Harvest API. Resumes, cover letters, and other document attachments are hosted on Amazon Web Services and are provided via signed, temporary URLs. Due to the ephemeral nature of these resource links, users should download these documents immediately after the request is made. If you don't download attachments during the same pipeline run, the URLs expire and you lose access. The BI Connector (paid add-on) gives you a nightly ETL dump to your own warehouse — the most portable option if you're on a high enough tier. ### Lever Export Lever's Data API provides full read access to Opportunities, feedback, notes, offers, and files. No native bulk export UI exists — you'll need to script it. The token bucket rate limit of 10 req/sec is workable for accounts under ~50K candidates; above that, expect multi-hour extraction runs. Lever's own instance-to-instance migration documentation is blunt: migration is paid, many objects cost extra, and items like integrations, automations, GDPR configuration, and custom application questions are not included in standard transfer. If even same-vendor migration leaves that much behind, cross-vendor migration is naturally harder. ### Switching Costs Moving between Lever and Greenhouse is a non-trivial engineering project. The data model mismatch (Opportunity-centric vs Application-centric) means: - A Lever Contact maps to a Greenhouse Candidate (1:1). Each Lever Opportunity maps to one Greenhouse Application tied to a specific Job. A single Contact with multiple Opportunities becomes one Candidate with multiple Applications. - Greenhouse's Harvest API does not expose a POST endpoint for creating scorecards — only GET endpoints for reading them. The standard workaround is to import Lever feedback as structured notes on the candidate's activity feed, preserving interviewer name, overall recommendation, and per-attribute ratings. - Attachment URLs are ephemeral on both sides, requiring same-run download and re-upload. - Source attribution, custom fields, EEOC/GDPR data, and historical stage movement are where most migrations silently lose fidelity. At ClonePartner, we handle these exact transformations daily. We map Greenhouse's relational structure into Lever's Opportunity model (and vice versa) using custom ETL pipelines that respect rate limits and guarantee zero data loss. For the full technical playbook, see our [Lever to Greenhouse](https://clonepartner.com/blog/blog/lever-to-greenhouse-migration-the-ctos-technical-guide/) and [Greenhouse to Lever](https://clonepartner.com/blog/blog/greenhouse-to-lever-migration-the-ctos-technical-guide/) migration guides, plus our [ATS migration gotchas](https://clonepartner.com/blog/blog/ats-migration-gotchas/) coverage. ## Use-Case Recommendations **Startup / small team (<50 employees):** **Lever.** Faster to set up, lower cost, and the CRM is useful when you're competing for early hires. Greenhouse's structured process adds overhead you don't need yet. The flexible data model fits teams pivoting their hiring plans weekly. **Mid-market / scaling team (50–500 employees):** This is where it gets interesting. If you're hiring engineers and need defensible, consistent evaluations — **Greenhouse**. If you're a sourcing-first team in a competitive talent market (SaaS, fintech) competing for passive candidates — **Lever**. **Enterprise (500+ employees):** **Greenhouse.** The structured hiring framework, DEI tooling, BI Connector, and compliance certifications are designed for this scale. Greenhouse is the clear choice for teams where compliance, structured process, and cross-department consistency are non-negotiable. **Low technical bandwidth:** **Lever.** If your recruiting team needs to move fast with minimal admin overhead, Lever's faster-to-configure interface is a practical advantage. Lever implementations take weeks, not months. **Dedicated dev/ops team building custom integrations:** **Greenhouse.** The API ecosystem is deeper, the BI Connector enables warehouse-level analytics, and the relational data model maps cleanly to SQL. **Regulated industries (financial services, healthcare-adjacent):** **Greenhouse.** ISO 42001 certification, audit log API, granular permissions, and EEOC/OFCCP compliance features are hard to replicate in Lever. **Budget-conscious buyers:** **Lever**, at the entry level. But model the 3-year TCO — both platforms have renewal escalation patterns that erode Year 1 savings. ## Strengths and Weaknesses ### Greenhouse Strengths 1. **Industry-leading structured hiring** — scorecards, interview kits, and approval workflows set the benchmark 2. **Deep analytics** — BI Connector gives data teams raw warehouse access with normalized keys 3. **Strongest compliance posture** — SOC 1/2, ISO 27001/27701/42001, GDPR, and EU AI Act readiness 4. **500+ integrations** — the largest ATS ecosystem 5. **DEI tooling** — anonymous review, bias nudges, inclusion analytics 6. **Relational data model** — makes enterprise reporting and warehouse ETL straightforward ### Greenhouse Weaknesses 1. **High configuration overhead** — 60–90 day enterprise implementation is real time invested 2. **Pricing opacity and escalation** — 8–15% annual increases compound fast 3. **Entry tier is hobbled** — API access, structured interviews, and advanced analytics are all gated 4. **CRM/sourcing is an afterthought** — passive candidate nurturing is not a strength 5. **Attachment URLs are ephemeral** — signed S3 links expire, creating migration and archival headaches 6. **Audit log retention** — rolling 30-day record requires external handling for long-term compliance history ### Lever Strengths 1. **Best-in-class CRM for an ATS** — LeverTRM's nurturing pipeline is genuinely differentiated 2. **Intuitive UI** — lower learning curve, faster time-to-productivity for recruiters 3. **Lower entry cost** — more accessible for growth-stage companies 4. **Developer-friendly API** — token bucket rate limiting with 10 req/sec steady state and 20 req/sec burst 5. **Faster implementation** — weeks, not months 6. **Strong search and rediscovery** — opportunity-centric search with resume snippets and structured tags ### Lever Weaknesses 1. **Shallow structured hiring** — scorecard system lacks Greenhouse's depth, competency frameworks, and feedback analytics 2. **Employ Inc. ownership** — PE-backed parent creates renewal pricing uncertainty 3. **Smaller integration ecosystem** — 300+ vs 500+ matters for niche enterprise tools 4. **Analytics gaps** — no warehouse-grade BI connector; limited custom reporting 5. **Candidate search at scale** — archived talent pool management can become cumbersome above ~50K contacts 6. **Weaker compliance posture** — simpler permissions model and less public documentation on security controls ### Overhyped vs Underrated - **Greenhouse overhyped:** Its CRM module. Don't buy Greenhouse expecting Lever-grade candidate nurturing. - **Greenhouse underrated:** The BI Connector. Teams that use it get a material analytics advantage over competitors stuck in in-app dashboards. - **Lever overhyped:** "ATS+CRM in one" — the ATS half is solid but the structured hiring depth isn't enterprise-grade. - **Lever underrated:** Speed to productivity. Recruiting teams ship with Lever faster than almost any other mid-market ATS. ## The Verdict: Choose Based on Your Bottleneck Greenhouse and Lever solve fundamentally different problems because they have fundamentally different data models. **Choose Greenhouse if:** - You need structured, defensible hiring processes with auditable scorecards - Your analytics team wants direct warehouse access to recruiting data - You operate in regulated industries requiring ISO 42001, EEOC/OFCCP compliance, or advanced audit logging - You have 500+ employees and multiple business units with different hiring processes - DEI is a strategic priority, not just a checkbox **Choose Lever if:** - Your competitive edge is sourcing — you're reaching out to passive candidates months before they're ready to apply - You need a CRM-grade talent pipeline without buying a separate tool - You're a growth-stage team that needs to move fast with minimal admin overhead - Your recruiting team prioritizes UI simplicity and time-to-productivity over process enforcement - You're budget-sensitive and need a lower entry point with a shorter implementation Greenhouse's **Candidate → Application → Scorecard** chain enforces process rigor at the cost of flexibility and configuration time. Lever's **Contact → Opportunity** chain enables relationship velocity at the cost of evaluation depth. Pick based on which bottleneck is actually hurting your hiring: inconsistent process, or insufficient pipeline. There is no universal "better" — only a better fit for your specific hiring motion, technical stack, and compliance requirements. If you're already on one platform and evaluating a switch, don't underestimate the migration complexity. The data model mismatch means you're not moving files — you're translating one hiring philosophy into another. Our [ATS migration checklist](https://clonepartner.com/blog/blog/the-ultimate-ats-data-migration-checklist-a-10-point-plan-for-a-compliant-transition/) covers the planning phase. > If you're evaluating a move between Lever and Greenhouse — or migrating to either platform from another ATS — we've handled hundreds of ATS migrations. We'll scope your data model, map the object translation, and execute with zero downtime. Book a free 30-minute migration assessment. > > [Talk to an ATS Migration Expert](https://cal.com/clonepartner/meet?duration=30) ## Frequently asked questions ### What is the main architectural difference between Lever and Greenhouse? Greenhouse uses an application-centric data model (Candidate → Application → Job → Scorecard) that separates the person from each candidacy. Lever uses an opportunity-centric model (Contact → Opportunity) where a single Contact has independent Opportunities for each candidacy. This difference affects reporting, integrations, and migration complexity. ### What are the API rate limits for Greenhouse and Lever? Greenhouse's Harvest API allows approximately 50–75 requests per 30-second fixed window (v3), returning HTTP 429 with a Retry-After header when exceeded. The Audit Log API is limited to 3 paginated requests per 30 seconds. Lever's Data API allows 10 requests per second (steady state) with burst capacity up to 20 req/sec via a token bucket algorithm, but application POST requests are capped at just 2 per second. ### Is Greenhouse or Lever better for structured hiring? Greenhouse is the clear winner. It offers per-attribute scorecard ratings, mandatory interview kits, question-to-attribute mapping, and approval workflows that enforce evaluation consistency. Lever has structured interview features, but they lack the competency framework depth and feedback analytics that make Greenhouse the industry benchmark. ### How much do Greenhouse and Lever cost in 2026? Neither publishes pricing. Greenhouse typically ranges from $6,000–$70,000+ per year depending on tier and company size, with reported annual renewal increases of 8–15%. Lever ranges from $4,000–$20,000+ per year. Both require custom quotes. Key features on both sides — BI Connector on Greenhouse, CRM/nurture on Lever — may be gated behind higher tiers or sold as add-ons. ### Can you migrate data between Lever and Greenhouse? Yes, but it's a data-model translation problem, not a simple CSV upload. A Lever Contact maps to a Greenhouse Candidate (1:1), and each Lever Opportunity maps to one Greenhouse Application. Scorecards cannot be created via Greenhouse's API — they must be imported as structured notes. Attachment URLs are ephemeral on both platforms and must be downloaded and re-uploaded in the same pipeline run.