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 panel's verdict

Kertos is a compliance platform from Kertos GmbH for GDPR record-keeping, data subject requests and multi-framework compliance in one system. The bench's highest scores went to integrations and automation at 7-8: a documented API reference, webhook and ingress documentation for data subject requests, connector categories across HR, ticketing, device and vulnerability management, and discovery scans that build the record of processing from the IT estate. Privacy management and rights and incidents scored 5-6: request handling is documented in depth — a 30-day default due date, per-system tasks under Articles 15 to 19 — while we found no public information on processor data processing agreements, a 72-hour breach clock or authority notification. Framework coverage split 4-7: three judges scored 7, crediting NIS2 and the EU AI Act modules; the judge at 4 read it as GDPR plus AI Act, with no public information on BDSG, UK GDPR or the Swiss nDSG. Sovereignty scored 2-3 — a German contracting entity is proven, but we found no public information on hosting location, subprocessors or a data processing agreement.

Report an error

Speaks for it

  • Records of processing, DPIAs, TOMs and transfer impact assessments are created on one platform, with automated discovery scans building the record of processing from the real tool estate
  • Data subject requests run as documented operations — types across Articles 15 to 19, a 30-day default due date, per-system execution tasks with assignment, and automatic closure once the data subject has been notified
  • The auditor view gives external auditors read-only access scoped module by module, excludes them from owner, assignee and training roles, and creates company-specific aliases when one auditor reviews several companies
  • A documented API reference plus webhook and ingress documentation for data subject requests supports automated intake, and the homepage claims over one hundred integrations
  • The EU AI Act is supported by dedicated modules — AI inventory, assessments, use-case documentation and employee trainings — with product updates published on a dated page

Report an error

Held against it

  • We found no public information on hosting location, subprocessors or a published data processing agreement, and the documentation pages state they are powered by Pylon, a third-party tool
  • Incident management appears as a module name and in the auditor view, but we found no public information on a 72-hour clock, severity assessment or authority notification output
  • We found no public information on BDSG, the Swiss nDSG, UK GDPR or ePrivacy/TTDSG, or on one record mapping requirements across regimes
  • We found no public information on a revision-safe change history or evidence packs generated on demand, and automatic evidence collection currently covers policies, with trainings, incidents, risks and assets named as future steps
  • Pricing transparency scored 0, with no prices, editions or billing periods found on the captured pages

Report an error

Best for

  • You are a company operating under GDPR that wants the record of processing built by automated discovery of your actual IT estate rather than typed by hand
  • Your team processes data subject requests under Articles 15 to 19 in volume and wants per-system execution tasks with API and webhook intake
  • You are preparing ISO 27001, NIS2, SOC 2, TISAX or C5 audits and need to give an external auditor read-only access scoped module by module
  • You need EU AI Act governance — AI inventory, assessment and use-case documentation — run alongside your GDPR programme

Report an error

Avoid if

  • Your procurement requires a stated hosting location, a subprocessor list and a published data processing agreement before signature — sovereignty scored 2-3, and the "Made in Germany" claim speaks to origin, not hosting
  • You operate under UK GDPR or the Swiss nDSG, or need BDSG or ePrivacy/TTDSG variants — coverage scores ranged 4 to 7, and we found no public information on these regimes or on one record mapped across regimes
  • You must be able to demonstrate a 72-hour authority-notification workflow from the tool — the incident side appears as a module name, and we found no public information on a clock, a severity assessment or a notification output

Report an error

The scores

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

Records & DPIA depth

Show reasoning
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

The In-House Counsel

Records of processing, DPIAs, TOMs and TIAs are created as modules on one platform, fed by discovery scans that populate the record from the real IT estate, and requests execute per system — so the objects are connected rather than parallel documents. We found no public information on processor DPAs or legal bases modelled into the record, on DPIA need derived from the record, or on multi-client separation for an external officer, which caps this below the top levels. 6 7 8 12

Report an error

The Drafted Generalist

The GDPR pages show records of processing, DPIAs, TOMs and vendor management as real modules, with a discovery scan that builds the record of processing from my IT estate instead of weeks of typing. I found no public information on whether processors' data processing agreements or legal bases are woven into one connected record, so I credit solid modules rather than a system of record. 6 7 10 12 3

Report an error

The Lead Auditor

Records of processing, DPIAs, TOMs and transfer impact assessments are built as modules on one platform, with vendor management alongside and automated discovery feeding the record of processing. We found no public information on processors' data processing agreements being recorded, legal bases linked to activities, or an Article 30 register output ready for a supervisory authority. 6 7 10 3 12

Report an error

The IT Integrator

Records of processing, DPIAs, TOMs and transfer impact assessments are all created on one platform, and — the part that decides it for me — the record of processing is built from automated discovery of the tools and data sources already in the infrastructure instead of being typed by hand. Vendor management sits alongside, and an external data protection officer can work in the same platform; we found no public information on processors' data processing agreements being recorded or on TOMs assigned to processing activities. 3 6 7 10 12

Report an error

The Skeptic

Records of processing, DPIAs, TOMs and even TIAs are creatable on one platform, and automated discovery builds the record from the real tool estate — that part is genuine and documented. But while the German page promises GDPR made easy, we found no public information on processor DPAs being managed, TOMs assigned to processing activities, legal bases linked to records, or DPIA need derived from the record, which is where a connected data model would show itself. 6 7 10 12

Report an error

Data subject rights & incidents

Show reasoning
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

The In-House Counsel

Request handling runs as an operation: the deadline defaults to 30 days and can be altered, work is executed per system with assignment, attachments and tags, the status closes automatically once the data subject is notified, and API plus webhook documentation supports automated intake. Incidents appear as a module name in the platform and the auditor view, but we found no public information on a 72-hour clock, a per-breach risk assessment or an authority notification output — the Art. 33 workflow I must be able to demonstrate. 8 10 12 15

Report an error

The Drafted Generalist

The request help centre is the plain-language walkthrough I need: request types across Articles 15 to 19, a thirty-day due date by default, per-system execution tasks you can assign, and a status flow that only closes once the data subject has been notified. Deletion and access requests can run automated end to end via APIs; incident management appears as a module, though I found no public information on a 72-hour clock or per-breach severity assessment. 8 6 10 3

Report an error

The Lead Auditor

Deletion and access requests run as genuine operations — a thirty-day due date tracked by default, per-system execution tasks, automatic completion once the data subject is notified, plus request automation and API intake. The incident side appears only as an incident management module; we found no public information on a 72-hour clock, per-breach risk assessment or authority notification. 8 6 10 3 12

Report an error

The IT Integrator

Request handling runs as operations: access, deletion, rectification, restriction and unsubscription under Articles 15 to 19, a thirty-day default deadline, per-system execution tasks with the status automatically set once every system is processed, and the confirmation email closing the request — driven through API integrations with separate ingress and webhook documentation. Incidents appear as a managed, auditor-visible module, but we found no public information on a 72-hour clock or authority notification workflow, and intake identity verification is not shown. 3 8 10 12 15

Report an error

The Skeptic

The data subject request side is documented at documentation depth: a 30-day default due date, a four-stage status flow, per-system execution tasks with assignment, API intake and webhook docs, and completion notification to the data subject. The breach side is only a module name — incident management appears in feature lists and auditors get read-only sight of incidents, but we found no public information on a 72-hour clock, severity assessment or authority notification output. Deletion is handled as requests in workflows rather than periods recorded per processing activity. 8 6 10 12

Report an error

Privacy regime coverage

panel disagrees Show reasoning
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

The In-House Counsel

GDPR is operationalised with registers, DPIA and TOM creation and automated requests, and the EU AI Act is supported with an AI inventory, assessment and use-case documentation presented in a published product update — maintained legal content, not a static checklist. The wider list is security regimes; we found no public information on BDSG, TTDSG/ePrivacy, Swiss nDSG or UK GDPR support, so the national variants a German-headed group needs are unproven. 1 6 10 11 13

Report an error

The Drafted Generalist

GDPR is covered deeply with its registers, and the EU AI Act has its own maintained modules — AI inventory, assessments, a management system and trainings — which is exactly the newer duty I would trip over. I found no public information on BDSG, the Swiss nDSG or UK GDPR, and nothing on whether one record maps across regimes, so this stays GDPR plus AI Act rather than multi-regime. 1 11 9 6

Report an error

The Lead Auditor

GDPR sits in one catalogue alongside ISO 27001, NIS2, ISO 27701, SOC 2, TISAX, C5 and the EU AI Act, and the AI Act is maintained product content — structured use-case documentation shipped as a feature with published product updates. We found no public information on BDSG, TTDSG or other national variants, or on one record mapping requirements across regimes. 1 6 11 13 12

Report an error

The IT Integrator

GDPR is fully operationalised alongside NIS2, and the EU AI Act is first-class content with an AI inventory, AI assessments, a management system, use-case documentation and employee trainings, with the product updates page showing the content moving. We found no public information naming BDSG, the Swiss nDSG, UK GDPR or TTDSG/ePrivacy, which is what would separate the strong multi-regime position from a fully mapped one. 1 6 9 11 13

Report an error

The Skeptic

GDPR is deeply built out and the EU AI Act is more than a badge — a dedicated module set for AI inventory, assessment and use-case documentation, with product updates published on a dated page. The regime list stops at EU level, though: we found no public information on BDSG, Swiss nDSG, UK GDPR or ePrivacy/TTDSG, and the captures show no evidence of one record with requirements mapped across regimes. The same six logos also appear in the captures both under Certifications & Attestations and as supported frameworks, with no certificate scopes to distinguish a held certificate from a supported regime. 1 11 6 13

Report an error

Audit readiness & evidence

Show reasoning
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

The In-House Counsel

The Auditor View is built for a real certification audit: read-only access to records and evidence, auditors excluded from assignments and trainings, configuration areas hidden, and company-specific aliases when one auditor reviews several clients. Policy completion now attaches evidence to the matching control automatically; we found no public information on a revision-safe change history or records reproducible as they stood on a given date, which is what my defensibility standard asks for. 12 13

Report an error

The Drafted Generalist

Auditors get a genuinely read-only view with scoped modules, hidden configuration, and even company-specific aliases when one auditor reviews several companies — I could set that up myself from the documented invitation steps. Evidence is collected automatically and linked to controls, but I found no public information on a revision-safe change history or reports generated for management. 12 13 10

Report an error

The Lead Auditor

Automatic evidence collection that links completed policies to controls, and a proper read-only auditor role with scoping and company-specific aliases, are exactly what an audit file needs. But we found no public information on a revision-safe change history, evidence packs generated on demand, or any record reproducible as it stood on a given date — the core of a defensible audit trail. 12 13 14 9

Report an error

The IT Integrator

There is a purpose-built read-only auditor role with an invitation flow, hidden configuration areas, exclusion from owner and assignee selection, and company-specific email aliases when one auditor reviews several companies — plus automatic evidence collection that detects a completed policy, marks the control done and links the evidence. We found no public information on a revision-safe change history or management and officer reports generated on demand. 9 12 13

Report an error

The Skeptic

The auditor view is the real thing: read-only access scoped module by module, company-specific aliases for auditors reviewing several companies, and auditors excluded from assignment and workflow roles. Automatic evidence collection links completed policies to controls, but the product update states this currently covers policies, with trainings, incidents, risks and assets named as future steps. We found no public information on a revision-safe change history or on-demand evidence packs, and the 100% audit-success figure stands alone in the captures without any named audits behind it. 12 13 9

Report an error

Integrations & automation

Show reasoning
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

The In-House Counsel

Over one hundred integrations are offered, a public API reference exists, webhooks are documented for data subject requests, and named connector categories cover HR, ticketing, device management, communication and vulnerability management, with monthly discovery feeding the records from the estate. Single sign-on with SCIM provisioning, escalation logic and the human-review model around the KAIA assistant are not described on the captured pages. 7 8 11 14 15

Report an error

The Drafted Generalist

Over a hundred integrations, a public API reference with webhook documentation for data subject requests, HR systems adding joiners automatically, and ticketing, device and vulnerability data feeding the asset inventory — the recurring work looks automated rather than re-typed. I found no public information on single sign-on with SCIM provisioning or on escalation rules in the workflows. 11 15 14 10

Report an error

The Lead Auditor

Over one hundred integrations are claimed with named connector categories — HR systems adding users automatically, device management feeding the asset inventory, ticketing sync, vulnerability remediation turned into audit evidence — plus a documented API reference and webhook documentation for data subject requests. We found no public information on single sign-on or SCIM provisioning, and webhook documentation is shown only for requests. 11 14 15 8 7

Report an error

The IT Integrator

This is where the platform earns its keep: a documented API reference, dedicated webhook and ingress API documentation for data subject requests, over a hundred integrations, automatic user provisioning from HR systems, task sync with ticketing tools, device sync into the asset inventory, vulnerability remediation converted into audit evidence, and monthly discovery scans that keep the record current without retyping. Webhooks are documented for request events specifically, and we found no public information on single sign-on or SCIM provisioning, which is why I stop one notch short of infrastructure-grade. 6 7 10 11 14 15

Report an error

The Skeptic

This is where the platform looks most like infrastructure: a documented API reference, webhook and ingress API docs for data subject requests, and a named connector set spanning HR systems, ticketing tools, device management, communication apps and vulnerability management. The over-100-integrations figure is a homepage count we cannot verify from the captures, but the documentation categories carry the story on their own. We found no public information on single sign-on or SCIM provisioning. 14 15 11 8

Report an error

European sovereignty panel opinion

Show reasoning
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

The In-House Counsel

The contracting side is proven European: Kertos GmbH, registered at the Munich court with Berlin and Munich offices, a German VAT identification, "Made in Germany", EU co-financing, and an optional data protection officer seated in the EU. Hosting location, subprocessors and a published data processing agreement are not stated in what we captured — and a platform that maps my processing is itself my most concentrated processing. 5 4 7 10 11

Report an error

The Drafted Generalist

The imprint proves a German contracting entity — Kertos GmbH, registered at the Munich court with a German VAT number — and the site carries a 'Made in Germany' claim. I found no public information on hosting location, subprocessors or a published data processing agreement, so the chain beyond the legal entity is unproven. 5 11

Report an error

The Lead Auditor

The imprint proves a German contracting entity — Kertos GmbH registered at the Munich court, with offices in Berlin and Munich — though the Made in Germany claim speaks to origin, not hosting. We found no public information on hosting location, a published subprocessor list, or a data processing agreement, and the documentation itself runs on a third-party platform of unstated location. 5 6 15

Report an error

The IT Integrator

The contracting entity is proven German — Kertos GmbH registered at the Munich registry court with a German VAT number, offices in Berlin and Munich, a Made in Germany claim and EU co-financing. Hosting location, subprocessors and a published data processing agreement are not stated on the captured pages, so those dimensions remain unknown rather than non-European. 5 7 11

Report an error

The Skeptic

The imprint proves the contracting entity: Kertos GmbH, registered at the Munich court with a German VAT ID and offices in Munich and Berlin. That is where proof stops — Made in Germany is an origin label rather than a hosting statement, and we found no public information on hosting location, a data processing agreement, or a published subprocessor list. The documentation pages themselves state they are powered by Pylon, a third-party tool that appears in no captured list. 5 11 14

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
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

The In-House Counsel not rated — no public information

We found no public information on pricing: no price, edition, module or per-entity boundary appears on the homepage, platform, GDPR and AI Act pages or the documentation we read, so I cannot compute an invoice from public material alone. 1 6 7 10 11

Report an error

The Drafted Generalist not rated — no public information

I found no public pricing information on any page I read — the homepage, platform, GDPR and product-update pages show not even a starting figure, and the external data protection officer is offered only as a bookable add-on without a price. Budgeting this would start with a sales conversation. 2 7 10 11

Report an error

The Lead Auditor not rated — no public information

We found no public information on pricing — no edition, module price, billing period or setup fee appears on any page we read, including the homepage, platform pages and framework pages. 1 2 1 6 10

Report an error

The IT Integrator not rated — no public information

We found no public information on pricing — the captured homepage, platform, GDPR and AI Act pages show no editions, per-module prices, licence boundaries or setup fees, so every configuration would start as a sales conversation. 1 6 7 11

Report an error

The Skeptic not rated — no public information

We found no public information on pricing: none of the captured pages — the platform, homepage, German framework pages and product pages — show prices, editions, billing periods or module costs. Even the optional external data protection officer is offered only as a bookable add-on with no figure attached. 2 1 6 10 11

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 →