audatis MANAGER

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by audatis Group GmbH · www.audatis-manager.de

Compare with Robin Data ComplianceOS → Compare with preeco | datenschutz → Report an error on this page Is this your product? →

Link to this page

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

audatis MANAGER at a glance

Vendor
audatis Group GmbH
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
In the EU source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates audatis MANAGER 3/5, the mean of 6 judges. audatis MANAGER is a German data protection and compliance platform, strongest on privacy management and sovereignty at 6–7. how scores are made
As of
Vendor pages captured 23 Aug 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

audatis MANAGER alternatives, European ones first →

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

The panel's verdict

audatis MANAGER is a German data protection and compliance platform, strongest on privacy management and sovereignty at 6–7. The record of processing activities is the engine: six industry template packs of 65 to 77 activities, delegation to departments, an export in authority-register format, plus DPIA, processor and TOM modules. Sovereignty rests on a German entity, hosting in a German data centre at IONOS in Montabaur, and an own-server option in the Whitelabel tier; we found no public information on a customer-facing data processing agreement, and the captured pages give different names for the operating company. The widest spread is rights and incidents at 2–4: the same missing pieces — breach register, 72-hour clock, deadline tracking — are weighted harder by the lowest score, which holds an Article 33 process cannot be defended on this evidence. Integrations and automation, at 3–4, is a second weak point: no public information on an API, single sign-on or directory import; records stay manually maintained. Framework coverage and audit readiness cluster at 6. Every price line reads "Auf Anfrage"; a 30-day non-binding trial is offered.

Report an error

Speaks for it

  • Record of processing seeded by six industry template packs of 65 to 77 activities, with group templates, delegation to department owners and export as the authority register
  • German entity, hosting at IONOS in Montabaur, an own-server option in the Whitelabel tier and a published subprocessor list
  • Current DSGVO, BDSG, DSG, EKD and KDG legal texts with a professionally reviewed update service delivered into the product
  • Edit history for input control, revision-safe online confirmation of employee attestations, and reports drawing KPIs from the system
  • Multi-client tiers for external data protection officers, with 2 tenants in Group and 46 in Whitelabel

Report an error

Held against it

  • Rights and incidents scores run 2 to 4, with no public information on a breach register, the 72-hour clock or deadline tracking for requests
  • We found no public information on an API, single sign-on, directory import or webhooks, so records are maintained by manual entry
  • We found no public information on activities linked through to processors, TOMs and legal bases, or on DPIA need derived from the record
  • The captured pages give different names for the operating company, audatis Services GmbH in the imprint and copyright and audatis Consulting GmbH once in the privacy policy, without explaining the relationship
  • We found no public information on a customer-facing data processing agreement for the platform itself

Report an error

Best for

  • You run data protection for a German mid-sized company, public authority or church institution and want template-driven records built on DSGVO, BDSG, DSG, EKD and KDG
  • You are an external data protection officer with several mandates and need multi-client tiers with reusable group templates
  • You need authority-ready output on demand — the register export in authority format, an edit history for input control and revision-safe attestations

Report an error

Avoid if

  • You need operational breach management; the pages show central request handling and a deletion concept, and we found no public information on a breach register or the 72-hour clock
  • Your records must stay current through connectors to your IT estate; we found no public information on an API, single sign-on or directory import, so entries are typed manually
  • You need AI Act or ePrivacy duties mapped on one record; we found no public information on either

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.5 of 5
Data subject rights & incidents 2 of 5
Privacy regime coverage 3 of 5
Audit readiness & evidence 3 of 5
Integrations & automation 2 of 5
European sovereignty 3.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

The record of processing activities is clearly the engine: it can be generated at the push of a button, filled in by delegated department contacts, exported as an internal or authority register, and reused through group templates and industry packs holding 65 to 77 pre-built processing activities, with DPIA, processor agreement and TOM modules plus multi-client tiers aimed at external data protection officers. What the captured pages do not show is TOMs or legal bases explicitly linked to each processing activity, so I stop short of a fully connected data model. This is nonetheless the reusable-template core a thirty-mandate practice runs on. 4 2 3 4

Report an error

The In-House Counsel

The record of processing activities is deeply evidenced: generated at the push of a button, filled in by delegated department contacts, kept with an edit history, exported as an internal or authority register, and seeded with sector template packs of 65 to 77 activities; DPIAs with risk management, processor agreements with an automatically generated processor register, and TOMs with over 200 text modules are documented, alongside multi-client tiers for external data protection officers. The captured pages do not show a connected model deriving DPIA need from the record, which holds it just under the fully connected level. 2 4 4 3

Report an error

The Drafted Generalist

The records of processing module is genuinely deep: over 400 pre-filled processing activities across six industry template packs, every activity savable as a template, delegation to the departments who know the answers, and an export already formatted as the official authority register. TOMs, processor agreements and DPIAs with risk management are all there as modules. We found no public information showing one activity connected through to processors, TOMs and legal bases with DPIA need derived from the record — that connection is what would let the software know the law instead of me. 4 2 4

Report an error

The Lead Auditor

The record of processing activities is properly built: sector template packs of 65 to 77 activities, any activity saveable as a template, group templates across organizational units, completion delegated to department owners, and an export as an internal or official register for the supervisory authority. DPIA with risk management, processor agreements, and TOMs with over 200 text blocks are documented modules, and multi-client capability for external data protection officers exists in the higher tiers. We found no public information on a connected model linking activities to systems, processors, TOMs and legal bases, or on DPIA need derived from the record. 4 2 3 4

Report an error

The IT Integrator

The record of processing activities is genuinely modelled — six industry template packs of 65 to 77 activities, group templates, delegation to department owners, and an export as internal or authority register — alongside a DPIA module with risk management, processor agreements and TOM text blocks. What the pages do not show is the connected model: nothing states activities are linked to systems, processors or TOMs, or that DPIA need is derived from the record itself. 4 2 3 4

Report an error

The Skeptic

The record of processing activities is clearly built out — six industry template packs with named activity counts, per-activity reuse as templates, group templates, delegation to department contacts, and export as an internal or official authority register. DPIA, processor agreements and TOMs each exist as modules with template text, but the pages never show activities linked to systems, processors, TOMs and legal bases in one model, or DPIA need derived from the record. Multi-client use for external data protection officers is stated for the Group and Whitelabel editions. 4 2 3 4

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 are managed centrally with response templates and there is a task and workflow layer, plus a deletion concept recording retention periods, storage locations and deletion classes. I found no public information on a data breach register, the 72-hour clock, or tracking of the one-month response deadline, which caps this well below operational incident readiness. 2 3

Report an error

The In-House Counsel

Requests of all types are managed centrally and answered from templates, and a deletion concept with retention periods, storage locations and deletion classes is documented. We found no public information on deadline tracking for requests, identity verification, a breach register or the 72-hour notification — without a documented breach clock I cannot defend an Article 33 process on this evidence, which caps the score at the entry level. 2 3

Report an error

The Drafted Generalist

Data subject requests of all types are managed centrally and answered from templates, and a deletion concept with deadlines, storage locations and deletion classes is provided. We found no public information on a breach register with the 72-hour clock, or on the one-month deadline being tracked with reminders — and the Friday-afternoon breach is exactly the day I need software to walk me through it. 2 3

Report an error

The Lead Auditor

Requests from data subjects of all kinds are managed and answered centrally from templates, and a deletion concept with retention periods, storage locations and deletion classes is created in the product. We found no public information on the one-month deadline being tracked with reminders, on a breach register with the 72-hour clock, or on deletion execution being evidenced. 2 3

Report an error

The IT Integrator

Data subject requests of all types are managed centrally with response templates, and a deletion concept with deletion periods, storage locations and deletion classes is in the product. We found no public information on a breach register, a 72-hour clock, or deadline tracking and reminders for requests, so this stays below the operational level. 2

Report an error

The Skeptic

Requests from data subjects are managed centrally with response templates, and a deletion concept with deletion deadlines, storage locations and deletion classes is a named feature. We found no public information on deadline tracking with reminders, an intake portal with identity verification, or any breach register and 72-hour clock. That leaves the operational half standing at central request logging plus a deletion concept. 2

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

DSGVO, BDSG, DSG, EKD and KDG are named as the current legal basis, with current legal texts in the product, professionally vetted privacy updates delivered in, and regular updates stated; the platform also names ISO 27001, NIS-2/BSIG, CRA and TISAX. I found no public information on AI Act or ePrivacy duties or on requirements mapped across regimes on one record, so this sits above national-law support but below the mapped multi-regime level. 1 2 3

Report an error

The In-House Counsel

The stated legal basis is GDPR together with BDSG, DSG and the church statutes EKD and KDG — coverage matching the authorities and church institutions the vendor targets — and current statute texts plus a professionally vetted legal update service delivered into the product answer my concern about unmaintained legal content. We found no public information on mapping several regimes across one record or on newer duties such as the AI Act or TTDSG, so it sits just under that level. 3 2 1

Report an error

The Drafted Generalist

DSGVO and BDSG are named as the legal basis the product runs on, together with the German church laws (DSG, EKD, KDG), current legislative texts and a professionally reviewed update service delivering legal changes straight into the tool — that last one matters because I cannot watch the law myself. We found no public information on AI Act or ePrivacy duties, or on requirements being mapped across regimes on one record. 2 3

Report an error

The Lead Auditor

The stated legal basis covers DSGVO, BDSG, DSG, EKD and KDG — GDPR plus national and both church regimes, consistent with the stated target of church institutions — backed by current legislation texts, regular updates and a professionally reviewed update service delivered into the product. We found no public information on requirements mapped across regimes on one record, or on UK GDPR, TTDSG/ePrivacy or AI Act privacy duties. 1 2 3

Report an error

The IT Integrator

GDPR is the base with BDSG, the Swiss DSG and the church laws EKD and KDG named as the current legal basis, and a professionally checked legal-update service delivers regime changes directly into the product. We found no public information on AI Act or ePrivacy duties or on one record being mapped across regimes, so this sits above plain national coverage but below multi-regime mapping. 2 3

Report an error

The Skeptic

The pricing page states the legal basis as GDPR, BDSG, Swiss DSG and the two German church laws EKD and KDG, backed by current legal texts and an update service the vendor calls professionally reviewed — without naming who does the reviewing. That is GDPR plus several national and church regimes with maintained content, but we found no public information on the EU AI Act or TTDSG, or on whether one record maps across regimes. 2 3

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

An edit history for input control, revision-safe staff evidence confirmations, reports that pull KPIs from the system automatically, and the authority-register export give me client-ready output for a supervisory conversation. What the pages do not show is on-demand audit evidence packs, read-only auditor access, or documents attached per processing activity. 4 2 4

Report an error

The In-House Counsel

An edit history expressly framed as input control, revision-safe online confirmations of employee commitments, an export formatted as the official authority register, and activity reports drawing KPIs directly from the system give me defensible proof for a supervisory authority visit. We found no public information on read-only auditor access or evidence packs generated on demand, which is what would lift it further. 4 4 2

Report an error

The Drafted Generalist

The edit history exists specifically to satisfy input-control accountability, employee attestations are confirmed online in revision-safe form, and reports pull information and KPIs from the system automatically, with the authority-register export available at a click. We found no public information on read-only auditor access or self-contained audit evidence packs, so I cannot say an authority audit walks through it unassisted. 4 2 4

Report an error

The Lead Auditor

An edit history on processing activities serving input control, revision-safe online confirmation of employee commitments and policy adherence, and reports drawing automatically on the system's information and KPIs — with exports distinguished as internal versus authority registers — give a defensible baseline. We found no public information on audit evidence packs generated on demand, read-only auditor access, or reproducing a record's state on a given date, which is the level I hold a DSMS to. 4 2 3 4

Report an error

The IT Integrator

An edit history for input control, revision-safe online confirmation of employee attestations, report management drawing KPIs from the DSMS, and the authority-register export give a defensible current state. We found no public information on audit evidence packs generated on demand or read-only auditor access. 4 2 4

Report an error

The Skeptic

An edit history for input control on processing activities, employee attestations confirmable online in revision-safe form, reports that draw automatically on the system's KPIs, and export of the register in authority format give real evidence value. We found no public information on audit evidence packs generated on demand or read-only auditor access. That sits above plain register reports but short of a standing audit state. 4 2 4

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

Workflow integration, delegation of processing activities to responsible users, CSV and Word export, and an integrable ticket system in the top tier are documented. I found no public information on an API, single sign-on, directory import or SCIM provisioning — the plumbing a multi-client practice needs to avoid re-typing thirty client estates. 4 2 3 4

Report an error

The In-House Counsel

The recurring privacy work is genuinely automated — records created at a button press, filling delegated to department users, tasks assigned to responsible parties, exports in CSV and Word — and the top tier can integrate the customer's own ticket system. We found no public information on a documented API, single sign-on, directory import or SCIM provisioning, so for a real IT estate the inventory is retyped. 4 4 2 3

Report an error

The Drafted Generalist

Filling of processing activities can be delegated to responsible department users, tasks are assigned and workflow-integrated, exports go to CSV and Word, and an own ticket system can be embedded on the top tier. We found no public information on an API, single sign-on or directory import — so the real IT estate and the privacy records stay strangers, and the typing stays with me. 4 2 3 4

Report an error

The Lead Auditor

Exports to CSV or Word, task assignment across the organization, delegation of record completion to responsible users, workflow integration, one-click record creation and ticket-system attachment in the top tier are documented. We found no public information on data import, single sign-on, a documented API, or directory and HR connectors, so the platform's feed from the real IT estate rests on manual entry. 4 2 3

Report an error

The IT Integrator

From my bench this is the weak point: nothing in the estate feeds the compliance record. Processing activities export to CSV or Word, workflow integration and delegation exist, and the top whitelabel tier can bind in an own ticket system, but we found no public information on a documented API, single sign-on, directory import or webhooks — the data stays current because someone retypes it. 4 3 4

Report an error

The Skeptic

Export of processing activities in CSV or Word, task and workflow management with delegation to responsible departments, and an embeddable own ticket system in the whitelabel tier are what the pages show. We found no public information on an API, single sign-on, directory or asset import, or webhooks — the connectors to the real IT estate are undocumented. 4 2 3

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

A German contracting entity, hosting stated at a data centre in Germany across the hosted tiers, an own-server option in the top tier, and a published subprocessor list naming the website's processors are proven; one website monitoring processor is described with a US operator address. The captured pages give different company names — the privacy policy once names audatis Consulting GmbH while the imprint and copyright name audatis Services GmbH — and I found no public information on a customer data processing agreement or published TOMs. 5 3 6

Report an error

The In-House Counsel

The contracting entity is German (audatis Services GmbH, Herford, registered at Amtsgericht Bad Oeynhausen), the hosted tiers run in a data centre in Germany, the top tier offers the customer's own server, and the privacy policy names the website's processors together with a data processing agreement with IONOS. We found no public information on a data processing agreement for the platform itself or its subprocessor list, and the captured pages give different names for the operating company — Services GmbH in the imprint and copyright, Group GmbH and a Consulting GmbH elsewhere. 5 3 6

Report an error

The Drafted Generalist

A German GmbH in Herford, hosting named in a German data centre with an own-server option on the top tier, and an openly published processor list — mostly German names, plus Microsoft in Ireland and Elastic given with a San Francisco address for website monitoring. We found no public information on a customer-facing data processing agreement for the product itself, and the captured pages name audatis Services GmbH and, once, an audatis Consulting GmbH without explaining the relationship, so the chain is close but not proven end to end. 5 3 6

Report an error

The Lead Auditor

A German contracting entity, hosting in a named German data centre as the default across the hosted tiers, and an own-server option in the top tier sit well for a platform that maps one's own processing. The published subprocessor list names Elasticsearch B.V. with a San Francisco address for monitoring, and we found no public information on a customer data processing agreement or published TOMs. The captured pages also give different operator names — audatis Services GmbH in imprint and copyright, audatis Consulting GmbH once in the privacy policy — without stating the relation. 5 3 6

Report an error

The IT Integrator

audatis Services GmbH of Herford hosts the standard and group tiers in a named German data centre at IONOS in Montabaur, holds its own processing agreement with the hoster, and offers an own-server option in the whitelabel tier. We found no public information on a published customer-facing data processing agreement for the platform, and the privacy policy's service list names a US-addressed provider (Elastic) for website monitoring. 5 3 6

Report an error

The Skeptic

A German entity with register court and number, a German data centre as the default for the hosted tiers and an own-server option on the top tier, plus a published subprocessor list, are proven. Gaps a buyer should weigh: we found no public information on a customer data processing agreement, one listed processor is addressed in San Francisco (Elastic), and the captured pages give different names for the operating entity — the imprint says audatis Services GmbH while the privacy policy once references audatis Consulting GmbH without explaining the relationship. 5 3 6

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

Every figure is "Auf Anfrage" — the standard edition, the ISMS add-on, extra users, storage and the annual flatrate tiers alike — so no invoice can be computed from the public pages. The tier structure, included users and tenants, and a 30-day non-binding trial are public, which is structure without a single published price. 3 4

Report an error

The In-House Counsel

Every figure on the pricing page reads "Auf Anfrage" — the standard edition, additional users, extra storage, the ISMS module and the annual flatrate tiers — so a buyer cannot compute any part of the invoice from public pages; only the edition structure, included user counts and a non-binding 30-day trial are public. That is a sales conversation, not a price. 3 4

Report an error

The Drafted Generalist

Every price on the pricing page is "Auf Anfrage" — the Standard edition, additional users, extra storage, the ISMS add-on, all of it — so the real invoice is unknowable without a sales conversation; only the 30-day non-binding trial is public. The editions and add-ons are laid out clearly, which helps me know what to ask for, but I cannot compute a budget from these pages. 3 4

Report an error

The Lead Auditor

Every price on the public pages is stated as "Auf Anfrage" — the standard edition, the Compliance + ISMS module, storage per gigabyte, each ten additional users, and the annual flatrate tiers alike — with invoice as the payment method. Tier inclusions (10 users, 2 tenants, 46 tenants) and a non-binding 30-day trial are public, but with no figure published the real invoice cannot be computed from public pages. 3 4

Report an error

The IT Integrator

Editions with included user and tenant counts, named add-ons and a 30-day non-binding trial are public, but every price line — standard, per ten users, per gigabyte of storage, the ISMS module, the flatrate — reads "Auf Anfrage". The invoice is computable only through a sales conversation. 3 4

Report an error

The Skeptic

Every price on the captured pricing page reads "Auf Anfrage" — the standard edition, every add-on from extra users to storage to the annual flatrate tiers — so no invoice can be computed from public pages. Tier structure, inclusions, payment by invoice and a 30-day non-binding trial are public; the numbers are not. 3 4

Report an error

European sovereignty — proven facts

3 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 EU only unverified
Why unverified?

The statement is pricing-page feature copy naming only the data-centre location, with no explicit "only in Germany/EU" wording, and the Whitelabel tier's "eigener Server" option puts location under customer control.

4/4 pts 3 Report an error
Hosting options Self-hostable unverified
Why unverified?

The own-server option appears only in the top Whitelabel tier; Standard and Group are hosted in the German data centre.

1/1 pts 3 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 audatis MANAGER

Is audatis MANAGER European?

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

Where does audatis MANAGER store data?

audatis MANAGER stores customer data in the EU, per the vendor’s page captured 16 Nov 2026.

Does audatis MANAGER have a free plan?

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

What are the best alternatives to audatis MANAGER?

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: audatis MANAGER 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 (6)

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

  1. 1 Vendor homepage www.audatis-manager.de Checked 16 Nov 2026 Details →
  2. 2 Features page www.audatis-manager.de Checked 16 Nov 2026 +1 earlier capture: 24 Aug 2026 Details →
  3. 3 Vendor pricing page www.audatis-manager.de Checked 16 Nov 2026 +5 earlier captures: 24 Aug 2026, 24 Aug 2026, 24 Aug 2026, 23 Aug 2026, 23 Aug 2026 Details →
  4. 4 RoPA feature page www.audatis-manager.de Checked 16 Nov 2026 +5 earlier captures: 19 Oct 2026, 24 Aug 2026, 24 Aug 2026, 23 Aug 2026, 23 Aug 2026 Details →
  5. 5 Imprint www.audatis-manager.de Checked 16 Nov 2026 Details →
  6. 6 Privacy policy www.audatis-manager.de Checked 16 Nov 2026 +1 earlier capture: 31 Aug 2026 Details →