As of 17 Nov 2026, the panel rates Kenjo 3.5/5 and Personalwolke 2.5/5 in HR Management. Weighted by what each judge cares about, 6 of the 6 judges pick Kenjo and 0 pick Personalwolke. Kenjo scores higher on 6 of 7 criteria (Recruiting & onboarding, Digital personnel file & data model, Payroll handoff, plus 3 more). Personalwolke scores higher on 1 of 7 criteria (European sovereignty). Provenance — Kenjo: EU-Made, Germany; Personalwolke: EU-Made, Austria. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
Kenjo leads on six of the seven criteria: core HR records 7.0 vs 4.5, payroll readiness 7.3 vs 5.5, recruiting and onboarding 7.0 vs 4.0 and employee data governance 5.7 vs 4.3 each draw a six-judge lean to Kenjo, while time and absence 8.0 vs 7.2 and pricing transparency 6.2 vs 5.0 lean Kenjo 5–0 with one tie apiece. Sovereignty is the split: 5.0 vs 4.3 toward Personalwolke, four judges lean Personalwolke, two tie, none lean Kenjo. Kenjo's data residency attribute reads EU by default, yet its captured pages give different figures for hosting and disclose US processing of transcripts via Anthropic and Google; Personalwolke states its server location as Austria, within the EU. Personalwolke's recruiting verdict itself splits 3–5 over Prescreen as a handover versus a documented joint process. The six judges' weighted totals run Kenjo 6–7 against Personalwolke 4.7–5.4.
Choose Kenjo if
You run DATEV-centred payroll in Germany and need handoff depth — payroll readiness leans Kenjo six judges to none, 7.3 vs 5.5, with a vendor-maintained export covering over 100 DATEV attributes per employee to LODAS and Lohn und Gehalt
You need recruiting and onboarding inside the same suite — the criterion leans Kenjo six judges to none, 7.0 vs 4.0, and Personalwolke's own judges split 3–5 over whether Prescreen is a handover into another applicant system
Your workforce clocks in by app, browser or PIN/QR kiosk and manual corrections need four-eyes approval — time and absence leans Kenjo five judges to none with one tie, 8.0 vs 7.2
You need a central personnel record strong enough for review — core HR records leans Kenjo six judges to none, 7.0 vs 4.5, and Personalwolke's verdict describes its core HR records as short of an auditor's file
You must budget from published prices — pricing transparency leans Kenjo five judges to none with one tie, 6.2 vs 5.0, while Personalwolke's captured pages give different figures for the same tiers
Choose Personalwolke if
Your data protection officer requires one stated server location — Personalwolke's pages state Austria, within the EU, while Kenjo's captured pages give different figures for hosting
Your policy cannot accept US processing of HR transcripts — Kenjo discloses US processing via Anthropic and Google, and sovereignty leans Personalwolke four judges to none with two ties, 5.0 vs 4.3
You want a vendor under Austrian jurisdiction — Personalwolke's legal entity jurisdiction is AT; Kenjo's is DE
You weigh stated EU hosting over feature breadth — sovereignty is the sole criterion leaning Personalwolke even as Kenjo leads the other six
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Works Council Advocate
Sits on the Betriebsrat and has to approve this rollout under BetrVG §87. Reads every feature for whether it can monitor behaviour, and asks what is logged, who can read it and what can be switched off. A tool that cannot answer those questions does not get installed, however good it is.
Kenjo
This judge's pick
Personalwolke
Criterion by criterion
Digital personnel file & data model
Kenjo
The digital personnel file is built the way a works council wants to see it: role-based rights down to individual fields, confidential areas for salary data and illness history visible only to roles the employer switches on, and a complete change log that automatically stores every data change. Multi-entity separation, document templates with e-signature and an auto-generated org chart with view-level access control are documented; we found no public information on effective-dated contract and compensation history or on cost-centre structures.
Personalwolke
The HR-Expert module gives a real digital personnel file with personnel administration, PDF payslips assigned automatically by their payslip AI, an org structure through organigram groups with department-level supervisor assignment, and role-based access rights configurable per group. We found no public information on versioned contract and compensation history, custom fields, or e-signature, so this is a working file, not an auditor's single source of truth.
Payroll handoff
Kenjo
The DATEV handoff is named and vendor-maintained: an API connection covering more than one hundred DATEV attributes per employee, export to DATEV LODAS / Lohn und Gehalt including hourly workers and recurring variable payments, and the tax adviser can be given their own access without full admin rights. Balance and history reports go out as CSV to the payroll office, and the implementation fee is published; we found no public information on a documented pre-payroll check, on retro-accounting, or on how mid-month leavers are handled.
Personalwolke
The Time module performs payroll pre-accounting and hands time data over automatically to named payroll systems — BMD, RZL and DATEV, with K5-Lohn added in the FAQ — and Travel carries expenses into payroll accounting. We found no public information on provider certification, mid-month joiners and leavers, or a documented pre-payroll check, so the clean month-end close is asserted rather than evidenced.
Absence & working-time
Kenjo
Break and rest-period rules with automatic deductions, colour-coded warnings for rest violations and maximum daily working time, overtime accounts, per-location holiday calendars, pro-rata entitlement and stored historical time data for Arbeitsamt inspections — this treats working-time recording as a legal duty, not a gadget. My reservation under co-determination: geolocation locking of clock-ins, a live attendance map showing who works and where they are, and project-level time categorisation are all documented, and we found no public information on switch-off or works-council-configurable limits for these, nor on tamper-evidence of the records.
Personalwolke
Time recording is the heart of the product: statutory-compliant recording is claimed for Austria and Germany, vacation accounts run day-exact with automatic pro-ration for joiners, part-time and leave, collective-agreement overtime rules are supported, and monitoring alerts on rest-period and maximum-working-time violations exist. From my chair two points stay open: the admin group can edit employees' time bookings in a correction client, and we found no public information on whether those edits are logged or tamper-evident; shift models and overtime calculation sit outside the two published tiers, and configurability of the monitoring limits for the works council is not described.
Recruiting & onboarding
Kenjo
Careers pages, pipelines with scorecards, multiposting to named boards such as LinkedIn and Xing, automatic deletion of unsuccessful applicant data after six months and talent-pool data after two years, e-signed contracts, and a preboarding flow in which new hires enter their DATEV-relevant data before day one. We found no public information on interview scheduling or on IT provisioning triggered from the record.
Personalwolke
Recruiting runs through the partner product Prescreen, with a documented automatic interface carrying the hire into Personalwolke's digital personnel file and XING TalentManager candidate reach — the handover into the employee record is genuinely described. We found no public information on onboarding tasks or checklists, applicant-data retention and deletion, or e-signed contracts, and the applicant data itself would live with the partner.
Employee data protection & co-determination
Kenjo
Field-level permissions, role-gated confidential areas, a change log of every data change, named subprocessors bound to Article 28 terms, stated deletion deadlines for applicant and transcript data, and a written commitment to no profiling and no automated individual decisions — that is a foundation a works council can negotiate on. What I cannot find is the decisive part for a BetrVG §87 review: we found no public information on an audit log of who read which record, nor on switch-off or scope limits for the monitoring capabilities such as geolocated clock-in, the live attendance map and per-project time tracking.
Personalwolke
A data processing agreement is available to every customer on request, permissions are configurable per module with user, manager and admin groups plus custom permission groups, and — meaningfully for us — addable roles for Betriebsrat and Datenschutzbeauftragter and stated conformity with Austrian works agreements. What I still need for a yes under co-determination finds no public answer: an audit log of who read what, retention and deletion per data category, subject-rights handling, and whether the monitoring and early-warning functions can be switched off or limited in scope.
European sovereignty
Kenjo
The contracting entity is Kenjo GmbH in Berlin and the product pages claim all data on German servers with six-hour backups, while the app privacy policy names only ISO 27001-certified servers without any location — the captured pages give different figures for hosting location. The same privacy statement that promises no transfer outside the EEA separately discloses US processing of call transcripts by Anthropic, the subprocessor list names providers with purposes but mostly without locations, and we found no public information on a data processing agreement or the hosting provider behind the servers.
Personalwolke
The contracting entity is Workflow HR Systems GmbH in Vienna with a Firmenbuch number, the server location is stated as Austria and thus within the EU, and a data processing agreement exists on request. The published processor entries concern the vendor's website — among them a UK cookie-consent provider without a stated safeguard — and we found no public information on the processors behind the product's own data processing, so the chain beyond the server is not proven.
Pricing transparency
Kenjo
Per-employee prices are public for both main tiers with monthly and annual figures, the recruiting add-ons carry fixed monthly prices, and the one-time onboarding fee from 400 € and the 600 € DATEV implementation fee are named. The captured pricing pages give no minimum term or VAT treatment, the Connect plan is price-on-request, and we found no public prices for the analytics, employee-survey and OKR modules.
Personalwolke
From-prices per user and month are published for the named plans — Absence ab € 2,82, Base ab € 4,70, Professional ab € 5,47, HR-Expert ab € 1,86, Project-Time and Travel ab € 4,90 — alongside the stated 36-month binding, a reference company size of 76–100 employees and module discounts. The captured pages give different figures for the same tiers (Base 4,70 versus 4,90; Professional 5,47 versus 5,83), the one-time setup fee carries no figure, VAT treatment is not stated, and a quote-request form sits alongside, so the real annual invoice is not computable from public pages alone.
Sovereignty, side by side
Dimension
Kenjo
Personalwolke
Legal entity
Incorporated in DE
Incorporated in AT
Hosting location
EU by default
Not determined
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Not determined
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 17 Nov 2026, the panel rates Kenjo higher: 3.5/5 against 2.5/5. Weighted by what each judge cares about, 6 of the 6 judges pick Kenjo and 0 pick Personalwolke. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is Kenjo or Personalwolke European?
Kenjo is European (EU-Made, Germany). Personalwolke is European (EU-Made, Austria). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do Kenjo and Personalwolke store customer data?
Per the vendors’ own pages as captured — Kenjo: In the EU by default. Personalwolke: Default not stated; pages mention Austria.