Kenjo vs Personalwolke

Kenjo

Digitale Personalakte, Organigramm, document management and digital signature are all named modules, which clears the flat-list floor — but nothing on the evidence evidences versioned contract/salary history with effective dates, custom fields, multi-entity org depth, or permissions beyond the surface. For a record that must be true three years back, that silence is information.

Personalwolke

A 'digitale Personalakte' with payslip storage, salary reporting and country standards is named, but nothing evidences an org chart, custom fields, or any dated history of contract or salary changes — and history is the whole point of replacing eleven spreadsheets. By the anchors, that silence pins this to the flat-file-with-documents level, not the structured-file level.

Kenjo

A 'Vorbereitende Lohnabrechnung' module and 'Abrechnungsmanagement' are named, so a payroll path exists on paper — but no named system (DATEV or otherwise), no export format, no mid-month joiner/leaver handling, and the APIs and integrations sit in the unpriced Connect tier behind a demo booking. I cannot tell from this whether my month closes or somebody retypes it.

Personalwolke

There is an optional 'Schnittstelle Lohn/Gehalt', 'vorbereitende Lohnabrechnung' in the Time module and a payroll connection from travel expenses, so a path exists — but no named payroll system, no documented format, and nothing on mid-month joiners/leavers or a pre-payroll check. That sits between the anonymous-export anchor and the named-integration anchor, and I won't gamble my December close on an unspecified interface.

Kenjo

Urlaubsverwaltung, Zeiterfassung, a Zeiterfassungs-Terminal and Schichtplanung are all real modules in one system, which is the breadth I want — but automatic entitlement and carry-over, sickness recording and any documented ArbZG/BAG-2022 compliance are absent from the evidence, and Zeiterfassungsautomatisierung and labour-law alerts hide in the gated Connect tier.

Personalwolke

This is the product's spine: vacation aliquoting for entry, part-time, exit and Karenz, absence workflows and notifications, capture by web, app and terminal, and 'komplexe Zeitwirtschaft inkl. Berechnung' with hardware support. It falls short of the higher anchor because sickness recording, carry-over, per-location holiday calendars, break/overtime rules and anything inspection-ready or tamper-evident are entirely unevidenced.

Kenjo

Both halves exist in one suite — an ATS at a publicly priced 249 €/month add-on and an Onboarding/Off-Boarding module — but nothing confirms a careers page, structured stages, applicant retention/deletion for customers, or that the hired candidate lands in the employee record without re-entry. The 6-month applicant deletion in the privacy policy governs applying to Kenjo itself, not the product's feature.

Personalwolke

The published module list is Time, Travel, Project Time and HR-Expert — no applicant tracking, no onboarding, not even a checklist. Absence of the module in the evidence is the capability's absence; hiring stays in the shared inbox.

Kenjo

The privacy policy is genuinely decent — DPO contact, full Art. 15–21 rights, stated retention with automatic deletion, no profiling, contractual AI-training exclusion — but that is Kenjo's own compliance posture. For the product itself the evidence says nothing about role models, field-level permissions, an audit log, or analytics switchable off for co-determination, which with a time-clock terminal is exactly what a BetrVG §87 conversation will ask about.

Personalwolke

A DPA is available on request, GDPR conformity is claimed, and SSL plus two-factor authentication are stated — but there is no evidenced role model, no retention periods, no deletion mechanics and no audit of who read what. That is exactly the DPA-on-request-with-the-rest-arranged-yourself anchor, and it would not survive a first conversation with a works council on the monitoring-heavy time module.

Kenjo

The contracting entity is solidly German — Kenjo GmbH, Berlin, HRB B 183681B at Amtsgericht Charlottenburg — and the privacy policy claims all processing stays in the EEA, particularly Germany. But no data-centre provider is named for the product itself, the customer-data subprocessor chain is not published, and the 'nothing leaves the EEA' claim sits awkwardly next to Anthropic (USA) and Google in the subprocessor list, which I cannot reconcile as a buyer.

Personalwolke

The server is stated to sit in Austria within the EU and the imprint shows an Austrian GmbH with a Firmenbuch number, which is better than EU-as-an-option. But the only subprocessors named anywhere are website analytics (Hotjar, Matomo), the product's own processing chain is absent, and even the contracting jurisdiction was flagged as unconfirmed — a published chain is what I'd need to move above the middle.

Kenjo

I can compute the core for my 400 heads: Starter 6 € or Growth 10 € per employee, monthly or annual with 10 % off, recruiting add-on at 249 €/month, onboarding from 400 €. But Connect — the tier holding the APIs, integrations and time-tracking automation I would actually need — is demo-gated with no price, and VAT treatment and minimum term are unstated.

Personalwolke

The pricing page describes a model — monthly rent per employee per module, a one-time setup fee, multi-module and loyalty discounts, 30-day trial — but not a single euro figure, so I cannot compute the annual invoice for 400 people from public pages. Only the model description and free trial keep this above the nothing-published anchor.