Kenjo vs Personalwolke

Kenjo

The module list names a digital personnel file, document management, an org chart and digital signature, which clears the 3-anchor — but the evidence says nothing about change history on employment fields, custom fields, field-level permissions or retention per document type, and I do not sign off on a personnel file whose history I cannot see. Missing evidence is missing capability here.

Personalwolke

A 'digitale Personalakte' and Personalverwaltung are named, but the evidence says nothing about org structure, custom fields, or dated change history on contract and salary — I cannot co-determine a file whose audit trail and field permissions are undocumented. Vacation aliquotation for entry, part-time and exit hints at some date awareness, but that is entitlement maths, not record history.

Kenjo

A 'Vorbereitende Lohnabrechnung' module and 'Abrechnungsmanagement' are named, but no payroll system, export format, mid-month joiner/leaver handling or pre-payroll check appears anywhere — a payroll path by name only, which sits between rubric level 0 and rubric level 3.

Personalwolke

A 'Schnittstelle Lohn/Gehalt' exists as an option and 'vorbereitende Lohnabrechnung' plus the travel module's Lohnverrechnungsanbindung show a handoff is intended — but no payroll system is named anywhere, no format is defined, and mid-month joiners/leavers and a pre-payroll check are unaddressed. That is above a bare CSV export, below a named integration.

Kenjo

Time tracking, a clock terminal, leave management and shift scheduling are in the core offering, which is real breadth, but nothing documents automatic entitlement, sickness handling, break and rest rules, tamper-evident records or the BAG/ArbZG recording duty — and there is not one word about monitoring limits a Betriebsrat could configure. Breadth without the legal-duty documentation gets the middle anchor.

Personalwolke

Vacation management in days and hours with proration for Eintritt, Teilzeit, Austritt and Karenz, approval workflows, and 'komplexe Zeitwirtschaft inkl. Berechnung' with terminal support go beyond the basics. But the evidence is silent on break and rest-period rules, overtime accounts, tamper-evidence and — my question — any works-council-configurable monitoring limits; a start/stop function is not documented compliance with the BAG/ArbZG recording duty, and live project-time bookings raise exactly the monitoring questions nobody answered.

Kenjo

Both an ATS add-on and an onboarding/off-boarding module exist, and applicant deletion is actually stated — six months after rejection, two years in the talent pool — but no careers page, structured stages, handover into the employee record or e-signed contract flow is evidenced. Two halves without proof of the join.

Personalwolke

Nothing: the module list is Time, Travel, Project Time and HR-Expert, and nowhere in the evidence is there an applicant list, a careers page, an onboarding checklist or any trace of a join path. Hiring evidently lives outside this product.

Kenjo

The privacy policy is respectable for the vendor's own website — Art. 15-21 rights, a DPO address, executed deletion periods, no profiling — but it governs kenjo.io visitors and applicants to Kenjo GmbH, not the product: no DPA, no role model, no audit log of who read which personnel file, and no evidence that the HR analytics, surveys and 360° reviews can be switched off for co-determination. A tool that cannot answer those questions does not get installed, so this sits between the 0 and 3 anchors.

Personalwolke

The DPA is available 'auf Anfrage' only — precisely the anchor-3 situation — and beyond SSL and Google-Authenticator 2FA the evidence offers no role model, no retention or deletion rules, no audit log of who read what, and no way shown to switch monitoring or reporting features off. That the vendor's own privacy policy runs Hotjar for 'Verhaltensdaten' with pseudonymised user profiles tells me behaviour analysis is in their culture even if it is not in the product.

Kenjo

The contracting entity is a German GmbH with a Charlottenburg registry number and one processing location is stated as Germany, but the product's hosting residency, ownership and its own subprocessor chain are all marked unknown, and the subprocessors that are named include US providers (Anthropic, Google) — for vendor processes, with the product's hosting nowhere confirmed.

Personalwolke

An Austrian GmbH in the Firmenbuch and a server 'in Österreich und damit innerhalb der EU' are genuinely solid and better than most. But the subprocessor disclosure stops at two website analytics tools, names no data-centre provider or product-side processor chain, and leaves Hotjar in the chain without an explained safeguard — for a §87 assessment I cannot verify where personnel data actually flows, so this sits just below the standard baseline.

Kenjo

Starter at 6€ and Growth at 10€ per employee are public with a monthly/annual toggle, the recruiting add-on at 249€/month and onboarding from 400€ are stated — but the Connect tier holding the APIs, integrations and time-tracking automation is demo-book only, and VAT treatment, minimum term and any headcount minimums are not published.

Personalwolke

The pricing page states a model — module- and user-based monthly rent, a one-time setup fee, multi-module and loyalty discounts, 30-day trial — but not a single euro figure for any tier or module, and the setup fee amount is unstated. No HR lead can compute the annual invoice from these pages; the price is a sales conversation.