Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by Keyed GmbH · keyed.de

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

Link to this page

Keyed DSMS: AI-assisted analysis on whats-best.ai Keyed DSMS: 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.

Keyed DSMS at a glance

Vendor
Keyed GmbH
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 26 Oct 2026
Panel verdict
The AI panel rates Keyed DSMS 2.5/5, the mean of 6 judges. Keyed DSMS, the data protection management software of Keyed GmbH in Altenberge, scores strongest on audit readiness at 6-7: audits attach to a company, department, data recipient as a transfer impact assessment, asset or AI system, recur on configurable intervals that remind, create tasks and file results on the object, with communication logged and versioned. how scores are made
As of
Vendor pages captured 24 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Keyed DSMS alternatives, European ones first →

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

The panel's verdict

Keyed DSMS, the data protection management software of Keyed GmbH in Altenberge, scores strongest on audit readiness at 6-7: audits attach to a company, department, data recipient as a transfer impact assessment, asset or AI system, recur on configurable intervals that remind, create tasks and file results on the object, with communication logged and versioned. Privacy management draws the widest range, 5-7 — the external DPO credits the DPIA-to-record linkage, while the in-house counsel holds back because TOMs and legal bases are not shown attached per processing activity. Weakest are framework coverage, rights and incidents and integrations and automation at 4-5, with sovereignty sitting at 4: the documented regime is the German GDPR market plus the AI Act, the 72-hour breach clock is proven but request handling is not shown end to end, we found no public information on an API or connectors, and beyond the German entity and the stated 100% EU-Server we found no public information on a data processing agreement or subprocessor list. Pricing transparency scores 5-6 on four public tiers; persona-weighted totals range 4.6 to 5.7.

Report an error

Speaks for it

  • Audits attach to a company, a department, a data recipient as a transfer impact assessment, an asset or an AI system, with results persisting on the object for the next review cycle
  • Configurable audit intervals trigger reminders, task creation and documented results, and breach tasks notify the responsible person and the data protection officer daily until closed under the 72-hour reporting duty
  • The core GDPR artefacts exist as templated modules — records of processing, DPIAs, TOMs, Article 28 arrangements, data recipients, a deletion concept — and a processing record can be generated from an existing DPIA
  • Four pricing tiers are public with monthly figures and company counts: Free 0 € monatlich, Starter Ab 99 € monatlich, Professional Ab 299 € monatlich, Enterprise Auf Anfrage
  • Group-wide audit control with several reporting levels, plus period reports you assemble yourself and export in Word and PDF with your own logo

Report an error

Held against it

  • We found no public information on a documented API, connectors, webhooks, SCIM provisioning or data import, and single sign-on appears only on the Enterprise tier priced Auf Anfrage
  • We found no public information on BDSG, nDSG or UK GDPR support, or on an update cadence when a regime changes
  • Beyond the stated 100% EU-Server, we found no public information on a data processing agreement, subprocessor list or named data centres, and data residency is listed as not confirmed on the vendor's own captured pages
  • We found no public information on one-month deadline tracking for data subject requests, per-breach risk assessment, or evidence that deletion was executed
  • The "Ab" price floors leave scale steps, user limits, setup fees and VAT treatment unpublished, and the captured pages give different figures for claimed effort reduction — 50 per cent in one place, up to 70 per cent in another

Report an error

Best for

  • You run German GDPR compliance and want recurring, documented audits of companies, departments, data recipients, assets or AI systems — audit readiness scores cluster at 6-7
  • You manage several companies or advise several clients, since inheritance, period reports and an Enterprise tier with unlimited companies are documented
  • You want a German contracting entity — Keyed GmbH, Amtsgericht Steinfurt HRB 11598, developed in Münster — with EU hosting as stated on the product pages (100% EU-Server)
  • You need the AI Act alongside GDPR, since separate AI regulation software, an external AI officer service and AI-system audit templates are offered

Report an error

Avoid if

  • You need the platform to feed from a directory, ticket queue or asset inventory rather than manual entry — we found no public information on an API, connectors or any import path
  • Your obligations extend beyond the documented regime — the German GDPR market and the AI Act — to frameworks such as BDSG, nDSG or UK GDPR
  • Your workload is dominated by data subject requests rather than breaches — the 72-hour breach clock is documented, while one-month request deadline tracking is not
  • You must clear your vendor's hosting chain before signature — we found no public information on a data processing agreement, subprocessor list or named data centres

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 2.5 of 5
Privacy regime coverage 2 of 5
Audit readiness & evidence 3.5 of 5
Integrations & automation 2 of 5
European sovereignty 2 of 5
Pricing transparency 3 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, impact assessments, technical and organisational measures, data recipients with Art. 28 contracts and a deletion concept all live as templated modules, and a processing record can be generated from an existing impact assessment — the link runs from assessment to record, with inheritance and template resources for reuse across companies. I found no public information showing the record derives impact-assessment need or ties measures and legal bases to individual activities, so it stops short of one record driving everything. 7 8 10 10

Report an error

The In-House Counsel

Records of processing, DPIAs, TOMs and data recipients are real modules with templates, an Art. 28 processing-on-behalf article exists, and a record of processing can even be generated from an existing DPIA — the kind of linkage that keeps an Art. 30 register honest. Period reports and Word and PDF exports cover the register. I found no public information on TOMs and legal bases attached per processing activity, which is what separates a filled form from a connected data model. 7 8 10 10

Report an error

The Drafted Generalist

Every core record I need is named as a module — the processing register, impact assessments, technical measures, a deletion concept and data recipients with Article 28 processing — with templates, a document generator and inheritance across companies, and a processing record can even be created straight out of an existing impact assessment. I found no public information on legal bases being linked in the record or on impact-assessment need being derived automatically, which would be the sign of one fully connected data model. 10 10 7 8

Report an error

The Lead Auditor

The help centre documents processing records with or without a template, impact assessments, TOMs and Art. 28 processing-on-behind records as structured modules, and a processing record can be created from an existing impact assessment, so the artefacts are at least partly connected. Inheritance across companies and an unlimited-company tier point to multi-client reuse, but we found no public information on TOMs assigned per processing activity or an authority-ready register output. 7 8 10 10

Report an error

The IT Integrator

Records of processing, DPIAs, Article 28 processing, data recipients, TOMs and a deletion concept all exist as documented modules with templates and inheritance across companies, and a processing record can be created from an existing DPIA. The captured pages read as manual creation help rather than proof of one connected model with activities, systems, TOMs and legal bases linked, so it sits between structured modules and a linked data model. 7 8 10 10

Report an error

The Skeptic

Help articles prove the legal artefacts exist as modules: a record of processing activities built with or without templates, a DPIA, TOMs created manually, Art. 28 processing arrangements and a data-recipient register — and a processing record can be generated from an existing DPIA, with inheritance and per-plan company counts pointing to reuse across companies. That is more than parallel templates. We found no public information on TOMs assigned to processing activities or DPIA need derived from the record, which is where a fully connected model would show itself. 7 8 10

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 requests, a deletion concept and data breaches are named modules, and external communications carry tracked deadlines with automatic reminders; breach tasks notify the responsible person and the data protection officer daily until closed, explicitly tied to the 72-hour reporting duty. I found no public information on a request intake portal with identity verification, breach severity assessment producing the authority notification, or deletion execution evidence. 8 9 10 10

Report an error

The In-House Counsel

The breach side has teeth: the documented 72-hour reporting obligation drives daily notifications to the responsible person and the data protection officer until the task is closed, and external communications are handled with linked, deadline-reminded tasks — a clock I can defend to an authority. A deletion concept module and a data subject request module are both named. I found no public information on one-month Art. 12 deadline tracking for requests, per-breach severity assessment, or evidence of deletion actually executed. 8 9 10 10

Report an error

The Drafted Generalist

Breach handling has the 72-hour clock built in, with daily notifications to the responsible person and the data protection officer until the task is closed, and data subject requests, external communication with linked tasks and deadline reminders, plus a deletion concept, are all named modules. I found no public information on identity verification for requesters or a per-breach severity assessment that produces the authority notification. 9 10 10 8

Report an error

The Lead Auditor

Breach documentation with the 72-hour clock enforced by daily notifications to the responsible person and the data protection officer, a deletion concept module, and data subject requests as part of the full DSMS put the operational half on record. We found no public information on the one-month deadline being tracked, identity verification for requesters, or evidence that deletion was executed. 9 8 10 10

Report an error

The IT Integrator

Breach tasks carry the 72-hour reporting obligation with daily notifications to the responsible person and the data protection officer until done, and data subject requests plus a deletion concept are named modules. We found no public information on an intake portal with identity verification, a risk assessment per breach, or deletion execution being tracked, so the deadline machinery is proven but end-to-end operations are not shown. 9 8 10 10

Report an error

The Skeptic

Breaches are operational: tasks reference the 72-hour reporting duty, the responsible person and the data protection officer receive daily notifications until completion, and external communication links to tasks with automatic deadline reminders. Data subject requests and a deletion concept exist as named modules. We found no public information on tracking the one-month Art. 12 deadline for requests, per-breach risk assessment, or deletion execution — so this sits between a plain register and deadline-driven workflows. 8 9 10

Report an error

Privacy regime coverage

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

The GDPR is operationalised to German-market depth — records of processing, impact assessments, TOMs, Art. 28 processing contracts — and the AI Act is covered as dedicated software, an AI officer service and AI-system audit templates. I found no public information naming BDSG, nDSG, UK GDPR or TTDSG content, nor a documented update cadence when a regime changes. 3 7 10 5

Report an error

The In-House Counsel

GDPR is clearly operationalised through the registers and templates, and the AI Act is treated as more than a brochure item — separate AI-Regulation software, an external AI officer service, and AI systems audited with their own template, which matters for our 2026 exposure. I found no public information on BDSG, Swiss nDSG or UK GDPR support, nor a published update cadence when the law moves, so I cannot confirm the content is maintained across regimes on one record. 3 10 10 5

Report an error

The Drafted Generalist

GDPR is clearly the core with its registers and templates, and the vendor sells separate AI Act software alongside it, which covers the newest duty on the market. I found no public information on national-law variants such as BDSG, or on several regimes mapped onto one record. 3 5 1

Report an error

The Lead Auditor

The GDPR is operationalised end to end, and the vendor separately ships AI Act software with its own audit template for AI systems, so a newer regime's duties are covered as maintained content. We found no public information on BDSG, Swiss nDSG or UK GDPR support, or on requirements being mapped across regimes on one record. 3 10 5 10

Report an error

The IT Integrator

GDPR is deeply implemented with processing records, impact assessments, TOMs and Article 28 processing, and AI Act duties appear as dedicated AI regulation software plus AI-system audits with their own template. We found no public information naming BDSG, the Swiss nDSG or UK GDPR with their own templates, and the AI Act looks like a separate product rather than requirements mapped onto the same record. 3 5 10 10

Report an error

The Skeptic

The documented regime is the German GDPR market — records of processing, DPIA, TOM, Art. 28, breach registers — plus the AI Act appearing both as separate KI-Verordnung software and as an AI-system audit template inside the DSMS. We found no public information on BDSG, nDSG or UK GDPR support, or on any update cadence when a regime changes. The lawyer-drafted templates are attributed to "zertifizierten Juristen" with no names, which I note and do not count as maintained legal content. 3 10 5

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

Audits attach to a company, a department, a data recipient as a transfer impact assessment, an asset or an AI system; recurrence is configured per object, the system reminds, creates the task and files the result on the object, and the communication is logged and versioned. Period reports with configurable scope and custom-branded export templates, plus group-wide control with separate reporting levels, give me client-ready packs; I found no public information on read-only auditor access or reproducing a record as it stood on a given date. 10 10

Report an error

The In-House Counsel

This is the strongest part of the file: audit communication is logged and versioned, recurring reviews of data recipients and assets run automatically with the result persisting on the object, and period reports assemble tasks, registers, TOMs, DPIAs, breaches and external communication in my own logo and layout — group-wide, with multiple reporting levels. Lawyer-maintained or custom templates and risk or conformity outcomes per chapter round it out. I found no public information on read-only auditor access or reproducing a record as it stood on a past date. 10 11 10

Report an error

The Drafted Generalist

Audits attach to whatever they concern — whole company, department, data recipients as a transfer impact assessment, systems, even AI systems with their own template — and intervals, reminders, tasks and results are handled by the system, with communication logged and versioned and period reports you assemble yourself from registers, impact assessments, breaches and more. I found no public information on read-only access for an external auditor, which is the one thing I would still want before an inspection. 10 10

Report an error

The Lead Auditor

Audits attach to companies, departments, data recipients, assets or AI systems, run on configurable intervals where the system creates the task and keeps the result on the object, and group-wide control with several reporting levels exists — that is a standing review loop, not a week-before scramble. Period reports let you assemble tasks, VVT, TOMs, deletion concept, audits, DSFA, breaches and external communication yourself, and audit communication is logged and versioned, but we found no public information on read-only auditor access, evidence packs, or reproducing a record as it stood on a given date. 10 10 8

Report an error

The IT Integrator

Audits attach to companies, departments, data recipients as a Transfer Impact Assessment, assets and AI systems, recur on configurable intervals where the system reminds, creates the task and documents the result on the object, and end in risk matrices or conformity degrees with period reports whose contents you assemble yourself. Audit communication is logged and versioned, but we found no public information on read-only auditor access or a revision-safe history across every record. 10 10 8

Report an error

The Skeptic

Audits attach to real objects — company, department, data recipient as a Transfer Impact Assessment, asset or system, AI system — end in a risk matrix or per-chapter conformity degree, recur on configurable intervals that trigger reminders and tasks, and every communication is "protokolliert und versioniert". Period reports sweep the whole register set (tasks, data recipients, VVT, TOMs, deletion concept, audits, DSFA, breaches) with configurable layout, even in corporate design. We found no public information on read-only auditor access, on-demand evidence packs, or reproducing a record as it stood on a given date. 10 10

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

The recurring work genuinely runs itself — audit intervals per data recipient and asset with system-generated tasks and documented results, plus daily deadline escalation on breaches — and single sign-on appears in the enterprise edition. I found no public information on an API, directory or ticketing connectors, webhooks, SCIM provisioning or bulk import, which for a multi-client practice is the difference between onboarding mandates and re-typing them. 9 10 10

Report an error

The In-House Counsel

The recurring work is genuinely automated — configurable review intervals where the system reminds, creates the task and documents the result, daily breach notifications, and an automated risk assessment — which is what stops re-typing. Single sign-on sits in the on-request Enterprise tier only. I found no public information on an API, directory or ticketing connectors, webhooks, or importing data from the existing IT estate. 1 9 10 10

Report an error

The Drafted Generalist

The recurring work genuinely runs itself: audit intervals generate tasks, reminders chase the responsible people, and breach and communication deadlines trigger notifications, which is exactly the kind of thing I need software to do instead of me. Single sign-on is listed only on the enterprise tier priced on request, and I found no public information on an API, connectors to directories or ticketing, or data imports. 9 10 10

Report an error

The Lead Auditor

Recurring audits with automatic reminders and task creation, an automated risk assessment, and inheritance of resources take the repeat privacy work off hands, and single sign-on appears on the Enterprise tier. We found no public information on a documented API, named connectors, webhooks, or directory and ticketing integration. 10 10 9

Report an error

The IT Integrator

Documents export in Word, PDF and other formats, recurring audits and deadline tasks generate themselves with reminders, and single sign-on is listed — but only on the Enterprise tier priced on request. We found no public information on a documented API, webhooks, directory or ticketing connectors, or any import path, so nothing captured shows the platform feeding from a directory, ticket queue or asset inventory rather than being typed into. 10 9 10 8

Report an error

The Skeptic

What repeats does run itself to a degree: audit intervals remind, generate tasks and document the result on the object, and breach and external-communication tasks notify the responsible person daily. SSO appears only on the Enterprise tier, whose price is Auf Anfrage, and we found no public information on an API, connectors, webhooks, SCIM provisioning or data import. Note also that the captured pages give different figures for effort reduction — 50 per cent in one place, up to 70 per cent in another — while neither documents the mechanism beyond these task reminders. 1 2 9 10 10

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 contracting entity is a German GmbH in Altenberge registered at Amtsgericht Steinfurt with a German VAT number, development sits in Münster, and the captured product pages state "100% EU-Server". The independently sourced sovereignty attributes list data residency as not confirmed, and I found no public information on a data processing agreement, a subprocessor list or named data centres, so the chain that would hold my clients' compliance record is only partly documented. 10 10 5

Report an error

The In-House Counsel

A German GmbH with a commercial register entry at Amtsgericht Steinfurt, development in Münster, and 100% EU-Server stated on the product page — the entity and hosting sit where I want a corporate compliance record to sit. The captured pages document no data processing agreement and no subprocessor list, and the EU-server claim names no data centres, so the chain is not cleared end to end and a platform that maps our processing must itself survive that review. 10 10 5

Report an error

The Drafted Generalist

A German limited company in Altenberge, developed in Münster, and servers advertised as 100% EU — that much is written in black and white. I found no public information on a published data processing agreement, a subprocessor list or named data centres, so the full chain is not documented publicly. 5 10 10

Report an error

The Lead Auditor

The contracting entity is a German GmbH registered at Amtsgericht Steinfurt, the software is developed in Münster, and the vendor states 100% EU-Server, which places the compliance record under German entity law with EU hosting. We found no public information on a published data processing agreement, a subprocessor list, or named data centres, so the chain below hosting stays unproven. 5 10 10 8

Report an error

The IT Integrator

Keyed GmbH is registered at Amtsgericht Steinfurt with a German address and VAT ID, the software is developed in Münster, and the pages claim 100% EU servers as the standard. We found no public information on hosting in named data centres, a data processing agreement or a subprocessor list, so the chain is German but not documented end to end. 10 10 5

Report an error

The Skeptic

The German chain is real and verifiable: Keyed GmbH in Altenberge, Amtsgericht Steinfurt HRB 11598, VAT ID DE312621690, development in Münster, and "100% EU-Server" stated on the product page. But we found no public information on a data processing agreement, a subprocessor list, or which country the servers sit in. A vendor whose product maps its customers' processing is itself concentrated processing, and only part of that chain is documented publicly. 7 10 5

Report an error

Pricing transparency

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

Four editions are public with monthly billing: 0 € monatlich for one company with essential functions, ab 99 € monatlich for one company with all data protection functions and exports, ab 299 € monatlich for three companies with reports and inheritance, and Enterprise auf Anfrage with unlimited companies and SSO. The company-count boundary is stated but what drives the "ab" price is not, and I found no public information on user limits, setup fees or VAT treatment — beyond three clients, a consultancy lands in the unpriced tier. 1 10

Report an error

The In-House Counsel

Four tiers are public with monthly billing and inclusions named: free at 0 € monthly, Starter at "Ab 99 € monatlich" for one company, Professional at "Ab 299 € monatlich" for three companies, and Enterprise on request for large companies and groups — that last one being the genuinely custom corporate contract. What pushes above the "Ab" floor, plus setup fees and VAT treatment, is not stated. Software and the consulting offerings appear as separately listed services. 1 3 10

Report an error

The Drafted Generalist

The tiers are laid out on a public pricing page with monthly figures — Free at 0 € monatlich, Starter Ab 99 € monatlich, Professional Ab 299 € monatlich — each with its company count and main inclusions listed, while Enterprise is Auf Anfrage. I found no public information on setup fees, user limits beyond company counts or VAT treatment, so the top end stays a conversation. 10 1

Report an error

The Lead Auditor

A pricing page publishes four tiers with billing period and main inclusions — Free at 0 € monatlich, Starter Ab 99 € monatlich, Professional Ab 299 € monatlich, Enterprise Auf Anfrage — with company-count boundaries stated per tier. The Ab pricing leaves the invoice for additional companies uncomputable, and we found no public information on setup fees, VAT treatment, or software separated from consulting. 10 1

Report an error

The IT Integrator

Four tiers are public with the monthly billing period, main inclusions and company counts per tier: Free at 0 € monatlich, Starter ab 99 € monatlich, Professional ab 299 € monatlich, Enterprise auf Anfrage. What drives the "ab" scale, user boundaries, setup fees and VAT treatment are not stated, so the invoice is only partly computable in advance. 10 1

Report an error

The Skeptic

Four tiers carry public monthly figures — Free 0 € monatlich, Starter Ab 99 € monatlich, Professional Ab 299 € monatlich, Enterprise Auf Anfrage — each with company counts and inclusions, which is genuinely above the pure contact-me norm of this market. The "Ab" leaves scale steps unpublished, no user counts, setup fees or VAT treatment appear, and the consulting line — external data protection officer, KI-Beauftragter, EU Vertreter — carries no public prices at all, so software and consulting do not separate cleanly on the pricing page. 1 1 10

Report an error

European sovereignty — proven facts

1 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 unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— 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 Keyed DSMS

Is Keyed DSMS European?

Yes. whats-best.ai classifies Keyed DSMS as EU-Made. Its vendor, Keyed GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does Keyed DSMS store data?

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

Does Keyed DSMS have a free plan?

Yes. Keyed DSMS has a free plan, per the vendor’s page captured 26 Oct 2026.

What are the best alternatives to Keyed DSMS?

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: Keyed DSMS 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 (11)

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

  1. 1 Vendor homepage keyed.de Checked 16 Nov 2026 +3 earlier captures: 26 Oct 2026, 16 Sep 2026, 15 Sep 2026 Details →
  2. 2 DSMS product page keyed.de Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 26 Oct 2026, 31 Aug 2026, 24 Aug 2026 Details →
  3. 3 Vendor pricing page keyed.de Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
  4. 4 Company page keyed.de Checked 16 Nov 2026 +3 earlier captures: 26 Oct 2026, 16 Sep 2026, 15 Sep 2026 Details →
  5. 5 Imprint keyed.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 26 Oct 2026 Details →
  6. 6 Records & DPIA depth — found from sitemap help.keyed.de Checked 16 Nov 2026 Details →
  7. 7 Records & DPIA depth — found from sitemap help.keyed.de Checked 16 Nov 2026 Details →
  8. 8 Data subject rights & incidents — found from sitemap help.keyed.de Checked 16 Nov 2026 Details →
  9. 9 Data subject rights & incidents — found from sitemap help.keyed.de Checked 16 Nov 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap keyed.de Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  11. 11 Audit readiness & evidence — found from sitemap help.keyed.de Checked 16 Nov 2026 Details →