Kombo is a technically credible, compliance-first unified HR API built for a specific audience: HR tech companies that need deep, reliable connectivity into European ATS and HRIS systems. For that use case, it is among the strongest options available in 2026. It earned a $25M Series A in February 2026 (bringing total funding to $30M), holds a 4.8/5 G2 rating across 87 reviews, and achieved the highest quality-of-support score (9.9/10) in the unified API category. But Kombo's strength is inseparable from its constraint: it covers four HR-adjacent categories and nothing else, uses a sync-and-store data model, and as of August 2026 has not shipped AI agent infrastructure. This evaluation breaks down where Kombo earns its reputation, where it creates architectural obligations you should understand before committing, and which teams should be looking at alternatives.
What Kombo Does
Kombo (kombo.dev) is a unified API platform founded in 2022 and headquartered in Berlin, Germany. Its core product lets software companies connect once to Kombo's API and gain immediate access to pre-built integrations across four HR-adjacent categories:
- HRIS & Payroll - employee records, payroll data, org structures, absences, timesheets, documents, performance reviews
- ATS (Applicant Tracking Systems) - candidates, applications, job postings, stages, offers, screening questions
- Assessment & Background Check - third-party assessment platforms integrated into hiring workflows
- LMS (Learning Management Systems) - learning and onboarding systems tied to workforce development
Instead of building and maintaining dozens of individual integrations as your customer base grows across different HR systems, you build one integration to Kombo and it handles the connectors, data normalization, and ongoing maintenance as upstream systems change.
What distinguishes Kombo from horizontal platforms like Merge or Apideck is a deliberate depth-over-breadth decision. Rather than spanning CRM, accounting, ticketing, email, and calendar alongside HR, Kombo concentrated its engineering investment within HR. That bet is most visible in its European system coverage and in the quality of its HR-specific data models.
As of mid-2026, Kombo works with 300+ companies, including Indeed, Paychex, HireVue, Edenred, Gem, Experian, Greenhouse, Factorial, and TestGorilla. The company raised $25M in Series A funding in February 2026 led by Volition Capital, with participation from Y Combinator, Acadian Ventures, and 468 Capital.
Architecture Deep Dive
Kombo's architecture is a sync-and-store model combined with regional deployment isolation. Understanding both is important before committing to the platform.
How Data Sync Works
Kombo pulls data from connected HRIS and ATS systems on a scheduled polling basis and stores a normalized copy in its own infrastructure. When your application calls Kombo's API, it reads from Kombo's locally cached copy rather than hitting the source system in real time. Kombo supplements polling with webhook notifications that alert you when sync events occur.
The trade-off: reads are fast and consistent because they are decoupled from source system latency and availability. The cost is inherent lag - the time between a change occurring in the source ATS or HRIS and that change appearing in Kombo's copy depends on the polling interval configured for each integration. Kombo does not publicly disclose default polling intervals per integration, so teams with strict freshness requirements should ask specifically during evaluation.
The more significant implication is data storage: this architecture means employee PII and candidate data is mirrored into Kombo's infrastructure, not merely proxied through it. Kombo manages this with strong security controls (detailed in the Compliance section below), but it is an architectural fact that has procurement consequences for enterprise buyers.
Regional Deployment Isolation
Kombo operates fully independent deployments across two regions:
- EU region:
api.kombo.dev - US region:
api.us.kombo.dev
These are not logical separations within a shared system - they are independent deployments with separate databases, sync workers, and API layers. API keys created in one region cannot authenticate against the other. Data does not traverse regional boundaries.
For EU-based companies with GDPR data residency requirements, this architecture provides a harder guarantee than most platforms offer. The global dashboard frontend routes to the appropriate datacenter based on account region.
Passthrough API
For scenarios where Kombo's normalized data model does not expose what you need, the platform provides a passthrough API that lets you send requests directly to the underlying connected system using that system's native schema. A standard escape hatch in unified API design - it acknowledges that normalization is always incomplete for edge cases while preserving the unified abstraction for the majority of use cases.
Integration Coverage
ATS Coverage: 70+ Systems
Kombo's ATS coverage spans 70+ systems. Major platforms include Greenhouse, Ashby, Lever, SmartRecruiters, Oracle Recruiting Cloud, Workday Recruiting, SAP SuccessFactors Recruiting, Bullhorn, iCIMS, and Jobvite.
European-specific ATS systems where Kombo shows particular depth include Softgarden (widely used in the German market), Recruitee, Umantis, onlyfy (formerly XING Jobs), and several UK-market systems that US-first platforms tend to under-invest in. This EU-specific breadth is where the platform's German origins translate into a concrete advantage.
HRIS Coverage: 87+ Systems
HRIS coverage spans major global platforms - Workday, SAP SuccessFactors, UKG Pro, UKG Ready, Oracle HCM, BambooHR, ADP Workforce Now, Dayforce, Cornerstone OnDemand - alongside a notably strong set of European-specific systems: Personio, PayFit, AFAS Software, Sage HR, rexx systems, HR WORKS, Kenjo, HeavenHR, and Factorial. Several of these are unavailable or poorly mapped on US-primary unified APIs, and the field-level implementation quality (covering German-specific employment fields, Dutch HR data structures, UK payroll nuances) reflects accumulated domain expertise.
Assessment and LMS
Kombo claims distinction as the only unified HR API platform offering both Assessment and LMS categories. The depth of connector coverage in these two categories is less mature than its ATS and HRIS coverage - teams evaluating Kombo primarily for Assessment or LMS should verify specific system support and field coverage during the sales process rather than relying on category-level claims.
What Is Not Covered
Kombo explicitly does not cover CRM, accounting, ticketing, email, calendar, communication, e-signature, expense management, or subscription management. Kombo's own documentation notes that companies needing integrations outside HR will need to combine Kombo with other specialized solutions.
Pricing
Kombo uses a platform fee plus flat per-customer connection fee model with unlimited API calls. Specific pricing is not published publicly and requires a direct quote from the sales team.
The structure suits B2B HR software companies: your cost scales with the number of active customer connections, not with API call volume. For products with recurring, consistent usage patterns - which describes most HR integrations - this is easier to budget than per-call pricing.
Enterprise pricing, on-premises deployment (referenced in the Series A announcement as a future option), and custom SLA terms require direct negotiation. No self-serve tier with published pricing exists as of August 2026.
Early-stage teams should request pricing details before investing significant engineering time in evaluation - without published pricing it is impossible to model cost-per-customer without a sales conversation.
Developer Experience
Documentation and Onboarding
Kombo's documentation is consistently rated as clear and complete across G2 reviews, with multiple reviewers reporting working integrations within days of starting evaluation. Sandbox access is available for most connected systems, which meaningfully reduces the time needed to test against specific ATS or HRIS configurations before production deployment.
Core Developer Tooling
- RESTful unified API with consistent endpoint structure across all connected systems
- Webhook notifications for sync events
- Custom field read/write capability (mapping custom fields from source systems to your unified schema)
- Remote data access for system-specific fields not covered by the normalized model
- Centralized dashboard with sync status tracking, authentication issue alerts, and searchable request logs
- Pre-built UI components for the customer-facing connection flow
Support Model
Kombo's support model is its most consistent differentiator across independent reviews. Customers receive dedicated Slack channels with access to engineers who carry domain expertise in specific HR systems. On G2, Kombo's quality of support score is 9.9/10 - the highest in the unified API category across 87 verified reviews. Multiple reviewers describe getting meaningful technical help within hours, including for edge cases in specific EU HR systems.
Known Friction Points
G2 reviewers identify several recurring issues:
- ATS sandbox approval delays: Accessing sandboxes for certain enterprise ATS systems is gated by approval processes controlled by the ATS vendors, not Kombo. iCIMS was cited with delays of three to six months - a real planning constraint for teams that need to validate against specific systems before committing.
- Write-back depth: Several reviewers noted that sending data back to ATS systems is less complete than reading from them. Pressure-test specific write operations you depend on during evaluation.
- Custom field mapping UX: The interface for configuring custom field mappings was noted as a usability gap - functional, but not as intuitive as the read-side experience.
Compliance and Security
What "GDPR-Native" Actually Means for Kombo
"GDPR compliant" appears on nearly every software vendor's marketing page. It is worth understanding precisely what Kombo's compliance architecture entails and where it goes further than a typical compliance checkbox.
Regional architectural isolation: Kombo's EU and US regions are fully independent deployments. Employee and candidate data for EU-region accounts never routes through US infrastructure - not as transit, not for analytics, not for replication. This is enforced at the infrastructure level, at the API key and database layer, not just through policy.
Deletion mirroring: Under GDPR, data subjects have the right to erasure. Kombo handles this by monitoring for deletions in the source system: when a record is removed from the connected HRIS or ATS, Kombo detects the deletion during the next sync and removes the mirrored record from its own database. The deletion is driven by the source system event, not by a separate API call from your application - though the timing is tied to the polling interval.
DSGVO certification: Kombo holds explicit DSGVO (Germany's implementation of GDPR) certification, reflecting the level of regulatory specificity expected by German enterprise procurement teams.
Security Certifications
- SOC 2 Type II
- ISO 27001
- HIPAA
- GDPR / DSGVO
Additional controls include encryption at rest, independent penetration testing, IP allowlisting for API keys, API key expiration policies, role-based dashboard access, and audit logging for sensitive operations.
For EU-based enterprise sales cycles - particularly in financial services, healthcare, and regulated industries where security questionnaires are a standard procurement step - this certification stack, combined with the architectural data residency guarantee, frequently shortens the compliance review period compared to vendors offering only logical separation or contractual commitments without architectural backing.
Honest Limitations
Geographic Concentration Within HR Coverage
Kombo's integration count across ATS and HRIS is competitive. But integration counts obscure something important: the completeness of field mapping and write operations for individual systems varies significantly. Kombo's depth in German, UK, French, Dutch, and Nordic HR systems - the implementation-level completeness of specific fields, edge-case workflows, and write operations - reflects years of European market focus. Its coverage of US regional payroll providers, mid-market US ATS platforms, and APAC HR systems is thinner.
For a US-primary or APAC-primary company, the high-level integration count can be misleading. Before committing, test the specific systems your customers use, including write operations, not just reads.
Category Scope Is Fixed at HR
Kombo does not cover and has not indicated plans to expand outside HR-adjacent categories. This enables depth within HR, but the constraint compounds over time for companies whose integration surface grows.
If your product today requires HR integrations and in 12 to 18 months will also need CRM, ticketing, accounting, or messaging integrations, building on Kombo means either adding a second unified API vendor or migrating platforms. Migrations between unified APIs are non-trivial: re-mapping data models, renegotiating pricing, rebuilding customer-facing connection flows.
Data Storage Is a Procurement Obligation
Kombo's sync-and-store model is standard architecture in the unified API category. But it is a fact that needs to surface in enterprise procurement processes. Employee records, candidate PII, salary data, and HR documents are stored in Kombo's infrastructure for as long as a connection is active. The security controls are strong, but "we store your customers' HR data in our infrastructure" is a statement that enterprise buyers require legal and security sign-off on, regardless of the certification stack.
No Native AI Agent Infrastructure
As of August 2026, Kombo does not offer a Model Context Protocol (MCP) server, AI agent framework, or structured interface for AI orchestration. Its AI Apply product (launched May 2026) uses browser agent automation to submit job applications through ATS interfaces that lack native APIs - an interesting approach to a specific problem, but distinct from exposing HR data to AI agents through a structured API.
The Series A announcement referenced future plans to enable AI agents through portable people data. That capability has not shipped. For companies building AI-native HR products - autonomous recruiting copilots, workforce planning AI, HR system chatbots - this gap means building your own orchestration layer on top of Kombo's existing API, without native tooling support.
Who Kombo Is Best For
European HR Tech Companies
If you are building an ATS, HRIS, hiring platform, or workforce tool primarily for European customers, Kombo's coverage of regional systems - Personio, PayFit, Softgarden, AFAS Software, rexx systems, Kenjo, HeavenHR - is a tangible advantage. These systems are underserved or unavailable on US-first platforms, and the implementation quality for EU-specific data fields and workflows reflects accumulated expertise, not just a connector checkbox.
ATS Platforms Expanding into European Recruitment Markets
US-based ATS vendors expanding into Europe who need to pull candidate data from or push offers into European employer HR systems benefit from Kombo's connector depth without having to build and maintain those integrations individually.
HR Tech Companies with Pure Hiring and Workforce Workflows
Assessment platform providers, background check vendors, LMS companies, and HR analytics tools that need structured, normalized access to ATS and HRIS data - and whose integration surface does not extend beyond HR - are well-served by Kombo's focused scope.
Companies Where GDPR Compliance Is a Sales Requirement, Not Just a Checkbox
Enterprise buyers in EU financial services, healthcare, and government procurement require verifiable data residency guarantees, not policy statements. Kombo's architectural isolation makes that verification auditable. For sales cycles where a data residency attestation accelerates procurement, this architectural approach has real commercial value.
Who Should Evaluate Alternatives
Global HR Tech Companies with Multi-Region Customers
Companies with significant US, APAC, and EU customer segments will encounter Kombo's European concentration as a practical constraint. The headline integration count looks balanced; the field-level completeness for US regional and APAC systems is where gaps appear. A platform with more geographically balanced investment may produce better aggregate outcomes for a globally distributed customer base.
Companies with Multi-Category Integration Needs
If your product's integration surface extends beyond HR - customers expect to connect CRM, ticketing, accounting, email, or calendar alongside their HRIS - Kombo cannot serve those needs. Operating two separate unified API vendors is workable but adds operational overhead: two vendor relationships, two monitoring setups, two data models, two pricing negotiations.
AI-Native Product Builders
Teams building AI agent-powered HR products - autonomous recruiting workflows, workforce planning copilots, HR chatbots - need infrastructure that exposes structured HR data to AI agents through defined interfaces. Kombo does not provide this natively. Until MCP server support or equivalent tooling ships, teams building in this space will need to construct their own orchestration layer.
Early-Stage Teams That Need Pricing Certainty Before Committing Engineering Resources
The absence of published pricing creates evaluation friction for early-stage teams operating under budget constraints. If a vendor's pricing model is a prerequisite for a build-vs-buy decision, not knowing Kombo's rates until after a sales cycle adds friction. Evaluate pricing early.
Knit
Knit takes a different architectural position: it operates as a stateless, zero-storage platform that does not persist customer data in its infrastructure. Data is pushed to your registered webhook endpoint in real time rather than polled and cached. For teams where GDPR's data minimization principle extends to third-party storage - meaning the preferred state is no third-party copy of employee PII - this architecture addresses that requirement structurally.
Knit covers 13+ integration categories (HRIS, ATS, CRM, Accounting, Ticketing, Email, Calendar, Communication, Meetings, E-Sign, Assessment, Expense Management, Subscription Management) with 160+ connectors, EU and global market coverage, and a native MCP server for AI agent workflows. For EU-only HR teams with no multi-category needs and a preference for Kombo's specific EU system depth, that trade-off may favor Kombo. For teams with multi-category requirements, a zero-storage preference, or AI agent workloads, the comparison shifts. Knit does offer hosting in Sweden for EU customers apart from other options for its global customers
Merge
Merge covers seven integration categories with strong US coverage and moderate EU depth. Its normalized data model is mature. It is the more established competitor in the US enterprise market but has historically invested less in EU-specific regional HR systems. Enterprise pricing is also quote-based.
Finch
Finch focuses specifically on HRIS and payroll connectivity in the US market. Its depth in US payroll data is real. For European teams or multi-category needs, it is a poor fit by design.
Apideck
Apideck covers five to six categories with a developer-friendly API and more transparent pricing than some competitors. Its EU HR coverage is less specialized than Kombo's. A reasonable option for early-stage teams that need broad coverage and can accept less depth in EU-specific systems.
FAQ
Does Kombo store my customers' employee and candidate data?
Yes. Kombo's sync-and-store architecture mirrors data from connected HRIS and ATS systems into Kombo's regional infrastructure. For EU-region accounts, data is stored on EU servers with no cross-regional transit. Security controls include SOC 2 Type II and ISO 27001 certification, encryption at rest, and audit logging. Teams with strict data minimization requirements or enterprise buyers who prohibit third-party PII storage should evaluate this architectural reality explicitly during procurement.
How many integrations does Kombo support?
As of mid-2026: 70+ ATS systems, 87+ HRIS systems, plus Assessment and LMS connectors - totaling 250+ integrations across four HR-adjacent categories.
Does Kombo handle GDPR deletion requests automatically?
Yes, through deletion mirroring. When a record is deleted from the source HRIS or ATS, Kombo detects the deletion during the next sync cycle and removes the mirrored record. The timing is tied to polling intervals rather than being instantaneous.
What are Kombo's published pricing tiers?
There are none. Kombo uses a platform fee plus flat per-customer connection fee model, but pricing requires a direct sales conversation. No self-serve or published pricing tier exists as of August 2026.
How complete are Kombo's write operations versus reads?
Write operations are supported and actively developed - employee creation with staffing entities was added in June 2026. Some G2 reviewers note that write-back depth for certain ATS systems is less complete than read depth. The passthrough API is available for write operations the normalized model does not cover. Verify specific write operations during evaluation.
Is Kombo suitable for AI agent workflows?
Not natively as of August 2026. Kombo does not offer a Model Context Protocol (MCP) server or native AI agent interface. AI Apply (launched May 2026) uses browser agent technology for ATS systems that block programmatic access - a different use case from AI agent orchestration. The Series A announcement referenced future plans in this area; those capabilities have not yet shipped.
Which EU-specific HR systems does Kombo cover that other platforms miss?
Notable EU-specific systems with documented Kombo coverage include Softgarden, AFAS Software, rexx systems, HeavenHR, Kenjo, PayFit, HR WORKS, and Personio. These are where Kombo's depth most clearly exceeds US-primary competitors.
How long does Kombo integration typically take?
Multiple G2 reviewers report going from signup to working integration in days. Sandbox access is available for most systems. Exception: certain enterprise ATS sandboxes (iCIMS specifically cited) require vendor-controlled approval processes that can take three to six months.
