Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Kertos GmbH · www.kertos.io

Report an error on this page Is this your product? →

Link to this page

Kertos: AI-assisted analysis on whats-best.ai Kertos: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Kertos at a glance

Vendor
Kertos GmbH
Headquarters
Not stated on the vendor’s pages as of 8 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 8 Nov 2026
Free plan
Not stated on the vendor’s pages as of 8 Nov 2026
Panel verdict
The AI panel rates Kertos 3/5, the mean of 6 judges. Kertos is a compliance platform from Kertos GmbH for GDPR record-keeping, data subject requests and multi-framework compliance in one system. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 8 Nov 2026; evaluated by the panel 27 Oct 2026. all sources

Kertos alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The External DPO

Weighted verdict

Carries thirty client mandates and bills by the hour they save. Optimizes for multi-client capability, reusable templates, a RoPA that drives the rest, and client-ready reports. Rejects single-tenant tools that treat the consultancy as thirty separate customers.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The External DPO

Panel median The External DPO This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The External DPO
Records & DPIA depth 3 of 5 3 of 5
Data subject rights & incidents 3 of 5 3 of 5
Privacy regime coverage 3.5 of 5 3.5 of 5
Audit readiness & evidence 3 of 5 3 of 5
Integrations & automation 3.5 of 5 3.5 of 5
European sovereignty 1.5 of 5 1 of 5

Records & DPIA depth

How this is scored

The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.

0 — Not a privacy management tool; at most a set of document templates with no structured records.

3 — A structured record of processing activities with templates, and a DPIA questionnaire or checklist.

5 — Records of processing and DPIAs as modules with templates, processors and their DPAs recorded, and TOMs documented and assigned to processing activities.

8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA need derived from the record, reusable templates across companies, and outputs (Art. 30 register, DPIA report) ready for a supervisory authority.

10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client capability for external data protection officers, and the documentation is audit-ready without manual assembly.

Report an error

The External DPO

Records of processing, DPIAs, TOMs and TIAs are created on one platform, fed by automated discovery of tools and data sources, with vendor management and policy management alongside — a workable core for a client file. For my mandates I would still need evidence of data processing agreements recorded per processor, DPIA need derived from the record, and reusable templates across companies; the only multi-company mechanism documented is an automatic email alias for auditors reviewing several clients. 6 7 10 12

Report an error

Data subject rights & incidents

How this is scored

The operational half of the DSMS: handling data subject requests within the Art. 12 deadline, a breach register with the 72-hour notification of Art. 33, and deletion concepts that are carried out.

0 — No handling of data subject requests or data breaches in the product.

3 — A log of data subject requests and a register of data breaches, with templates for the responses.

5 — Request workflows with the one-month Art. 12 deadline tracked and reminders, a breach register with the 72-hour clock and a risk assessment per breach, and deletion periods recorded per processing activity.

8 — An intake form or portal for requests with identity verification, deadline escalation, breach severity assessment producing the authority notification, and deletion rules tied to the RoPA with execution tracked.

10 — Rights and incidents as operations: end-to-end request handling an authority audit can walk through, breach workflows that produce the Art. 33 and Art. 34 notifications, and deletion automation with evidence that the deletion happened.

Report an error

The External DPO

Data subject request handling is documented in depth: request types under Articles 15 to 19, a tracked 30-day due date by default, per-system execution tasks assignable to members, automated intake via API with webhook documentation, and automatic closure once the data subject is notified. Incident management appears as a module in the platform and the auditor view, but the captured pages give no detail on a 72-hour clock, severity assessment or authority notification, and deletion runs as request handling rather than as periods recorded per processing activity. 8 10 12 15

Report an error

Privacy regime coverage

How this is scored

Which privacy regimes the product operationalises — DSGVO/GDPR, BDSG, TTDSG/ePrivacy, Swiss nDSG, UK GDPR, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.

0 — No privacy regime built in; a generic task or document tool.

3 — GDPR implemented with its registers, templates and checklists.

5 — GDPR plus the national law of its market (BDSG, nDSG or UK GDPR) named and supported with their own templates or requirements.

8 — Several regimes on one record with requirements mapped across them, newer duties (AI Act, ePrivacy/TTDSG) covered as maintained content, and updates published when a regime changes.

10 — Regime coverage as a living product: many privacy regimes and per-country variants on one data basis, and a documented update cadence when the law moves.

Report an error

The External DPO

Beyond GDPR the platform names NIS2, the EU AI Act, ISO 27001, ISO 27701, ISO 42001, SOC 2, TISAX and C5 on one platform, with AI Act support backed by structured AI use-case documentation and an AI inventory, and product updates published when features extend. We found no public information on national privacy laws such as BDSG, the Swiss nDSG or UK GDPR, or on per-country variants mapped onto one data basis. 1 4 11 13

Report an error

Audit readiness & evidence

How this is scored

Whether the system produces defensible proof: change history, evidence collection, and reports for auditors, authorities and management.

0 — No reports, history or evidence; the product only stores the current state.

3 — PDF or Word reports of the registers, and documents attachable to records.

5 — Versioned records or a change history, report generators for the core registers (RoPA, DPIA, TOMs), and evidence attached per processing activity or measure.

8 — A revision-safe change history, audit evidence packs generated on demand, management and data protection officer reports at a click, and read-only auditor access.

10 — Audit readiness as a standing state: documentation status shown continuously per regime and scope, proof packs an auditor accepts as they are, and any record reproducible as it stood on a given date.

Report an error

The External DPO

Read-only auditor access with granular restrictions — including automatic company-specific aliases for auditors reviewing several clients — plus automatic evidence collection linking policies to controls and continuous Auto-Checks is genuinely client-audit material. We found no public information on a revision-safe change history, on-demand evidence packs, or management and officer reports generated at a click, which is what I need to hand an authority a defensible file. 9 12 13

Report an error

Integrations & automation

How this is scored

Whether the platform feeds from the real IT estate — directory import, ticketing, SSO, API — and automates the recurring privacy work instead of re-typing it.

0 — No import, export or integration; data is typed in and printed out.

3 — CSV or Excel import and export, and reminders for recurring reviews.

5 — Single sign-on, a documented API or a few named connectors (directory, ticketing), and recurring tasks with reminders and assignment.

8 — A documented REST API for the core objects, a named connector set (directory, ticketing, HR or asset sources), webhooks, SSO with SCIM provisioning, workflow automation with delegation and escalation, and AI assistance with human review.

10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, two-way sync with the estate, and recurring work (reviews, attestations, evidence collection) automated and documented.

Report an error

The External DPO

A documented API reference, webhook API documentation for data subject requests, and over one hundred integrations — HR systems that add new users automatically, device sync into the asset inventory, ticketing and communication tools, discovery and vulnerability management — plus the KAIA AI assistant for compliance workflows. We found no public information on single sign-on with SCIM provisioning or on delegation and escalation in task workflows. 8 11 14 15

Report an error

European sovereignty

How this is scored

Where the compliance record of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. A platform that maps your processing is itself your most concentrated processing. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.

0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or EU hosting is offered only on request or on top tiers.

5 — EU hosting stated as the default, a data processing agreement and a subprocessor list published; a parent company or a subprocessor may sit outside the EU.

8 — EU entity, EU hosting in named data centres, a subprocessor list with no non-EU processor touching customer content, and the DPA and TOMs published.

10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, an on-premises or sovereign-cloud option, and the whole chain documented publicly.

Report an error

The External DPO

The imprint proves a German contracting entity — Kertos GmbH, registered at the Munich court with a German VAT number — and the captured pages state "Made in Germany" and European Union co-financing. We found no public information on hosting location or data centres, subprocessors, a data processing agreement or ownership, so I cannot verify from these pages where my clients' most concentrated processing would actually sit. 5 7 11

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.

0 — No public prices at all; every configuration is a sales conversation.

3 — A public "from" price or one priced edition; the other editions, modules or entity counts are not public.

5 — Public prices per edition or tier with the billing period (monthly or annual) stated and the main inclusions listed.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated, software separated from consulting, and VAT treatment given; only genuine corporate-group contracts are custom.

10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a 10-client consultancy is a two-minute exercise.

Report an error

The External DPO not rated — no public information

We found no public information on pricing: none of the captured product pages shows prices for editions, modules, user counts or the optional external data protection officer service that can be booked in addition to the platform. An invoice cannot be computed from these pages alone; unpublished pricing is the norm in this market, and here a sales conversation would be required. 2 6 10

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Kertos

Is Kertos European?

Yes. whats-best.ai classifies Kertos as EU-Made.

Where does Kertos store data?

Not stated on the vendor’s pages as of 8 Nov 2026.

Does Kertos have a free plan?

Not stated on the vendor’s pages as of 8 Nov 2026.

What are the best alternatives to Kertos?

As of 19 Nov 2026, the panel rates preeco | datenschutz (3.5/5), caralegal (3.5/5) and Dastra (3.5/5) highest among the other 46 Data Protection products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | datenschutz (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Kertos alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (16)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.kertos.io Checked 16 Sep 2026 +1 earlier capture: 15 Sep 2026 Details →
  2. 2 Platform page www.kertos.io Checked 16 Sep 2026 Details →
  3. 3 GDPR framework page www.kertos.io Checked 16 Sep 2026 +1 earlier capture: 31 Aug 2026 Details →
  4. 4 About page www.kertos.io Checked 16 Sep 2026 +1 earlier capture: 31 Aug 2026 Details →
  5. 5 Imprint www.kertos.io Checked 16 Sep 2026 Details →
  6. 6 Records & DPIA depth — found from sitemap www.kertos.io Checked 1 Oct 2026 Details →
  7. 7 Records & DPIA depth — found from sitemap www.kertos.io Checked 1 Oct 2026 Details →
  8. 8 Data subject rights & incidents — found from sitemap docs.kertos.io Checked 1 Oct 2026 Details →
  9. 9 Data subject rights & incidents — found from sitemap www.kertos.io Checked 1 Oct 2026 Details →
  10. 10 Privacy regime coverage — found from sitemap www.kertos.io Checked 1 Oct 2026 Details →
  11. 11 Privacy regime coverage — found from sitemap www.kertos.io Checked 1 Oct 2026 Details →
  12. 12 Audit readiness & evidence — found from sitemap docs.kertos.io Checked 1 Oct 2026 Details →
  13. 13 Audit readiness & evidence — found from sitemap www.kertos.io Checked 1 Oct 2026 Details →
  14. 14 Integrations & automation — found from sitemap docs.kertos.io Checked 1 Oct 2026 Details →
  15. 15 Integrations & automation — found from sitemap docs.kertos.io Checked 1 Oct 2026 Details →
  16. 16 Structured-data backfill: markup only, no text or screenshot www.kertos.io Checked 8 Nov 2026 Details →