Kenjo vs Personalwolke

Kenjo

The nav bar promises a digital personnel file, org chart and digital signature, which clears the 'no org chart' bar — but nothing on the evidence evidences change history, effective dating, custom fields or field-level permissions, so I cannot distinguish this from a flat file with upload. Module names are marketing; an auditor needs the record model, and the evidence never shows it.

Personalwolke

The personnel file is four words on a feature list — "Digitale Personalakte, Personalverwaltung" — with "über 60 smarte Features" standing in for any detail. No org chart, no custom fields, no change history, no document types, no field-level permissions are so much as named; the evidence confirms records exist and nothing about their structure. That is the flat-file anchor, generously read.

Kenjo

A 'vorbereitende Lohnabrechnung' module exists and Starter lists Abrechnungsmanagement, but no payroll system is named — no DATEV, no format, no mid-month joiner/leaver handling — and 'APIs und Integrationen' sits inside the unpriced, demo-gated Connect tier. That is a payroll path stated and nothing more; the handoff is somebody's re-typing until proven otherwise.

Personalwolke

"Schnittstelle Lohn/Gehalt optional" — an unnamed interface, marked optional in every tier, plus "vorbereitende Lohnabrechnung" and the travel module's "Lohnverrechnungsanbindung". No named payroll system (no DATEV, no BMD, nothing), no defined format, no mid-month joiner/leaver handling, no pre-payroll check; and even this thin handoff is an add-on line. That is the generic-interface anchor, word for word.

Kenjo

Time tracking is clearly more than a timer — module, reports, a terminal, shift planning, and Connect adds automation and shift templates. But the evidence is silent on entitlement calculation, carry-over, sickness, holiday calendars, and above all on the BAG/ArbZG recording duty; a German vendor selling Zeiterfassung without one documented word on the legal obligation gets no benefit of the doubt.

Personalwolke

The one area with genuine specificity: vacation in days and hours with pro-rata entitlement for entry, part-time, exit and Karenz, start/stop capture, "komplexe Zeitwirtschaft inkl. Berechnung", terminal hardware and digital approval workflows. But the compliance half is entirely silent — no holiday calendars per location, no break/rest rules, no overtime accounts, no tamper-evidence, not one word on the ArbZG/BAG recording duty — so "inkl. Berechnung" stays marketing fog. Above the 5 anchor for proration and hardware, well short of 8.

Kenjo

Both halves are named — an ATS as a €249/month add-on and an onboarding/offboarding module — which is more than one orphaned checklist. But there is no evidence of careers page, structured stages, rejection handling, or the candidate-to-employee handover, and the six-month applicant deletion I do see is Kenjo's own hiring policy, not the product's feature.

Personalwolke

The module list is Time, Travel, Project Time and HR-Expert — no applicant tracking, no onboarding, no e-signature, no careers page anywhere in the evidence.

Kenjo

The privacy policy shows real hygiene — DPO contact, Art. 15–21 rights, executed automatic deletion, no profiling, AI training excluded — but it governs the vendor's own website and sales processing, not the customer's employee records. No DPA is offered on the site, no role model is described anywhere, no audit log, no field-level access, nothing on BetrVG §87; product-side governance is a blank page.

Personalwolke

A DPA exists "auf Anfrage" — literally the on-request anchor — and beyond a blanket "erfüllt alle Anforderungen der EU-DSGVO" plus SSL and 2FA, governance is undocumented: no retention periods, no deletion mechanics, no role model, no audit log, no subject-rights process. Telling detail: the vendor's own site runs Hotjar for "Verhaltensdaten, pseudonymisiertes Nutzerprofil", and nothing says product-side analytics can be switched off for a works council.

Kenjo

The Impressum nails the contracting entity — Kenjo GmbH, Berlin, Amtsgericht Charlottenburg — and the privacy policy claims EEA/Germany processing, but that claim covers the vendor's web sphere: the product's hosting region is marked unknown, the product's subprocessor chain is unpublished, and even the vendor's own chain shows Anthropic PBC (USA) and Google on call transcripts plus a Singapore-registered Supabase. German letterhead, unverifiable data path.

Personalwolke

Hosting is stated plainly as Austria, inside the EU, and the imprint gives a full Austrian identity (Firmenbuch FN 188579 y, ATU VAT, Vienna address) — but the contracting name shifts between Workflow EDV GmbH and Workflow HR Systems GmbH, so I cannot confirm who I would actually be signing with. No data-centre provider named, no product subprocessor list (only website analytics appear), which parks this between the 3 and 5 anchors.

Kenjo

Real credit where due: Starter €6 and Growth €10 per employee, monthly/annual toggle with 10% annual discount, recruiting add-on at €249/month, onboarding 'ab dem 400€', all public. But Connect — holding the APIs, integrations, time-tracking automation and labor-law warnings — is demo-gated with no number, and VAT treatment and minimum term are unstated; 'from €400' is a floor, not a price.

Personalwolke

The pricing page publishes the shape of the invoice — monthly rent per employee and module, an unquantified "Einrichtungs-pauschale", loyalty and multi-module discounts, optional add-ons — and not a single euro figure. Even the payroll interface and the API are "optional" lines with no numbers, so an HR lead can compute nothing beyond the 30-day trial. That is the no-public-prices anchor, with one courtesy point for at least describing the model.