Kenjo vs Personalwolke

Kenjo

Module names for a digital personnel file, digital signature, org chart and workflows exist, which clears the flat-contact-list floor, but the evidence shows nothing on custom fields, effective-dated contract or salary history, multi-entity org structure, or field-level permissions — the difference between rubric level 3 and rubric level 5 is unevidenced in either direction, so I sit just below 5.

Personalwolke

A 'Digitale Personalakte' with Personalverwaltung and Excel/PDF export is confirmed, but the evidence is silent on org structure, custom fields, dated contract/salary history, e-signature and field-level permissions — that is a flat file, not a system of record. And since the only data access on evidence is a webservice sold as an optional add-on, I have no way to treat this file as the identity source my systems sync from.

Kenjo

"Vorbereitende Lohnabrechnung" and "Abrechnungsmanagement" are named modules, so a payroll path is stated — but no named payroll system, no export format, no mid-month joiner/leaver handling, and the only integration path ("APIs und Integrationen") is locked behind the contact-sales Connect tier. A module name I cannot connect to DATEV or anything else is a retyped spreadsheet waiting to happen.

Personalwolke

A 'Schnittstelle Lohn/Gehalt' exists as an optional module and the site claims 'vorbereitende Lohnabrechnung' plus a travel-expense payroll hookup, but no payroll system is named, no export format is documented, and mid-month joiners/leavers and pre-payroll checks are absent. I can't wire a month-end handoff on an interface that has a name and nothing else.

Kenjo

Zeiterfassung, a Zeiterfassungs-Terminal, Urlaubsverwaltung and Schichtplanung are in the base tiers, which is more than request-and-approve — but nothing evidences automatic entitlement and carry-over, sickness recording, per-location holiday calendars, or any ArbZG/BAG recording-duty compliance, and "Zeiterfassungsautomatisierung" itself sits in the unpriced Connect tier.

Personalwolke

Working-time capture is real — start/stop in Base, complex time calculation and terminals in Professional, web and app — and vacation runs in days and hours with pro-rating for entry, part-time, exit and parental leave. But nothing evidences sickness recording, carry-over, per-location holiday calendars, rest-period rules or tamper-evidence, so the German recording duty side of it is a claim, not a documented capability.

Kenjo

Both halves exist as modules — Recruiting/ATS as a priced 249 €/month add-on and Onboarding/Off-Boarding in the HR list — plus genuinely stated applicant retention (6 months, 2 years talent pool). But nothing shows the candidate-to-employee handover without re-entry, a careers page, or onboarding that triggers anything in IT: no account creation, no provisioning, no SCIM. A checklist that doesn't create the account is exactly what I don't grade.

Personalwolke

The complete feature inventory contains no vacancy, applicant-tracking, contract or onboarding capability of any kind — hiring lives in a shared inbox. And nothing here provisions the day-one account, no SCIM, no task trigger into IT, which for me is the entire measure of onboarding.

Kenjo

The privacy policy is real work: DPO contact, the full Art. 15–21 rights list, SCC/BCR/adequacy safeguards, AI-training exclusion, and executable retention for applicants and transcripts (6/12/24 months, auto-delete). But there is no published signable DPA, no role model beyond nothing stated, no audit log, and no retention statement for employee records themselves — that sits between rubric level 3 and 5, and a works council would ask the questions this sheet cannot answer.

Personalwolke

The only governance artifact is a substantive DPA available on request specifying processing and the TOMs, backed by SSL transport and Google-Authenticator 2FA — no role model beyond unstated, no retention periods, no deletion execution, no audit log of who read what. No SSO/SAML or SCIM is evidenced anywhere, and the GDPR-conformance line is a sticker, not documentation.

Kenjo

The imprint evidences a German contracting entity in full — Kenjo GmbH, Amtsgericht Charlottenburg HRB B 183681B, Berlin, German VAT ID — so I cannot follow the pipeline's 0. But the residency claim in covers sales/web analytics on Supabase, not the HR suite's hosting, which the evidence leaves undocumented; named non-EU subprocessors exist (Anthropic, USA) with safeguards stated, and ownership is unknown.

Personalwolke

Hosting is stated as Austria, EU, and the imprint is an Austrian GmbH with Firmenbuch number and UID, which I genuinely weigh. But no data-centre or product subprocessor is named — the published list covers only the marketing site's Hotjar and Matomo — and the vendor record says 'Workflow EDV GmbH' while the imprint says 'Workflow HR Systems GmbH', so I cannot even confirm who I would be contracting with. Missing evidence here is information, not a pass.

Kenjo

Starter at 6 € and Growth at 10 € per employee are public, with the monthly/annual toggle (10% annual saving), a priced recruiting add-on, and an onboarding fee stated as "ab dem 400 €". But Connect — the tier holding APIs, integrations and time-tracking automation — has no public price and requires a demo booking, VAT treatment and minimum term are unstated, and "from 400 €" is a floor, not an invoice line.

Personalwolke

The pricing page discloses the shape of the invoice — module- and user-based monthly rent, a one-time setup fee, term and multi-module discounts, a 30-day trial — but not one euro figure survives into the evidence, and the API itself is an 'optional' line item with no price. An HR lead cannot compute the annual invoice from these pages; they can only start a sales conversation.