preeco | informationssicherheit

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

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

by preeco GmbH & Co. KG · www.preeco.de

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

Link to this page

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

preeco | informationssicherheit at a glance

Vendor
preeco GmbH & Co. KG
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
In the EU; pages mention Germany 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 preeco | informationssicherheit 3.5/5, the mean of 6 judges. preeco | informationssicherheit is an ISMS aimed at German practice. how scores are made
As of
Vendor pages captured 24 Aug 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

preeco | informationssicherheit alternatives, European ones first →

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

The panel's verdict

preeco | informationssicherheit is an ISMS aimed at German practice. The bench scored information security management at 8: protection needs follow BSI-Standard 200-2 with inheritance and accumulation effects, risks link to measures with owners, and incident deadlines — 24-hour early warning, 72-hour notification, one-month final report — are monitored automatically with nine templates. Sovereignty scores 8-9: a German entity in Ulm, hosting at Hetzner in Nürnberg and Falkenstein, subprocessors Hetzner (Germany) and UpCloud (Finland), a published Article 28 data processing agreement, and an on-premises variant typically for the public sector or enterprise. Controls and audit readiness sit at 7-8 on immutable SHA-256 revisions, filterable activity logs and a Statement of Applicability fed by mandatory exclusion justifications. Integrations and automation is the weak point at 5-6: the captured pages give different figures on public REST API availability, SAML2 runs only on Private Cloud and On-Premises, and evidence is uploaded or requested by link. The widest spread, 5-7 on framework coverage, concerns the single-catalogue model — one catalogue is active per organisation, and no documented control-to-multi-framework mapping appears. Pricing is an individual quote.

Report an error

Speaks for it

  • Information security management sits at 8: protection needs per BSI-Standard 200-2 with inheritance and accumulation across the asset tree, risks linked to owned measures, and incident deadlines monitored automatically with nine report templates
  • Sovereignty scores 8-9: a German entity in Ulm, Hetzner hosting in Nürnberg and Falkenstein, a published Article 28 data processing agreement with downloadable TOMs, and subprocessors Hetzner (Germany) and UpCloud (Finland)
  • Every approval creates an immutable revision with SHA-256 checksums and visual comparison, with filterable activity logs recording who did what and when
  • Mandatory exclusion justifications flow automatically into a Statement of Applicability that freezes into immutable dated versions, with the cockpit fulfilment level recalculating on every status change
  • Evidence can be requested by link from people without a user account and carries validity dates with cockpit expiry warnings before the next audit

Report an error

Held against it

  • Integrations and automation scores 5-6, with the captured pages giving different figures on public REST API availability and the interface switched off by default
  • SAML2 single sign-on is offered only for Private Cloud and On-Premises, and we found no public information on connectors to ticketing, directory or CMDB systems, on webhooks or on SCIM provisioning
  • Exactly one requirement catalogue is activated per organisation, and we found no public information on a mapping where one control satisfies several frameworks
  • We found no public information on business continuity planning or a business impact analysis
  • The vendor states that preeco itself is not ISO 27001 certified — the certification covers its Hetzner data centres only

Report an error

Best for

  • You run a German-market ISMS — protection needs per BSI-Standard 200-2, automatically monitored BSIG reporting deadlines, and catalogues for ISO 27001, NIS2 and BSI C5
  • You are a municipality or public-sector organisation needing the SiKoSH catalogue for communal information security
  • German hosting and a published Article 28 data processing agreement are hard requirements in your procurement
  • You maintain one framework at a time and want the Statement of Applicability generated from live control status rather than assembled by hand

Report an error

Avoid if

  • You need one control set answering several frameworks at once — the pages state exactly one catalogue is activated per organisation
  • Your workflow assumes evidence flows in automatically from the live estate — here evidence is uploaded or requested by link
  • You need single sign-on in the standard cloud variant — SAML2 is offered only for Private Cloud and On-Premises
  • Your compliance calendar requires a DORA catalogue now — DORA appears in the pages only as an update commitment, not a shipped catalogue

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
Asset & risk management depth 4 of 5
Controls, SoA & measures 3.5 of 5
Framework & standard coverage 3 of 5
Audit readiness & evidence 4 of 5
Integrations & automation 3 of 5
European sovereignty 4 of 5

Asset & risk management depth

Show reasoning
How this is scored

The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), inheritance of protection needs (Schutzbedarf) across assets, and security incident handling with its reporting deadlines.

0 — Not an ISMS tool; the product has no asset or risk management.

3 — A risk register with likelihood and impact, and an asset list that can be imported.

5 — Asset inventory and risk management with a configurable risk matrix, risk treatment with owners and measures, and a register for security incidents.

8 — A documented risk methodology (ISO 27005, BSI 200-3 or equivalent), protection needs inherited across asset relations, incident workflows with the NIS2 reporting deadlines (24h/72h), and risk acceptance with named owners.

10 — Risk management a certifier works inside: the complete asset-risk-treatment chain with inheritance, business continuity planning (BIA, ISO 22301 or BSI 200-4), incident reporting with export for the authority, and risk reporting for the executive level.

Report an error

The CISO

The protection-need assessment runs on the BSI-Standard 200-2 damage-scenario matrix with the maximum principle, accumulation effects of linked systems and inheritance across the whole asset tree — exactly the backbone I need — and incidents carry a real clock: reporting-deadline status is monitored automatically and nine ready templates cover early warning, notification and final report to the BSI under § 32 BSIG plus the GDPR Art. 33/34 notifications. Risk analyses let me define events, damage assessment and risk levels freely, link risks straight to measures with named responsibilities per measure, and consciously accepted residual risks are counted as accepted rather than quietly disappearing, with who-did-what-when in the activity logs. What I found no public information on is business continuity planning (BIA, ISO 22301 or BSI 200-4). 2 2 12 8 13

Report an error

The GRC Consultant

Protection needs are determined on a damage-scenario matrix with the maximum principle and inherited across the entire asset tree with accumulation effects per BSI Standard 200-2, and risk analyses — from protection-needs and threat analyses to threshold and resource assessments — are freely definable, link directly to measures, with conscious residual-risk acceptance counted separately from the fulfilment metric. Security incidents are captured with categories, severity and reporting-obligation assessment, with automatic monitoring of reporting deadlines and nine ready templates for the BSI early warning (24 hours), notification (72 hours) and final report (one month) under § 32 BSIG, plus the GDPR Articles 33 and 34 reports. We found no public information on business impact analysis or continuity planning, which keeps this off the top level. 12 13 2 18

Report an error

The Drafted IT Officer

This is an ISMS I could actually run next to my day job: assets carry protection needs for confidentiality, integrity and availability, the protection need is inherited across the whole asset tree per BSI Standard 200-2 including accumulation effects, and risk analyses let me define events, damage and risk levels to my own methodology and link each risk to the measure that reduces it, with accepted residual risks counted as accepted exceptions. Incident capture comes with severity, reporting-obligation assessment and automatic deadline monitoring, backed by nine ready templates covering the BSI 24-hour early warning, 72-hour notification and one-month final report. I found no public information on business continuity planning or a fixed ISO 27005/BSI 200-3 style risk methodology, so I stop short of the top. 12 2 18 13 14

Report an error

The Lead Auditor

The asset-risk-treatment chain is documented end to end: hierarchical assets with responsibilities, providers and data flows, protection needs assessed per BSI Standard 200-2 with inheritance over the whole asset tree and accumulation effects, risks freely defined and linked to measures with clear owners, and risk reports for management and auditors. Incident handling carries automatic monitoring of reporting deadlines with nine ready templates covering the 24-hour early warning, 72-hour notification and one-month final report to the BSI, and consciously accepted residual risks are tracked as their own status. We found no public information on business continuity planning such as a business impact analysis. 2 2 12 18 8 13

Report an error

The Evidence Integrator

The BSI-Standard 200-2 chain is fully documented: protection needs via a damage-scenario matrix under the maximum principle, with accumulation effects and inheritance across the whole asset tree, custom risk analyses with freely defined events and risk levels linked to measures, and central incident capture with nine reporting templates for the 24-hour early warning, 72-hour notification and final report to the BSI, whose deadlines are automatically monitored. Accepted residual risks sit as a distinct status with their own metric treatment. We found no public information on business continuity planning or a business impact analysis, which is what separates this level from the top of the scale. 12 13 2 18 8

Report an error

The Skeptic

Protection needs follow BSI-Standard 200-2 — damage-scenario matrix, maximum principle, accumulation effect, inheritance down the asset tree — and risks are documents with freely definable events, damage ratings and risk levels, linked to measures. Incidents are captured with severity and reporting-obligation assessment, deadline status automatically monitored against the 24-hour/72-hour/one-month BSIG schedule, with nine report templates supplied. I found no public information on business impact analysis or business continuity planning, which is what the top tier requires. 13 2 12 18

Report an error

Controls, SoA & measures

Show reasoning
How this is scored

Control catalogues, the statement of applicability, measure tracking and internal audit — whether the control side of the ISMS is operable or a checklist.

0 — No control catalogue or measures in the product.

3 — Control catalogues (such as ISO 27001 Annex A) with an implementation status per control.

5 — Controls linked to risks and to measures with owners and due dates, a statement of applicability generated from the control status, and internal audits supported with checklists.

8 — A statement of applicability always current from live control status, measure tracking with delegation and escalation, internal audit workflows with findings and corrective actions, and evidence attached to each control.

10 — The control fabric as a living system: catalogue updates versioned, audit programmes with recurring schedules, and every control answerable with linked, current evidence at any moment — all documented.

Report an error

The CISO

The SoA is the part I trust: exclusions demand a mandatory justification that flows automatically into the Statement of Applicability, which is maintained separately per loaded catalogue and freezes into immutable filed versions, and every change to a requirement's assessment feeds the cockpit fulfilment degree immediately — a statement of applicability that cannot go stale. Each requirement carries its own evidence tab with validity dates and cockpit expiry warnings, and measures have owners, status and versioning, linked to risks and protection needs. I found no public information on escalation in measure tracking or on audit findings with corrective actions as workflow objects; audits are documented as structured, scheduled and gap-free, but the findings loop is not shown. 16 8 2 17 15

Report an error

The GRC Consultant

Requirement catalogues (ISO 27001, NIS2, BSI C5, SiKoSH; BSI IT-Grundschutz, CISIS12 and VdA ISA as optional paid audit catalogues) are assessed per requirement with status, maturity and responsible persons, exclusion justifications are mandatory and flow automatically into a Statement of Applicability that can be frozen as an immutable version, and every requirement carries its own evidence tab with expiry dates and renewal warnings. Measures have owners, status and versioning, link to risks and requirements, and a measures-coverage KPI tracks the share of applicable requirements with at least one linked measure. We found no public information on escalation paths for overdue measures or on audit findings with corrective actions. 7 15 20 17 12

Report an error

The Drafted IT Officer

Requirements are assessed with implementation status, maturity and responsible people, the justification for not-applicable controls flows automatically into a Statement of Applicability that can be frozen as an immutable PDF or Word version per catalog, and the fulfillment degree updates the moment a status changes — a SoA that stays current instead of being a yearly chore. Measures carry owners, status and versioning, link to risks and protection needs, and a coverage indicator shows which applicable requirements still have no measure. Evidence attaches to each requirement and audits run structured, on schedule and gap-free with centrally available evidence; I found no public information on findings and corrective-action workflows or on delegation and escalation inside measure tracking. 16 8 15 20 17

Report an error

The Lead Auditor

The Statement of Applicability is maintained from the live assessed state of each loaded catalogue, exclusion justifications flow into it automatically, and filed versions are immutable with date and author — a SoA generated from control status rather than assembled by hand. Requirements link to measures (a coverage indicator counts requirements with at least one linked measure), measures carry owners, status and versioning, evidence sits in its own tab per requirement with validity dates, and audits run structured, scheduled and gap-free with central evidence. We found no public information on delegation and escalation in measure tracking or on audit findings with corrective actions. 16 8 20 15 17 12

Report an error

The Evidence Integrator

Exclusions with a mandatory justification flow automatically into a Statement of Applicability maintained per catalog, and the cockpit's fulfilment degree updates the moment a requirement's status changes, so the SoA reflects live control status rather than a snapshot. Measures carry clear responsibilities, status and versioning, link to risks and protection needs, and every requirement holds uploaded or link-requested evidence with validity dates; audits run structured and on recurring schedules. We found no public information on delegation or escalation for overdue measures, or on audit findings with corrective actions. 16 8 15 20 17

Report an error

The Skeptic

The Statement of Applicability is machine-fed: marking a requirement not applicable forces a mandatory exclusion justification that flows automatically into the SoA, which can be frozen as an immutable dated version, and the cockpit fulfilment level recalculates the moment a status changes. Every requirement carries its own evidence tab with validity dates, and measures have owners, status and versioning linked to risks, assets and audits. I found no public information on a findings-and-corrective-action workflow for internal audits, or on delegation and escalation in measure tracking. 7 2 2 17

Report an error

Framework & standard coverage

Show reasoning
How this is scored

Which regimes the product operationalises — ISO 27001, NIS2, TISAX/VDA ISA, DORA, BSI IT-Grundschutz, SOC 2 — and whether one control maps across them or each framework is a fresh island.

0 — No security framework built in; a generic task or document tool.

3 — One recognised framework (typically ISO 27001) delivered with its requirements and controls.

5 — Several named frameworks for its market (for example ISO 27001, NIS2, TISAX or BSI IT-Grundschutz), with controls mapped across at least two of them.

8 — Broad current coverage including NIS2, TISAX and DORA where relevant, one control satisfying many frameworks through a documented mapping, and updates published when a standard changes.

10 — Framework coverage as a living product: dozens of regimes, multi-compliance on one data basis, per-industry profiles, and a documented update cadence when the standard moves.

Report an error

The CISO

Seven regimes are named for the German market — ISO 27001, NIS2, BSI C5, BSI IT-Grundschutz, CISIS12, VdA ISA and the communal SiKoSH catalogue — with updates delivered roughly monthly and new requirements such as NIS2, DORA or GDPR changes implemented for SaaS customers at no extra cost. The mapping story stops there: exactly one requirement catalogue is active per organisation and the SoA is kept per catalogue, so the documented one-control-satisfies-many-frameworks mapping I would need for multi-compliance is not shown; the shared measures and shared asset basis between the privacy and information security products are the closest evidence, and DORA appears only as a promise of timely implementation. 7 2 2 18 1

Report an error

The GRC Consultant

For the German market the breadth is real: ISO 27001, NIS2 and BSI C5 catalogues, SiKoSH for municipal information security, and BSI IT-Grundschutz, CISIS12 and VdA ISA as optional paid audit catalogues, with roughly monthly updates said to implement new requirements such as NIS2, DORA or GDPR changes promptly. The documented model activates exactly one catalogue per organisation and maintains the Statement of Applicability separately per loaded catalogue, and we found no public information on a documented mapping that lets one control answer several frameworks at once — the multi-framework reuse I optimise for is not evidenced here. DORA appears only as an update statement, not as a delivered catalogue. 12 2 12 1

Report an error

The Drafted IT Officer

The catalog shelf is genuinely stocked for the German market: ISO 27001, NIS2 and BSI C5 load as requirement catalogs, BSI IT-Grundschutz, CISIS12 and VdA ISA come as ready audit catalogs as paid extras, there is a municipal SiKoSH catalog, and new requirements such as NIS2, DORA or GDPR updates are said to be implemented promptly with roughly monthly SaaS updates. What I did not find is a documented mapping letting one control satisfy several frameworks — exactly one catalog is activated per organization — so multi-compliance looks like parallel catalogs rather than one answered control set, which is more bookkeeping than I want as a one-person security function. 7 12 2 2 1

Report an error

The Lead Auditor

A broad German-market set is named and operable: ISO 27001 with SoA catalogues, NIS2 with a five-step implementation and reporting templates, BSI IT-Grundschutz, CISIS12, VdA ISA, BSI C5 and the municipal SiKoSH, with measures, assets and risk analyses kept on one shared data basis. Updates land roughly monthly, with new requirements such as NIS2, DORA or GDPR changes implemented promptly for SaaS customers. We found no public information on a documented mapping where one control satisfies several frameworks at once — the captured pages state that exactly one catalogue is activated per organization — and several catalogues are optional and paid. 12 7 12 18 2 1

Report an error

The Evidence Integrator

Catalogues span ISO 27001, NIS2, BSI C5, BSI IT-Grundschutz, CISIS12 and VdA ISA — the last three as optional paid audit catalogues — plus a municipal SiKoSH catalog, with roughly monthly updates that pick up new requirements such as NIS2, DORA or GDPR changes. We found no public information on a documented mapping that lets one control satisfy several frameworks at once, and DORA appears only as an update commitment rather than a delivered catalog; one capture also states exactly one catalog is activated per organization. 12 7 18 2

Report an error

The Skeptic

Seven regimes are named — ISO 27001, NIS2, BSI C5, BSI IT-Grundschutz, CISIS12, VdA ISA and the municipal SiKoSH — though the Grundschutz, CISIS12 and VdA ISA audit catalogues are optional paid extras. I found no public information on a documented mapping where one control satisfies several frameworks, and the pages state exactly one catalogue is activated per organisation; DORA appears only in a sentence about new requirements being implemented promptly, not as a shipped catalogue. 7 2 2 1

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 risks and controls, and documents attachable to records.

5 — Versioned records or a change history, standard report generators (SoA, risk report, management report), and evidence attached per control.

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

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

Report an error

The CISO

Revisions are genuinely revision-safe: every approval creates an immutable PDF/ZIP or HTML revision, integrity is verifiable through SHA-256 checksums with a visual comparison, and activity logs record who did what and when, filterable by user and period. Evidence sits on each requirement with validity dates while the cockpit flags early what must be renewed before the next audit; status and audit reports export as PDF or DOCX, can be generated automatically on a recurring schedule with notification, and filed SoA versions stay traceable so I can show which exclusion applied at which point in time. I found no public information on read-only auditor access. 2 2 20 19 16

Report an error

The GRC Consultant

Every approval creates an immutable revision as PDF/ZIP or HTML, integrity-checked with SHA-256 checksums with a visual comparison, activity logs record who did what when and are filterable by time period and user, and filed Statement of Applicability versions stay traceable with date and author. Status, audit and risk reports for management and auditors export as PDF and DOCX with recurring automatic generation and notification, and evidence carries 'Valid until' dates with cockpit warnings ahead of the next audit. We found no public information on read-only auditor access or on-demand audit evidence packs. 12 19 20 16

Report an error

The Drafted IT Officer

Every approval creates an immutable revision with SHA-256 checksums and a visual comparison, activity logs record who did what and when including administrative actions, and evidence sits permanently on each requirement with a validity date the cockpit flags before the next audit. Status and audit reports export as PDF or Word, risk reports are aimed at management and auditors, recurring reports generate themselves with email notification to the responsible person, and filed SoA versions keep it traceable which exclusion applied at which point in time. I found no public information on read-only auditor access or on self-contained evidence packs an external auditor would accept as they are. 19 20 16 19

Report an error

The Lead Auditor

Revision safety is real here: every approval creates an immutable revision in PDF/ZIP or HTML, integrity is verifiable via stored SHA-256 checksums with visual revision comparison, and activity logs record who did what and when, filterable by period and user, down to administrative actions and AI usage. Filed SoA versions keep it traceable which exclusion applied at which point in time, evidence carries validity dates with cockpit warnings before expiry, and recurring reports, audit exports and a compliance-level card with weekly trend generate automatically. We found no public information on read-only auditor access, the one element of this level we could not verify. 19 12 16 20 19 13

Report an error

The Evidence Integrator

Every approval creates an immutable revision with SHA-256 integrity checks and visual comparison, activity logs record who did what and when including administrative actions, and the SoA can be frozen as dated versions whose exclusions remain traceable over time. Evidence per requirement is uploaded or requested by link without an account, carries validity dates with cockpit expiry warnings, and status, audit and management risk reports generate automatically on recurring schedules. We found no public information on read-only auditor access. 19 2 19 16 13

Report an error

The Skeptic

Every approval creates an immutable revision verified by SHA-256 checksums with visual comparison, activity logs record who did what when and are filterable, and evidence can be requested by link from people without an account, with validity dates and cockpit expiry warnings before the next audit. Status, audit, risk and management reports recur automatically with notification. I found no public information on read-only auditor access or on a consolidated evidence pack generated on demand. 2 19 20 19

Report an error

Integrations & automation

Show reasoning
How this is scored

Whether the platform feeds from the real IT estate — directory import, CMDB, ticketing, scanners, SSO, API — and automates evidence collection 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 or CMDB), and recurring tasks with reminders and assignment.

8 — A documented REST API for the core objects, a named connector set (Jira/ServiceNow-class ticketing, CMDB, cloud and endpoint sources), webhooks, SSO with SCIM provisioning, and automated evidence tests with human review.

10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, continuous control monitoring against the live estate, and recurring evidence collection automated and documented.

Report an error

The CISO

The captured pages give different figures for API availability: one states a REST interface with read and write access across nearly all modules, JSON format and interactive OpenAPI documentation, but disabled by default and switched on per team on request, while another states no public REST API is currently available and customer-specific endpoints exist only for Private Cloud and On-Premises. SAML2 single sign-on is offered for Private Cloud and On-Premises but stated as not available in the standard cloud, and I found no public information on directory, CMDB, ticketing or scanner connectors, webhooks, SCIM provisioning or automated evidence collection from the live estate. Recurring tasks with assignment and e-mail notifications exist, and the named third-party integrations are DeepL translation and OpenAI-compatible LLM providers. 12 2 12 2 2

Report an error

The GRC Consultant

The captured pages give different statements on the interface: one full specification describes a REST interface across nearly all modules, reading and writing, with personal tokens, JSON payloads, a sixty-requests-per-minute limit, OpenAPI documentation and activation per team on request (the interface is switched off by default), while another capture of the same specification states that a public REST API is currently not available and customer-specific endpoints are developed for Private Cloud and On-Premises only. SAML2 single sign-on is available on Private Cloud and On-Premises, imports run via XLSX or individual migration projects, and recurring reports generate automatically with notification. We found no public information on connectors to ticketing, CMDB, cloud or endpoint sources, on SCIM provisioning, webhooks, or automated evidence collection. 12 2 12 2

Report an error

The Drafted IT Officer

The full product specification documents a REST interface across nearly all modules, reading and writing, with OpenAPI documentation, personal tokens and a sixty-request-per-minute limit — but the interface is switched off by default and enabled per team on request, and the captured pages give different statements on public API availability, one describing the application as a closed system. Single sign-on via SAML2 exists only on Private Cloud and On-Premises; the plain cloud shows none. I found no public information on connectors to ticketing, directory or CMDB systems, on webhooks, SCIM provisioning or automated evidence collection — evidence is uploaded or requested by link, and migrating legacy data is a paid individual project. 12 2 2 12

Report an error

The Lead Auditor

The captured pages give different figures for API availability: earlier captures describe a closed system with no public REST API and customer-specific endpoints only for Private Cloud and On-Premises, while the latest specification documents a read-write REST interface over nearly all modules, JSON with PATCH, OpenAPI documentation with a changelog, personal tokens and 60 requests per minute, released per team on request. Single sign-on via SAML2 is offered for Private Cloud and On-Premises, and recurring tasks with e-mail notifications plus automatically recurring reports are documented. We found no public information on connectors for ticketing, CMDB or scanning, on webhooks, on SCIM provisioning, or on automated evidence testing. 12 2 2 12 2 19

Report an error

The Evidence Integrator

The captured pages give different figures for the API: the latest product specification documents a read-write REST interface over nearly all modules with OpenAPI documentation and personal tokens, but switched off by default and enabled per team on request, while an earlier capture describes the application as a self-contained system with no public REST API and custom endpoints only for Private Cloud and On-Premises. The hosting comparison lists SAML2 single sign-on as "Nein" for the cloud variant and optional for the other two, and we found no public information on directory, CMDB, ticketing, cloud or endpoint connectors, webhooks or SCIM provisioning. Evidence reaches the system by upload or link request rather than from the live estate, so nothing about the control data refreshes itself. 12 2 12 2 12

Report an error

The Skeptic

The current product specification documents a REST interface over nearly all modules, read and write, with an OpenAPI file, changelog, personal tokens and a sixty-requests-per-minute limit — while also stating the interface is switched off by default and unlocked per team on request, and an earlier capture gives a different statement, saying a public REST API is not available at all. Single sign-on is SAML2 on Private Cloud and On-Premises only, plus DeepL and a configurable LLM provider; I found no public information on named connectors to ticketing, directory or CMDB sources, on webhooks or on SCIM provisioning. Evidence is uploaded or requested by hand — I found no public information on automated evidence collection. 12 2 2 12

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where the security posture 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. The risk register is itself a target. 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 CISO

The chain is documented on the vendor's own pages end to end: a German entity in Ulm registered at Amtsgericht Ulm, hosting exclusively in Hetzner data centres in Nürnberg and Falkenstein, and a published subprocessor list naming only Hetzner (Germany, hosting of customer applications) and UpCloud (Finland, internal monitoring) — both inside the EU. The Article 28(3)-(4) data processing agreement is published and can be concluded online, the TOMs are downloadable, no third-country transfer of personal data is stated, and an on-premises variant with full data sovereignty exists, though typically only for the public sector or enterprise segment. The one open point for content: the optionally configurable OpenAI-compatible LLM integration carries no statement on provider locations — AI is disabled by default and activated per team, but if I switch it on for my risk register I am buying an unknown. 10 9 5 9 11

Report an error

The GRC Consultant

A German contracting entity in Ulm develops, operates and hosts exclusively in Germany, with Cloud and Private Cloud data in named ISO 27001-certified Hetzner data centres in Nuremberg and Falkenstein and no third-country transfer. The data processing agreement is published and can be signed online with downloadable TOMs, the subprocessor list names only Hetzner Online GmbH (Germany) and UpCloud Oy (Finland) with two weeks' written change notice and an objection right, and an on-premises option exists, though the pages state it is generally available only for the public sector or enterprise segment. The optional LLM-provider integration is described without any statement on provider locations, so the chain is documented broadly but not end to end. 4 12 10 9

Report an error

The Drafted IT Officer

The whole chain is German and documented: preeco GmbH in Ulm as contracting entity, hosting exclusively at Hetzner in Nuremberg and Falkenstein in ISO 27001-certified data centers, no third-country transfers, and a published data processing agreement on GDPR Article 28 standard clauses that I can sign online, with downloadable TOMs. The subprocessor list names Hetzner in Germany and UpCloud in Finland — both EU — with two weeks' written notice of changes and a right to object, and an on-premises variant keeps data in my own data center, though the vendor says that option is typically reserved for the public sector or enterprise customers. The optional, configurable LLM provider integration is the one open question, as the captured pages make no statement about where such a provider would process content. 4 9 10 5 9

Report an error

The Lead Auditor

A German contracting entity in Ulm hosts Cloud and Private Cloud in named Hetzner data centres in Nuremberg and Falkenstein, with published subprocessors Hetzner (Germany) and UpCloud (Finland), no third-country transfer of personal data, and a published data processing agreement on Article 28 GDPR standard clauses that can be concluded online, with TOMs downloadable. On-premises operation with full data sovereignty is offered, typically restricted to the public sector or enterprise segment. The pages make no statement on where the optionally configurable LLM provider integration processes data. 9 12 10 10 5 9

Report an error

The Evidence Integrator

A German entity in Ulm contracts, hosting sits in named ISO 27001-certified Hetzner data centres in Nuremberg and Falkenstein with no third-country transfer, and the published subprocessor list names only Hetzner Online GmbH in Germany and UpCloud Oy in Finland. The data processing agreement is published with GDPR Article 28 standard clauses, signable online, with TOMs downloadable and two weeks' written notice plus objection rights on subprocessor changes; an on-premises variant keeps data in the customer's own data centre, though typically for the public sector or enterprise segment. We found no public information on where the optionally configurable LLM provider integration processes data, which leaves one link in the chain unstated. 4 9 10 9 10

Report an error

The Skeptic

German entity in Ulm, hosting exclusively at Hetzner in Nürnberg and Falkenstein in ISO 27001-certified centres with no third-country transfer, a published data processing agreement on Art. 28 standard clauses with downloadable TOMs, and a subprocessor list naming only Hetzner (Germany) and UpCloud (Finland). An on-premises variant where data never leaves the customer's data centre is documented. The one gap: for the optional, per-team-activated LLM provider integration the pages state no location, and the vendor says plainly that preeco itself is not ISO 27001 certified — only its data centres are. 9 10 4 12

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 scale steps 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 certification project is a two-minute exercise.

Report an error

The CISO

No euro figure is public: the licence and price model for the information security product is created as a separate individual offer depending on the employee count of the whole organisation, the chosen modules and the hosting variant, with risk analyses, audits and the training function licensed as their own modules and the audit catalogues, DeepL, data migration and premium support all optional and paid. What is public is structure, not invoice: an annual subscription including updates, maintenance and support, with no setup fees and no cancellation periods — a buyer still cannot compute a price from these pages. 12 12 2 13

Report an error

The GRC Consultant

The licensing and pricing model is prepared as a separate, individual offer depending on the employee count of the whole organisation, the chosen modules and the hosting variant; we found no public prices for any edition, module or catalogue on the captured pages. Publicly stated: annual subscription with updates, maintenance and support included, no setup fees and no cancellation periods, with BSI IT-Grundschutz, CISIS12 and VdA ISA catalogues optional and paid. 12 12 2

Report an error

The Drafted IT Officer

No euro figure is public — the licensing and price model is prepared as a separate, individual offer depending on the employee count of the whole organization, the chosen modules and the hosting variant, so every invoice starts with a sales conversation and I cannot budget from the website alone. To the vendor's credit the cost structure is stated plainly: no setup fees and no cancellation notice periods, an annual subscription that already includes updates, maintenance and support, and the paid extras such as the BSI IT-Grundschutz, CISIS12 and VdA ISA catalogs, DeepL translation, migration support and premium support are named as optional and paid rather than hidden. 12 12 2 2

Report an error

The Lead Auditor

We found no public price figures: the licensing and pricing model is prepared as a separate, individual offer depending on the employee count of the whole organization, the chosen modules and the hosting variant. The pages do state annual subscription billing with updates, maintenance and support included, no setup fees and no cancellation notice, and that the audit catalogues, DeepL translation and data migration are optional and paid — pricing structure without any computable numbers. 12 12 2 2

Report an error

The Evidence Integrator

Pricing is an individual offer: the product specification states the licence and price model is prepared as a separate, individual quote depending on the employee count of the whole organization, the chosen modules and the hosting variant, with risk assessments licensed as their own module and the BSI IT-Grundschutz, CISIS12 and VdA ISA catalogues optional and paid. The pages do publish the commercial frame — annual subscription with updates, maintenance and support included, no setup fees, no notice periods — but we found no public information on price figures for any edition or module. 12 12 2 13

Report an error

The Skeptic

No public price anywhere: the licence and pricing model is prepared as a separate individual offer depending on the employee count of the whole organisation, the chosen modules and the hosting variant. The structure is disclosed — annual subscription with updates, maintenance and support included, no setup fees, no cancellation notice — but the Grundschutz, CISIS12 and VdA ISA catalogues are marked optional and chargeable with no figure attached, so an invoice cannot be computed from any captured page. 12 12 2 2

Report an error

European sovereignty — proven facts

4 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?

Die Aussage betrifft Cloud und Private Cloud; On-Premises-Kunden hosten selbst, und zur optional konfigurierbaren LLM-Provider-Integration macht die Seite keine Angabe.

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

Die Seite schränkt ein, dass On-Premises in der Regel nur im öffentlichen Bereich oder im Enterprise-Segment zur Verfügung steht.

1/1 pts 9 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined unverified
Why unverified?

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

— uncited Report an error
Transfer impact assessment Not needed, no transfer outside the EU/EEA unverified
Why unverified?

Die Aussage steht im Abschnitt zu Cloud und Private Cloud; zur optional konfigurierbaren LLM-Provider-Integration macht die Seite keine Angabe zu Standorten.

1/1 pts 9 Report an error

Questions about preeco | informationssicherheit

Is preeco | informationssicherheit European?

Yes. whats-best.ai classifies preeco | informationssicherheit as EU-Made. Its vendor, preeco GmbH & Co. KG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does preeco | informationssicherheit store data?

preeco | informationssicherheit stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 2 Nov 2026.

Does preeco | informationssicherheit have a free plan?

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

What are the best alternatives to preeco | informationssicherheit?

As of 18 Nov 2026, the panel rates 6clicks (3.5/5), Secfix (3.5/5) and HiScout GRC Suite (3.5/5) highest among the other 35 Information Security 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 HiScout GRC Suite (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: preeco | informationssicherheit 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 (20)

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

  1. 1 Vendor homepage www.preeco.de Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026, 15 Sep 2026, 24 Aug 2026 Details →
  2. 2 Information security product page www.preeco.de Checked 16 Nov 2026 +5 earlier captures: 19 Oct 2026, 5 Oct 2026, 16 Sep 2026, 15 Sep 2026, 24 Aug 2026 Details →
  3. 3 About page www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 Imprint www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 Privacy policy www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  6. 6 Product documentation library www.preeco.de Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 5 Oct 2026, 24 Aug 2026 Details →
  7. 7 SoA automation doc www.preeco.de Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 15 Sep 2026, 24 Aug 2026, 24 Aug 2026 Details →
  8. 8 ISMS cockpit metrics doc www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 24 Aug 2026 Details →
  9. 9 Hosting variants page www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 16 Sep 2026 Details →
  10. 10 Published DPA (AVV) for cloud customers www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  11. 11 Multi-entity use case page www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  12. 12 Full product specification (Leistungsbeschreibung) www.preeco.de Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 19 Oct 2026, 5 Oct 2026, 16 Sep 2026, 24 Aug 2026 Details →
  13. 13 Asset & risk management depth — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  14. 14 Asset & risk management depth — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  15. 15 Controls, SoA & measures — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  16. 16 Controls, SoA & measures — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  17. 17 Framework & standard coverage — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
  18. 18 Framework & standard coverage — found from sitemap www.preeco.de Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026 Details →
  19. 19 Audit readiness & evidence — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
  20. 20 Audit readiness & evidence — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →