Absence Management
Rippling
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Rippling Ireland Limited · www.rippling.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Rippling at a glance
- Vendor
- Rippling Ireland Limited
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Rippling 1.5/5, the mean of 6 judges. Rippling is an all-in-one HR, payroll, IT and finance platform from Rippling People Center Inc. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Rippling is an all-in-one HR, payroll, IT and finance platform from Rippling People Center Inc. of San Francisco, with Rippling Ireland Limited of Dublin named in the German legal notice. It is strongest at approval machinery: requests and approvals scores run 4-6, with multi-approver chains, routing by tenure and department, re-routing when the primary approver is away, and a reviewer and timestamp on every request. Payroll handover scores also run 4-6, on a DATEV-integrated, ITSG-certified German payroll and a public REST API covering leave requests, accruals and balances — though its payroll API reference sits behind sign-in. Leave policies scores sit at 2-4: accruals, balances and partial-day hours are documented, but the judges found no public information on part-time proration, carry-over with expiry, or public holidays per federal state. Weakest is sick leave and eAU at 0-1, with no public information on the eAU, certificates, continued-pay counting or child-sick days. Sovereignty scores span 0-2, with residency and subprocessors recorded as unknown; the pricing page lists modules without figures. The judges did not meaningfully split on any criterion.
Speaks for it
- Multi-approver chains, routing by tenure and department, and re-routing when the primary approver is away are all documented.
- Every leave request records a reviewer and review timestamp, with absence requests handled in the mobile app.
- A public REST API exposes leave requests, accruals and balances with scopes, bearer authentication and custom hours for partial days.
- German payroll is named as DATEV-integrated and ITSG-certified, with time and payroll claimed to run in one system without manual transfer.
- Permission profiles scope access by reporting line or department with view, edit and approve actions, and the privacy notice names Rippling as processor for customer data.
Held against it
- We found no public information on the eAU, sick certificates, six-week continued-pay counting, BEM or child-sick days.
- We found no public information on part-time proration, carry-over with expiry, public holidays per German federal state, or special and parental leave types.
- The Global Payroll API documentation requires an account sign-in, and we found no public information on mapping absence types to payroll codes, monthly period locks or webhooks.
- We found no public information on who may see a sickness reason or certificate, on retention or deletion of absence records, on access logging, or on whether Rippling AI's shared data basis excludes sickness data.
- Data residency, ownership, the contracting jurisdiction and subprocessor exposure are recorded as unknown, and the parent company sits in San Francisco.
Best for
- You want absence approvals, time tracking and payroll on one platform and manage sickness notifications through another channel.
- You have developers who will integrate leave requests, accruals and balances through a documented public REST API.
- You run German payroll through DATEV and want absence and payroll in one system, as the vendor claims.
Avoid if
- You need the eAU, continued-pay counting and child-sick days handled in the product itself — the lowest-scoring area at 0-1.
- You must verify entitlement computation for part-timers across German federal states before signing; leave policies scores run 2-4.
- You require evidenced data residency and a named subprocessor chain before go-live; sovereignty scores run 0-2 and its attributes are recorded as unknown.
The scores
| Criterion | Panel median |
|---|---|
| Entitlements & German leave rules | 1.5 of 5 |
| Requests, approvals & team calendar | 3 of 5 |
| Sick leave, eAU & continued pay | 0 of 5 |
| Payroll handover, time tracking & API | 3 of 5 |
| Health data, access & works council | 2 of 5 |
| European sovereignty | 0.5 of 5 |
Entitlements & German leave rules
Show reasoningHide reasoning
How this is scored
Whether the tool computes leave the way German and Austrian law and contracts do: entitlements per contract and working-time model, part-time proration, carry-over and expiry with the required notice, public holidays per federal state, half days and hourly leave, and special leave types.
0 — A fixed number of days per person typed in by hand; no carry-over, no proration and no public holidays.
3 — Annual entitlements and national public holidays, with carry-over as a manual adjustment and no statement on part-time or regional holidays.
5 — Entitlements per employee with automatic proration for joiners, leavers and part-time working days, public holidays per German federal state or Austrian region, half days, configurable carry-over with an expiry date, and custom leave types.
8 — Several working-time models per employee with changes over time recalculated, hourly leave, carry-over expiry with automatic notices to employees before leave lapses, special leave and parental leave types with their own rules, and entitlement changes logged.
10 — Leave law modelled and documented: entitlement rules per contract or collective agreement, statutory minimum and contractual leave kept apart where they expire differently, balances recalculated retroactively with an audit trail, and the rules a tool applies published in its help centre.
The Team Lead
There is a real leave engine behind the API — leave types, leave policies, accruals and balances, and you can book hours instead of whole days — but I found no public information on public holidays per German federal state, part-time proration, or carry-over with expiry and notice, and nothing on special or parental leave types. As it stands I cannot tell from the captured pages whether a part-timer's balance comes out right. 6 8 5
The Managing Director
The public API shows real entitlement machinery — leave accruals, balances, custom leave types and partial-day hours on start and end dates — which is more than a typed-in number per person. But I found no public information on part-time proration, public holidays per German federal state, or carry-over rules and expiry notices, and the compliance claim for 185+ countries names no German rule I could verify; with part-timers in two federal states, I cannot check a single entitlement calculation from these pages. 8 5 1 3
The Payroll Accountant
Leave types, accruals, balances and per-hour amounts on a request's start and end date are documented in the API, which covers hourly and part-day leave, but the entitlement object itself is only an id with a description. We found no public information on part-time proration, carry-over with expiry and notice, public holidays per German federal state, or special and parental leave types. Without those I cannot tell how German leave law is actually computed. 6 8 5
The Data Protection Officer
The developer pages show leave policies, leave types, accruals and balances as first-class objects, and a request can carry custom hours on its start and end dates. We found no public information on part-time proration, public holidays per German federal state, carry-over with expiry dates, or German special-leave and parental-leave types. For a German buyer the leave engine's German specifics rest on nothing more than a generic compliance-in-185-countries claim. 3 6 8 5
The HR IT Integrator
The time-off API shows leave policies, leave types, automatic accruals and balances, and partial-day leave through custom hours on the start and end dates. We found no public information on part-time proration, public holidays per German federal state or Austrian region, or carry-over with expiry and notices — the parts that make German entitlement computation lawful — so the machinery sits below what a German buyer needs. 6 8 5
The Skeptic
The leave API does expose accruals, balances, leave types, and partial days with custom hours on start and end dates, so hourly and half-day leave look computed rather than typed in. But I found no public information on carry-over and its expiry, part-time proration, public holidays per federal state or Austrian region, or special-leave rules — the entitlement model shown carries nothing but an identifier, a name and a description. 8 6 5
Requests, approvals & team calendar
Show reasoningHide reasoning
How this is scored
The everyday flow: an employee requests leave on a phone, the right person approves, a substitute is named, and the team can plan around it — judged on configurable approval chains and on what colleagues are allowed to see.
0 — Leave requested by email or in a shared calendar; no approval step and no record of who approved.
3 — Requests with a single approver and a team calendar, but no substitutes, no blocking rules and every absence reason visible to everyone.
5 — Mobile requests and approvals, approvers per team or department, substitutes named on the request, a team calendar that shows absence without the reason, email or push notifications, and calendar sync.
8 — Multi-level approval chains, minimum staffing rules or blackout periods, delegation while the approver is away, configurable calendar visibility per role, Microsoft Teams or Slack integration, and every request, approval and cancellation logged.
10 — Approval logic that matches a real organisation: rules per location, team and leave type, conflicts checked against staffing and shift plans before approval, a complete history per request, and reporting on pending and overdue approvals.
The Team Lead
Mobile absence requests, approvals routed by department or reporting line, multi-approver chains with re-routing when the approver is themselves away, and every request carrying who reviewed it and when — that is solid machinery. But I found no public information on a team calendar showing who is away, on naming a substitute on the request, or on minimum-staffing warnings before approval, which are exactly what stops me finding out about clashes too late. 3 7 8 11
The Managing Director
The approval engine is strong: multi-approver logic, routing by department and tenure, automatic re-routing when the primary approver is away, mobile absence requests, and API fields recording who reviewed a request and when. What I found no public information on is the planning half — a shared team calendar, what colleagues may see of an absence, named substitutes on the request, or staffing and blackout rules — so I can judge the approvals but not the team planning around them. 11 7 8 3
The Payroll Accountant
Mobile absence requests, approval routing by department and tenure, multi-approver chains and re-routing when the primary approver is away are all documented, and every leave request carries a reviewer and review timestamp. On the planning side we found no public information on a team calendar, substitutes named on the request, or what colleagues are allowed to see. The approval engine is solid; the calendar half of the criterion is silent. 3 7 8 11
The Data Protection Officer
The approval machinery is real: multi-approver logic, re-routing when the primary approver is on vacation, routing by department and tenure, reminders, and each leave request carrying a reviewer and a review timestamp, with mobile requests in the app. We found no public information on the team calendar side — substitutes named on the request, what a colleague may see about another's absence, or calendar sync — and that visibility question is the one my lens weighs heaviest. 3 7 8 11
The HR IT Integrator
Multi-approver logic, routing by employee attributes, re-routing when the primary approver is on vacation, and approval scopes by reporting line or department are all documented, and the leave-request API records reviewer and review timestamp with statuses from pending to canceled. The mobile app handles requesting absence. We found no public information on substitutes, a team calendar, calendar sync or notifications specific to leave requests, which is the planning half of the everyday flow. 3 7 8 11
The Skeptic
Mobile absence requests, multi-approver chains, attribute-based routing by tenure and department, re-routing when the primary approver is away, and a reviewer with timestamp on every leave request are all documented. What I found no public information on is the planning half: a team calendar, calendar sync, or naming a substitute on the request. 3 7 11 8
Sick leave, eAU & continued pay
Show reasoningHide reasoning
How this is scored
Sick notifications and the German electronic certificate of incapacity: whether the tool retrieves the eAU from the health insurer itself or through a named payroll system, how sick days are counted towards the six-week continued-pay and BEM thresholds, and how child-sick days and certificates from private insurance are handled.
0 — Sickness recorded as another leave type with no word on the eAU, certificates or thresholds.
3 — A sick-leave type with a document upload, and "eAU" mentioned without saying who retrieves it or how.
5 — Sick notification by the employee in the app, the eAU retrieval process documented — by the tool itself or via a named payroll system — with the retrieval status visible to HR, and child-sick days as a separate type.
8 — eAU retrieval from the statutory health insurers documented end to end with the certified software named, retrieval results written back to the absence, sick days counted towards the six-week continued-pay limit per illness, BEM thresholds flagged to HR only, and paper certificates for privately insured employees handled.
10 — Sick leave handled as the regulated process it is: eAU retrieval automated with error and follow-up handling, continued-pay and sickness-benefit transitions tracked, BEM invitation workflow supported, reasons and documents restricted to named roles, and the whole process documented in the help centre.
The Team Lead
The captured pages are silent on the electronic certificate of incapacity, on who retrieves it, on certificates, and on counting sick days towards the six-week continued-pay limit; sickness would at best sit among the custom leave types. I found no public information on child-sick days either. 8 12
The Managing Director
I found no public information on the eAU, sick certificates, the six-week continued-pay counting, BEM or child sick days; sickness appears at most as a generic leave type among the absence modules. For me that still means phoning health insurers, so this sits at the floor. 8 12 3
The Payroll Accountant
The captured pages say nothing about sick notifications, the eAU, certificates, the six-week continued-pay limit, BEM or child-sick days; sickness is not even shown as a leave type. I found no public information on any of it, and that silence is worth the bottom of the scale here. Absences would reach payroll without an eAU result attached or continued pay counted per illness. 3 12
The Data Protection Officer
Sickness appears nowhere as its own process: no word on the eAU, on certificates, on how sick days count toward the six-week continued-pay limit, or on child-sick days. Leave types and leave requests exist as generic objects in the API, but every regulated step of German sick leave is undocumented. A sick day is special-category data; a buyer cannot learn from these pages how the product treats it. 8 12
The HR IT Integrator
The captured absence and time-tracking pages and the time-off API say nothing about sickness: we found no public information on sick notifications, the eAU and who retrieves it, six-week continued-pay thresholds, BEM, or child-sick days. With nothing on the regulated process at all, this sits at the bottom of the scale. 3 8
The Skeptic
I found no public information on sick notifications, the eAU, who retrieves a certificate, continued-pay thresholds, BEM or child-sick days anywhere — not on the time-and-absence product page and not in the leave API reference. That is the bottom of the scale: the regulated sick process is simply not spoken to. 3 8
Payroll handover, time tracking & API
Show reasoningHide reasoning
How this is scored
Getting absences into the payroll run with the right codes and keeping balances consistent with time tracking: exports or integrations for the payroll systems German companies use, time-account interaction, and an API.
0 — No export beyond a screen list; absences are retyped into payroll.
3 — A CSV or Excel export of absences per month, with no named payroll system and no API.
5 — A documented export or integration for DATEV (LODAS or Lohn und Gehalt) or another named German payroll system, absence types mapped to payroll codes, and a documented API.
8 — Several named payroll integrations, absence and overtime balances shared with time tracking, configurable payroll codes per leave type, monthly closing that locks past periods, webhooks, and an API with published limits.
10 — Payroll handover that closes the month: absences, sick days and eAU results delivered to payroll in its own format with corrections flagged, a period lock with an audit trail, a versioned API with a deprecation policy, and the full absence history exportable at contract end.
The Team Lead
German payroll with DATEV integration and ITSG certification is named, time and payroll sit in one system with no manual transfer, and a documented REST API covers leave requests, accruals and balances with scopes and pagination. What holds it back is that the payroll API documentation is gated behind sign-in, and I found no public information on payroll codes per leave type, monthly period locks or webhooks. 1 3 9 5
The Managing Director
The German pages name a DATEV integration and an ITSG-certified German payroll with time and payroll in one system, and the public absence API covers leave requests, accruals and balances. How absence types map to payroll codes is not shown — the Global Payroll API documentation sits behind an account sign-in — and I found no public information on period locks, corrections or webhooks. 1 3 8 9
The Payroll Accountant
A DATEV-integrated, ITSG-certified German payroll is claimed on the homepage, time and payroll run in one system with no manual transfer, and leave requests, accruals and balances are exposed through a documented API with bearer-token authentication. We found no public information on mapping absence types to payroll codes, a monthly period lock, webhooks or published API limits, and the payroll API reference itself sits behind an account sign-in. Good enough to hand over; not enough to close the month with a trail. 1 3 8 9 5
The Data Protection Officer
German payroll is claimed ITSG-certified and DATEV-integrated, time and payroll sit in one system without manual transfer, and the public REST API covers leave requests, accruals and balances with scopes and bearer authentication. We found no public information on absence-to-payroll code mapping, monthly period locks, webhooks or published API limits. The global payroll API documentation requires signing in with an account, which a buyer cannot audit before contracting. 1 3 8 9 5
The HR IT Integrator
The German payroll offering names DATEV integration and ITSG certification, time and payroll are claimed to sit in one system without manual transfer, and a public REST API covers leave requests, accruals and balances with scopes, bearer auth and pagination. The payroll API documentation itself sits behind a Rippling account sign-in, and we found no public information on webhooks, mapping leave types to payroll codes, or period locking with an audit trail — so the handover is named but not documented end to end. 1 3 8 9
The Skeptic
"DATEV-integriert" stands as one badge word on the German homepage — an integration named, not shown — with no public information on export format or how absence types map to payroll codes. The public REST API with leave-request, accrual and balance endpoints is genuinely documented, though the Global Payroll API documentation sits behind an account sign-in, and I found no public information on webhooks, published API limits or a period lock for monthly closing. 1 3 8 9
Health data, access & works council
Show reasoningHide reasoning
How this is scored
What the tool does with data that is health data in law: who can see a sickness reason or certificate, how long absence records are kept, whether access is logged, and whether the vendor documents what a works agreement on absence recording needs.
0 — Nothing stated about who sees sick data or how long absences are kept.
3 — Roles for employees, managers and admins, but sickness reasons and documents visible to managers by default, and no retention setting.
5 — Sick-leave reasons and certificates restricted to HR by configurable permissions, colleagues see only "absent", retention or deletion of absence records configurable, and a DPA available.
8 — Field-level permissions per leave type, access to health-related records logged, retention rules per record type with automatic deletion, employees able to see their own records, and documentation aimed at works councils or a works agreement.
10 — Health data governed and evidenced: Art. 9 GDPR processing explained per feature, deletion runs logged and reportable, audit logs exportable, no analytics or AI features run on sickness data without explicit configuration, and the vendor publishing a template or checklist for the works agreement.
The Team Lead
Permission profiles with scope, actions and data-level access, plus a privacy policy describing the vendor as processor for customer data, are real and granular. But I found no public information on who may see a sickness reason or certificate, on retention and deletion of absence records, on access logging, or on any documentation aimed at a works council. 11 12
The Managing Director
There is a serious permissions architecture — scope by reporting line or department, access per app, actions like view, edit and approve — and the privacy notice names Rippling as processor for customer data. But I found no public information on retention or deletion of absence records, access logging, or who may see a sickness reason; and Rippling AI is marketed across the shared employee data source with no public statement on whether sickness data is included. 11 7 12 1
The Payroll Accountant
Permission profiles carry scope, data access and actions like view, edit and approve, attached to attributes rather than persons, and the privacy policy names Rippling as processor for customer data. On the health side we found no public information on restricting sick reasons and certificates to named roles, retention or deletion of absence records, access logging, or works-council documentation. Granular general permissions, but the special-category specifics are unverifiable from these pages. 11 12
The Data Protection Officer
The permission model is genuinely granular — profiles bound to attributes rather than persons, scoped to a reporting line or a whole department, with view, edit and approve actions — yet we found no public information on who may see a sickness reason or certificate, on retention or deletion of absence records, on access logging, or on a data-processing agreement. Nothing is aimed at works councils or a works agreement. And the AI features are marketed as running across all modules on one shared employee-data basis, including burnout prevention, with no public word on whether sickness data is fenced off from them — exactly the question a works agreement will ask. 1 3 11 12
The HR IT Integrator
Permission profiles govern scope, per-app access and actions such as view, edit and approve, tied to attributes rather than persons with a preview of access changes, and the privacy notice states Rippling acts as processor for customer data. We found no public information on whether sickness reasons and certificates are restricted to HR, on retention or deletion of absence records, on access logging, or on documentation for a works agreement — the health-data questions themselves are unanswered. 11 12
The Skeptic
The permission machinery is real — profiles with scope over a reporting line or department, per-app access, view/edit/approve actions, and a processor statement in the privacy policy — but all of it is about permissions in general, not health data. I found no public information on who may see a sickness reason or certificate, on retention or deletion of absence records, on access logging, or on anything addressed to a works council, while Rippling AI is promoted as working across all areas on one shared data basis with no word on excluding health data. 11 12 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where absence and sickness data lives, who the contracting entity is, and who the subprocessors are — including email, push-notification and support providers. Independently sourced by the sovereignty pipeline.
0 — Non-EU vendor and contracting entity, hosting unstated, and subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — email, push notifications, analytics or support — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, and a DPA that covers sickness data as special-category processing.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, and certification published.
The Team Lead
The German imprint names Rippling Ireland Limited in Dublin, but I found no public information on hosting location, data residency, or the subprocessor chain, and the company behind the product is American. Until residency and subprocessors are published, I have to treat the location of absence and sickness data as unknown. 4 12
The Managing Director
The company is American (Rippling People Center Inc., San Francisco) and I found no public information on hosting location or any named subprocessor, including email or support providers. The German imprint names Rippling Ireland Limited of Dublin as the European entity, but the captured pages do not confirm which entity I would actually contract with, so my employees' absence data has no evidenced European home. 4 12
The Payroll Accountant
Provenance is a San Francisco company with Rippling Ireland Limited named in the German imprint, and the captured pages state nothing about where absence and sickness data is hosted or which subprocessors — email, push, support — sit in the chain. No subprocessor list, no data-residency statement, no certification captured. That places it between the floor and the middle of the scale. 4 12
The Data Protection Officer
The group sits in San Francisco, the European entity is named only in the German imprint, and the captured pages leave data residency, ownership and every subprocessor — including whoever would deliver a push notification saying an employee is ill — unnamed. No EU hosting commitment, no subprocessor list with locations, and no certification is published. From public pages a buyer cannot tell where absence and sickness data would live or who else touches it. 4 12
The HR IT Integrator
Provenance shows a San Francisco parent with the German legal notice naming Rippling Ireland Limited of Dublin as the European entity, but the jurisdiction is not confirmed on the vendor's own captured pages, and we found no public information on data residency or on any subprocessor, including email, push notifications and support. The captured privacy notice states processor and controller roles without naming hosting or locations, which leaves the chain opaque. 4 12
The Skeptic
Provenance is a San Francisco company, and the capture could not confirm contracting entity, ownership, hosting or data residency on the vendor's own pages; the German imprint names a Dublin entity, but that could not be confirmed as captured. I found no public information on any subprocessor — not even for email or push notifications — so nothing European is evidenced end to end. 4 12
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per employee or per user, which features (eAU, payroll export, time tracking) sit in which tier, minimum users and the minimum term.
0 — No public prices at all; every tier is a sales conversation.
3 — A starting price exists, but the pricing basis or which features it covers is unstated — the invoice is unknowable.
5 — Tier prices public with the pricing basis given, but at least one commonly needed piece (eAU, payroll export, time tracking, extra admins) is unpriced or "on request".
8 — Every tier priced publicly with its basis, add-on prices listed, minimum users, minimum term and VAT treatment given.
10 — Complete price computability: the annual invoice derivable for a given headcount and feature set, with every add-on, setup fee and overage published.
The Team Lead
The captured pricing page lists module groups without a single figure — no price, no pricing basis, no minimum users and no term — and the question of buying modules separately appears only as an unanswered FAQ. Everything runs through a demo request. 1 2 7
The Managing Director
The captured pricing page lists module names and support channels but not a single price figure, and the only buying information is an FAQ topic about buying modules separately plus a demo request. From these pages I cannot compute even a rough annual invoice for forty people. 2 12 1
The Payroll Accountant
The captured pricing page lists modules and help-centre links but shows no figures, and the only pricing-adjacent text is an FAQ question about buying modules separately, with no answer captured. We found no public information on per-employee prices, tiers, minimum users, minimum term or VAT treatment. A buyer cannot compute any invoice from this. 1 2
The Data Protection Officer
The captured pricing page names module groupings and even asks whether modules can be bought separately, but not one figure appears — no per-employee price, tier price, minimum users, minimum term or VAT treatment. Numbers come only through a demo request or account sign-in. From public pages alone the annual invoice is not computable. 1 2 1
The HR IT Integrator
The pricing page capture contains no price figures at all, and the only pricing-related item anywhere is an FAQ heading asking whether modules can be bought separately, with no answer in the captures. A buyer cannot derive any annual cost from what is published; every tier is a sales conversation. 1 2
The Skeptic
The captured pricing page shows module lists, not numbers: no price per employee, no tier price, no minimum users and no term appears anywhere, and even "can I buy individual modules separately" is an unanswered FAQ topic. With a demo request as the only path shown, the annual invoice is not computable from public pages. 2 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Rippling
Is Rippling European?
No. whats-best.ai classifies Rippling as Rest of world.
Where does Rippling store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Rippling have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Rippling?
As of 15 Oct 2026, the panel rates Kenjo (3/5), flair (2.5/5) and HRlab (2.5/5) highest among the other 16 Absence Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Kenjo (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Rippling alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 22 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 12 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.rippling.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 2 Pricing page www.rippling.com Checked 13 Oct 2026 Details →
- 3 Time and absence www.rippling.com Checked 13 Oct 2026 Details →
- 4 Legal notice www.rippling.com Checked 13 Oct 2026 Details →
- 5 Entitlements & German leave rules — found from sitemap developer.rippling.com Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 6 Entitlements & German leave rules — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
- 7 Requests, approvals & team calendar — found from sitemap www.rippling.com Checked 13 Oct 2026 Details →
- 8 Requests, approvals & team calendar — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
- 9 Payroll handover, time tracking & API — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
- 10 Payroll handover, time tracking & API — found from sitemap developer.rippling.com Checked 13 Oct 2026 Details →
- 11 Health data, access & works council — found from sitemap www.rippling.com Checked 13 Oct 2026 Details →
- 12 Health data, access & works council — found from sitemap www.rippling.com Checked 13 Oct 2026 Details →