Calamari
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Calamari sp. z o.o. sp.k. · www.calamari.io
Compare with Timetastic → 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.
Calamari at a glance
- Vendor
- Calamari sp. z o.o. sp.k.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Calamari 2/5, the mean of 6 judges. Calamari is an absence-management suite from Calamari sp. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Calamari is an absence-management suite from Calamari sp. z o.o. sp.k., Warsaw, covering time off, time and attendance, core HR, performance and scheduling. It scores best on leave policies: the help centre documents proration methods with rounding options, seniority-based entitlements such as 20 days under five years and 26 days from five, carry-over caps with automatic expiry, and hourly absence types — though the judges found no public information on public-holiday calendars per German federal state. Requests and approvals score 4-6 on web, mobile and Slack requests with per-absence-type fields. The weak spots are stark: sick leave and eAU scored 0, with no public information on sick-leave recording, eAU retrieval, continued-pay counting or child-sick days; payroll handover scored 2, with no public information on an export to DATEV or any named payroll system. Sovereignty splits 3-4 over the unstated AWS hosting region and the vendor's own ISO 27001 still in preparation. Pricing: 2 USD per employee/month, billed yearly by default, with a 14-day trial requiring no credit card.
Speaks for it
- Leave policies score the bench's best range on documented proration methods, rounding options, seniority- and contract-type-based entitlements, and carry-over caps with automatic expiry
- Requests run from web, mobile or Slack, with reason, substitute, comment and attachment fields settable as required, optional, hidden or disabled per absence type
- Five account roles run from employee to administrator, with encrypted modification-protected logs of every profile change and periodic access audits
- Time & Attendance sits in the same suite as time off, bringing timesheets and eight clock-in methods under one product
- One plan is priced publicly at 2 USD per employee/month, billed yearly by default, with a 14-day trial requiring no credit card
Held against it
- Sick leave and eAU scored 0, with no public information on sick-leave recording, eAU retrieval, continued-pay counting or child-sick days
- Payroll handover scored 2, with no public information on DATEV or any named payroll export, absence-to-payroll-code mapping or period locking
- The captured pages do not state the AWS hosting region, no subprocessor list is published, and the vendor's own ISO 27001 is in preparation while only the hosting provider's certifications are cited
- No public information on public-holiday calendars per German federal state, part-time proration or automatic notices before carried-over leave lapses
- The annual invoice is not computable from the public pages: the customized plan and the SAML SSO add-on carry no published price, with no public information on minimum users, minimum term or VAT treatment
Best for
- You need a leave engine that prorates joiners and leavers, sets entitlements by seniority and contract type, and caps carry-over with automatic expiry
- Your team requests time off from the web, mobile or Slack and you want a substitute named on every request
- You want absences and time tracking in one product, with timesheets and eight clock-in methods beside time off
- You want to pilot before committing, with a 14-day trial that requires no credit card and one published price of 2 USD per employee/month
Avoid if
- You need sick-leave recording, eAU retrieval, six-week continued-pay counting or child-sick days handled as a regulated process — this criterion scored 0
- Your payroll run depends on a DATEV or other named payroll export, absence-to-payroll-code mapping or a month-end lock — payroll handover scored 2
- You must settle the hosting region and subprocessors, or need a DPA in hand before signing — ask the vendor: the public pages we read do not show it
- Your staff sit across German federal states and your policy turns on per-state public-holiday calendars or automatic notices before carried-over leave lapses, on which the judges found no public information
The scores
| Criterion | Panel median |
|---|---|
| Entitlements & German leave rules | 3 of 5 |
| Requests, approvals & team calendar | 3 of 5 |
| Payroll handover, time tracking & API | 1 of 5 |
| Health data, access & works council | 2 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2 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 — Not a leave tool; entitlements and leave balances cannot be kept in the product.
3 — Annual entitlements per employee with remaining balances, public holidays, and custom leave types.
5 — Entitlements prorated for part-time working days and for joiners and leavers, public holidays per German federal state or Austrian region, and configurable carry-over with an expiry date.
8 — Several working-time models per employee with changes over time recalculated, half days and hourly leave, carry-over expiry with automatic notices to employees before leave lapses (as the BAG requires), special 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
The help centre documents a real entitlement engine: accrual rules restricted to contract types such as a '20 days contract', seniority-based rules (20 days under five years, 26 days from five), several proration methods for joiners with rounding to half days, carry-over caps with expiry after a set period, and hour-based absence types. We found no public information on public holidays per German federal state or automatic notices to employees before carried-over leave lapses. 4 5
The Managing Director
The configuration guide documents a genuinely careful engine: proration by days, full or partial months with rounding to whole or half days, hourly absence types, entitlement rules per contract type and seniority band, and carry-over capped in days or hours with automatic expiry. That handles joiners and leavers properly, but we found no public information on public-holiday calendars per German federal state, on prorating part-time working days, or on automatic notices to employees before carried-over leave lapses — and with staff in two federal states, the regional-holiday question decides where I land. 4 5 2
The Payroll Accountant
Proration is documented with three methods and rounding options for joiners and leavers, carry-over is configurable with a limit and an expiry that deducts automatically, and entitlement rules can follow contract types and seniority (for instance 20 or 26 days) — but we found no public information on public holidays per German federal state or automatic notices to employees before carried-over leave expires. 4 5 2
The Data Protection Officer
The help centre documents entitlement mechanics in real depth: proration for joiners with three calculation methods and rounding to whole or half days, accrual restricted to contract types and seniority bands (20/26 days per year), carry-over caps with an expiry that deducts unused balance automatically, and absence types configurable in days or hours. We found no public information on public holidays per German federal state, part-time proration, or notices to employees before carried-over leave lapses, so I stop below the higher levels. 4 5 2
The HR IT Integrator
The help centre documents real entitlement mechanics: proration formulas for joiners with four rounding modes, seniority-based rules matching the German 20/26-day pattern, accrual restricted to contract types, carry-over caps with configurable automatic expiry, and hourly accounting with hours-per-day conversion. We found no public information on public holidays per German federal state or on automatic notices to employees before carried-over leave lapses. 4 5
The Skeptic
The help centre shows genuine configuration depth: proration with worked examples and rounding to half days, carry-over limits with an expiry rule that deducts lapsed days automatically, entitlements by seniority and by contract type, hourly leave and negative-balance limits. What the captured pages do not show is public holidays per German federal state, an automatic notice to employees before carried-over leave lapses, or working-time models recalculated retroactively — the deduction is evidenced, the BAG-critical warning is not. 4 5 2
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 — No request flow; absences are entered by an administrator only.
3 — Leave requests with an approval by a manager, and a shared team calendar of absences.
5 — Requests and approvals from a mobile app, approvers configurable per team or department, email or push notifications, and a team calendar that syncs with Outlook or Google Calendar.
8 — Multi-level approval chains, substitutes named on the request, minimum staffing rules or blackout periods, delegation while the approver is away, calendar visibility per role that hides the absence reason, 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
Employees request leave on the web, mobile or Slack, picking the leave type, naming a substitute and leaving comments, and the substitute, reason, comment and attachment fields can be set required, optional, hidden or disabled per absence type — so I can insist a substitute is named every time. Five account roles from direct manager to administrator and an absences overview calendar are shown. We found no public information on multi-level approval chains, minimum-staffing warnings, delegation while an approver is away, or calendar visibility that hides the reason from colleagues. 3 4 2 6
The Managing Director
The everyday flow I need is evidenced: employees request time off on the web, the mobile app or Slack and can name a substitute right on the request, with account roles from employee through team and direct manager up to administrator. We found no public information on multi-level approval chains, delegation while an approver is away, email or push notifications, or calendar sync with Outlook and Google, so I would be buying the core flow and improvising the rest. 3 1 6
The Payroll Accountant
Requests run from the web, mobile or Slack with a substitute, reason, comment and attachments configurable per absence type, and defined roles run from direct manager to company manager; we found no public information on multi-level chains, staffing or blackout checks, or calendar visibility that hides the reason, which keeps this just past the standard mobile-and-approval level. 3 4 2 6
The Data Protection Officer
Requests run from web, mobile and Slack with a substitute selectable and per-absence-type form fields, five account roles including Team manager and Direct manager imply per-team approval, and restrictions such as advance notice or maximum days per week can block or warn. We found no public information on multi-level approval chains, staffing or blackout rules, or a log of every approval and cancellation. 3 4 1 6
The HR IT Integrator
Requests come from web, mobile or Slack with a substitute on the request, and the reason, substitute, comment and attachment fields can each be required, optional, hidden or disabled per absence type, with restriction rules that block or warn. Roles run from administrator down to direct manager, but we found no public information on multi-level approval chains, calendar sync details or approval history reporting. 3 4 6
The Skeptic
Requests run from web, mobile and Slack with a substitute field, and the request form's reason, substitute, comment and attachment fields can be made required, optional, hidden or disabled per absence type; five account roles exist including team and direct manager. We found no public information on approval notifications, multi-level chains, delegation, calendar sync to Outlook or Google, or calendar visibility per role that hides the absence reason. 3 4 6
Sick leave, eAU & continued pay
n/r
n/r
n/r
n/r
n/r
n/r
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 (EFZG § 3) and BEM (SGB IX § 167) thresholds, and how child-sick days and certificates from private insurance are handled.
0 — No sick-leave recording; the product handles holiday only.
3 — Sick leave recorded as its own absence type, with a certificate uploaded by the employee.
5 — Sick notification by the employee in the app, eAU retrieval offered with the route stated (by the tool itself or via a named payroll system), 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 status and 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 not rated — no public information
We found no public information on sick-leave recording, electronic certificates of incapacity, continued-pay counting or child-sick days on any page we read; the captures cover leave-policy configuration, the leave-management pages, pricing and security only. 3 4 2 6
The Managing Director not rated — no public information
We found no public information on sick-leave recording, eAU retrieval, continued-pay tracking or child-sick days. The leave-configuration guide, the leave-management page and the pricing page describe holiday, attendance and core-HR capabilities, and sickness handling is not among the capabilities they state. 3 4 2
The Payroll Accountant not rated — no public information
We found no public information on sick leave recording, eAU retrieval, counting towards the six-week continued-pay limit, or child-sick days on the captured pages; the leave policy guide, leave management page, pricing page and security page cover holidays, attendance and platform security only. 3 4 2 6
The Data Protection Officer not rated — no public information
We found no public information on sick-leave recording, eAU retrieval, six-week continued-pay counting, BEM thresholds, child-sick days or certificate handling on any captured page, including the leave-management pages, the pricing page, the security page and the help-centre article on leave policies. Absence types are configurable, but we found no public information on sickness being handled as the regulated process it is, so I will not guess a score for it. 3 4 2 6
The HR IT Integrator not rated — no public information
We found no public information on sick-leave handling: nothing on sick notifications in the app, certificate uploads, eAU retrieval by any route, child-sick days, or counting sick days towards the six-week continued-pay threshold. The leave-configuration and product pages we read do not address sick leave. 4 2
The Skeptic not rated — no public information
We found no public information on sick-leave handling: the captured help article on leave policies, the leave-management pages, the pricing page and the security page say nothing about a sickness absence type, certificate upload, eAU retrieval, continued-pay counting, child-sick days or privately insured employees. 4 2 3
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 — A closed tool with no export, integration or API.
3 — A CSV or Excel export of absences per month for the payroll office.
5 — An export or integration for DATEV (LODAS or Lohn und Gehalt) or another named payroll system, and either a documented API or absences shared with a named time-tracking tool.
8 — Several named payroll integrations, absence types mapped to configurable payroll codes, absence and overtime balances shared with time tracking, 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
An API and integrations with Slack, Microsoft 365, Google, Jira, Asana and Basecamp are listed, and the suite carries its own time and attendance module, so absences and time data can live in one product. We found no public information on exports or integrations for payroll systems, absence-to-payroll-code mapping, monthly period locks, webhooks or published API limits. 2 6
The Managing Director
An API is listed among the published integrations and time tracking sits in the same product with timesheets and eight clock-in methods, so absences and worked hours at least live under one roof. We found no public information on exports to DATEV or any other named payroll system, on mapping absence types to payroll codes, month-end locking or webhooks — and I remain personally liable for the payroll run. 2 6
The Payroll Accountant
An API is listed alongside Slack, Microsoft 365, Google, Jira, Asana and Basecamp, and the vendor's own time and attendance module with timesheets and clock-in sits beside time off; we found no public information on a DATEV or other named payroll export, absence types mapped to payroll codes, or a monthly closing that locks past periods, so nothing here tells me how absences reach the payroll run. 2 6
The Data Protection Officer
The captured pages list an API and integrations with Slack, Microsoft 365, Google, Jira, Asana and Basecamp, and time tracking sits in the same product as absences. We found no public information on any export or integration with a named payroll system such as DATEV, on absence-to-payroll-code mapping or on a period lock, so the payroll side of the handover is not established by this evidence. 1 2 6
The HR IT Integrator
The integration pages name an API alongside Slack, Microsoft 365, Google, Jira, Asana and Basecamp, but we found no public information on DATEV, Lohn und Gehalt or any other payroll connector, no CSV export for payroll, no webhooks and no published API limits. Time & Attendance and Time Off are modules of the same suite, so clock-in data and absences sit in one product, though balance reconciliation with an external time system is not described. 1 2 6
The Skeptic
An API appears in the integration list and the vendor's own time-and-attendance module with timesheets and eight clock-in methods shares time off with scheduling, but no captured page names a payroll system, an export format or payroll codes — no DATEV, no LODAS, no CSV. That is an API plus native time tracking, not a payroll handover. 1 2
Health data, access & works council
Show reasoningHide reasoning
How this is scored
What the tool does with data that is health data in law (GDPR Art. 9): 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 — The vendor describes every absence and its reason as visible to all users, with no roles.
3 — Roles for employees, managers and administrators that govern who sees absence data.
5 — Sickness reasons and certificates restricted to HR or named roles, colleagues shown only that someone is absent, and a data processing agreement offered.
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
Five account roles from employee to administrator govern who sees data, logs are encrypted and protected from modification, every employee-profile modification is logged, access audits run periodically, and a DPA appears in a customized-plan offer. We found no public information on restricting sickness reasons or certificates to named roles, retention rules with automatic deletion, or documentation aimed at works councils. 6 2 6
The Managing Director
Documented basics are real: distinct account roles from employee to administrator, encrypted tamper-proof logs of every profile change, periodic access audits, and a DPA available with the custom plan; the reason field on a request can also be set hidden or disabled per absence type. We found no public information on restricting sickness reasons and certificates to named roles, on retention and automatic deletion of absence records, or on any works-council or works-agreement documentation. 4 6 2 6
The Payroll Accountant
Account roles from employee to administrator govern visibility, the reason field on a request can be hidden per absence type, every profile modification is logged and encrypted, and a data processing agreement is offered; we found no public information on retention rules with automatic deletion, works-council documentation, or restrictions on sickness records. 6 4 2
The Data Protection Officer
Five account roles govern who sees absence data, a data processing agreement is offered under custom contracts, logs are encrypted and protected from modification, each client sits in its own database, and access is audited periodically. We found no public information on who may see a sickness reason or certificate, retention and deletion periods per record type, or documentation aimed at a works council — the Art. 9 questions I ask first. 6 2 6
The HR IT Integrator
Five account roles are published, the reason field can be hidden per absence type, logs are encrypted and protected from modification, access audits run periodically, and SAML SSO with auth logs exists as an add-on. A data processing agreement appears only as "Custom contracts & DPA" in the customized plan, and we found no public information on retention rules, employees viewing their own records, or works-agreement documentation. 4 6 2 6
The Skeptic
Five account roles govern access, an access-management process with periodic audits is described, and every employee-profile modification is logged and encrypted. But we found no public information on restricting sickness reasons or certificates to named roles, retention or deletion rules, employees viewing their own records, or any documentation aimed at a works council; the only data processing agreement mention is 'Custom contracts & DPA' inside an enterprise offer. 6 6 2
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; dimensions the evidence does not establish are unknown, not non-European.
0 — Vendor, contracting entity and hosting all shown to be outside the EU, with no data processing agreement offered.
3 — A privacy policy and a data processing agreement offered, with hosting or the contracting entity outside the EU or not established.
5 — EU hosting stated and an EU contracting entity or EU representative, with a data processing agreement offered.
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: European ownership, entity, hosting and every subprocessor, and certification (ISO 27001, BSI C5 or equivalent) published.
The Team Lead
Hosting on Amazon Web Services is named, GDPR compliance is stated, and a DPA is offered within a custom plan, but the captured pages do not state where data is hosted, do not establish the contracting entity, and publish no subprocessor list. The vendor's own ISO 27001 certification is described as in preparation, while the hosting provider's ISO 27001, SOC 2 and SOC 3 certifications are cited. 6 2 6
The Managing Director
The contracting vendor is a Polish company in Warsaw, the apps run on Amazon Web Services with the hosting provider certified ISO 27001 while the vendor's own ISO 27001 is still in preparation, and a DPA is offered with the custom plan. We found no public information on the hosting region, on subprocessors and their locations, or on whether the DPA treats sickness data as special-category processing, so I cannot yet confirm where my data would sit. 2 6
The Payroll Accountant
The vendor identifies as a Polish company registered in Warsaw, a data processing agreement is offered as a custom contract in the enterprise plan, and the apps are hosted on Amazon Web Services with GDPR compliance claimed — but the captured pages do not state where the data is hosted, the vendor's own ISO 27001 certificate is still in preparation, and only the hosting provider's certifications are named. 2 6
The Data Protection Officer
Hosting is stated as Amazon Web Services with no region published on the captured pages, a data processing agreement is available on request, and the vendor's own ISO 27001 certification is described as in preparation while the published ISO 27001, SOC 2 and SOC 3 certificates belong to the hosting provider. We found no public information on data residency, the contracting entity's establishment or a subprocessor list, including who delivers the push and email notifications. 6 2 6
The HR IT Integrator
The provenance shows a Warsaw entity, hosting runs on Amazon Web Services, and the hosting provider is certified with ISO 27001, SOC 2 and SOC 3 while the vendor's own ISO 27001 is stated to be in preparation. The hosting region is not confirmed on the vendor's own captured pages, and the data processing agreement is offered only on request within a custom offer, with no subprocessor list published. 2 6
The Skeptic
The contracting entity is Calamari sp. z o.o. sp.k. in Warsaw, Poland, and a data processing agreement is offered on request; hosting is placed at Amazon Web Services with no region stated, so data residency remains unestablished on the vendor's own pages. The vendor's own ISO 27001 is 'in preparation' — only the hosting provider's certifications are cited — and we found no public information on subprocessors or their locations. 6 2
Pricing transparency
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 public "from" price, a free tier, or one priced tier, with the rest on request.
5 — Prices for each tier public with the billing period (per month or per year) and the pricing basis (per employee or per user).
8 — Every tier priced publicly with its basis, which tier includes eAU, payroll export and time tracking stated, 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
One plan is publicly priced at 2 USD per employee/month, billed yearly, with a free 14-day trial requiring no card, and a customized plan is available on request. We found no public information on which tier includes eAU, payroll export or time tracking, the price of add-ons such as the SAML SSO add-on, minimum users, minimum term or VAT treatment. 2 3 2
The Managing Director
One price is public and well specified: 2 USD per employee per month, with yearly billing as the default and a 14-day trial that needs no card. The custom plan sits on request, and we found no public information on the price of the SAML SSO add-on, on which features sit in which tier, on minimum users, the minimum term or VAT treatment — so the real annual invoice is not computable from the public pages. 2 3 2
The Payroll Accountant
One tier is priced publicly at 2 USD per employee per month with yearly billing as the default and a 14-day trial without a credit card, while everything else is a customized plan on request; the pages name no minimum users, minimum term or VAT treatment, and the SAML single sign-on add-on carries no published price, so a buyer cannot compute the annual invoice. 3 2 2
The Data Protection Officer
One tier is published at 2 USD per employee/month, billed yearly by default, with a card-free 14-day trial, while the customized plan (custom contracts & DPA, adjusted payment methods) is priced on request. We found no public information on which tier includes which features, VAT treatment, minimum users or the minimum term, so the annual invoice is not computable from these pages alone. 2 3 2
The HR IT Integrator
One tier is priced publicly at 2 USD per employee/month with yearly billing stated as the default, plus a free 14-day trial with no credit card. The customized plan and the SAML SSO add-on carry no published price, and we found no public information on minimum users, minimum term or VAT treatment. 2 3 2
The Skeptic
One tier is priced publicly at 2 USD per employee per month with a yearly billing default stated, alongside a Customized Plan on request and a free 14-day trial without a credit card. A buyer still cannot compute the annual cost: we found no public information on which modules sit in which tier, the price of the SAML SSO add-on, minimum users, minimum term or VAT treatment. 3 2 2
European sovereignty — proven facts
1 of 6 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
On request
unverified
Why unverified?The pricing page only lists 'Custom contracts & DPA' within an enterprise offer without publishing the agreement or stating that it can be concluded online. |
0/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Calamari
Is Calamari European?
Yes. whats-best.ai classifies Calamari as EU-Made.
Where does Calamari store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Calamari have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Calamari?
As of 18 Nov 2026, the panel rates HRlab (3/5), Kenjo (3/5) and flair (3/5) highest among the other 19 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 HRlab (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Calamari 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 — Data processing agreement. The pricing page only lists 'Custom contracts & DPA' within an enterprise offer without publishing the agreement or stating that it can be concluded online.
- Weak sourcing — Hosting options. 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.
- 153 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
- 69 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
- 30 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
- 18 compliance 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
- 16 support 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
- 11 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
- 9 hosting 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
- 5 data 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.calamari.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 2 Pricing page www.calamari.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 1 Oct 2026 Details →
- 3 Leave management www.calamari.io Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 4 Entitlements & German leave rules — found from sitemap help.calamari.io Checked 16 Nov 2026 Details →
- 5 Entitlements & German leave rules — found from sitemap help.calamari.io Checked 16 Nov 2026 Details →
- 6 Security / trust page — found from the homepage www.calamari.io Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →