SECJUR Digital Compliance Office (ISMS)
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by secjur GmbH · www.secjur.com
Compare with Vanta → Compare with DataGuard ISMS → Report an error on this page Is this your product? →
Link to this page
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.
SECJUR Digital Compliance Office (ISMS) at a glance
- Vendor
- secjur GmbH
- 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 SECJUR Digital Compliance Office (ISMS) 3/5, the mean of 6 judges. SECJUR's Digital Compliance Office is the ISMS side of secjur GmbH's compliance platform; a dedicated expert takes on 80% of the work. 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
SECJUR Digital Compliance Office (ISMS) alternatives, European ones first →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
SECJUR's Digital Compliance Office is the ISMS side of secjur GmbH's compliance platform; a dedicated expert takes on 80% of the work. Its strength is framework coverage, a flat 8: fourteen named regimes including ISO 27001, NIS2, TISAX, DORA, SOC 2 and the EU AI Act on one shared data basis, controls mapped across frameworks. Integrations and automation score a flat 7 — REST API, sixty-plus connectors, an MCP server, automated control checks filing live evidence. The middle holds: information security management at 5-6, controls and statement of applicability at 6-7, audit readiness a flat 6, with no public information on a named risk methodology, read-only auditor access or the 24-hour and 72-hour NIS2 reporting deadlines. Pricing transparency is the weak point at 0 to 2: the fixed-price model is public in words, but no price figure appears anywhere. Judges split on sovereignty, 4 to 6 — development, hosting and support stated fully in Germany, but the statement is homepage marketing not corroborated by a data processing agreement or subprocessor list, and the vendor's own website runs on a US host.
Speaks for it
- Framework coverage scores a flat 8 — fourteen named regimes from ISO 27001, NIS2 and TISAX to DORA, SOC 2, the EU AI Act and the VdS standards on one shared data basis, with controls mapped across frameworks.
- Integrations and automation score a flat 7 — more than sixty named connectors across cloud, identity, DevOps and HR, a REST API, an MCP server into AI tools, and file import for asset, risk and supplier registers.
- Automated control checks bind live-estate evidence to controls, with an Azure configuration check linked to control A.8.9 documented as an example.
- The pricing model is public in words — planable package prices, all costs known at project start, unlimited consulting at a fixed price, and no day-rate billing.
- Documentation is described as revision-safe, central, linked and versioned, with document packages and a public Trust Center.
Held against it
- We found no public price figure — no euro amount, edition price or per-user rate, only a package name ('SECJUR Standard') without an amount — so pricing transparency scores between 0 and 2.
- The captured pages give different savings figures — '50% günstiger' and 'bis zu 67% günstiger' than consultants — which we report without reconciling.
- 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, leaving audit readiness at a flat 6.
- The recorded residency is EU-only, but the claim is homepage marketing not corroborated by a platform data processing agreement or subprocessor list, and the privacy policy discloses that secjur.com itself is hosted by Webflow, Inc. in the USA — sovereignty scores span 4 to 6.
- Internal audit and management review are presented as services the vendor's expert performs, and we found no public information on delegation and escalation in measure tracking or on corrective actions for audit findings.
Best for
- You juggle several regimes at once — ISO 27001 alongside NIS2, TISAX, DORA, SOC 2 or the EU AI Act — and want one control set implemented once and reused across all of them.
- Your security function is small or part-time and you want a dedicated expert who takes on 80% of the build, with unlimited consulting at a fixed price.
- You want evidence collected continuously from your existing stack — AWS, Azure, Okta, Jira and Personio among more than sixty named connectors — rather than assembled by hand before each audit.
Avoid if
- You must compute or compare costs before a sales conversation — we found no public price figures, and the real invoice remains a sales conversation.
- You need internal audit, management review and corrective actions as workflows your own team runs in the tool — the vendor's expert performs these as services, and we found no public information on delegation, escalation or corrective-action workflows.
- Your procurement requires a published platform data processing agreement and subprocessor list before signature — we found no public information on either, and the Germany hosting claim rests on homepage marketing.
The scores
| Criterion | Panel median |
|---|---|
| Asset & risk management depth | 2.5 of 5 |
| Controls, SoA & measures | 3 of 5 |
| Framework & standard coverage | 4 of 5 |
| Audit readiness & evidence | 3 of 5 |
| Integrations & automation | 3.5 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 0.5 of 5 |
Asset & risk management depth
Show reasoningHide 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.
The CISO
Asset management with criticality, risk assessment, treatment and tracking, and an incident register with capture, assessment and reporting are all documented, plus NIS2 reporting processes for Germany and Austria and automated risk simulations with a ROSI calculator. But we found no public information on a documented risk methodology, protection-need inheritance across asset relations, the 24/72-hour incident clocks, or risk acceptance with named owners. 4 2 8 9
The GRC Consultant
The Digital Compliance Office keeps assets (held by criticality), risks that are assessed, treated and tracked, measures, incidents that are captured, assessed and reported, and the SoA in one place, plus automated risk simulations with a ROSI calculator and file import for asset, risk and supplier registers. For the depth I run clients at, we found no public information on a documented risk methodology, protection-need inheritance across asset relations, risk acceptance with named owners, or the 24-hour and 72-hour NIS2 deadlines behind the reporting processes they cite. 4 2 8
The Drafted IT Officer
The platform modules give me the working middle of an ISMS: assets held by criticality, risks that are assessed, treated and tracked, measures, and an incident register that records, evaluates and reports. Automated risk simulations with a return-on-security-investment calculator even help me explain spend to my boss. I found no public information on a documented risk methodology, on protection needs inherited across asset links, or on the NIS2 24-hour and 72-hour reporting clocks, so I stop short of the top marks. 4 2 8
The Lead Auditor
Asset inventory with criticality, risk assessment, treatment and tracking, and an incident register with capture, assessment and reporting are all documented, plus automated risk simulations with a ROSI calculator. We found no public information on a named risk methodology such as ISO 27005 or BSI 200-3, inheritance of protection needs across asset relations, or the NIS2 24h/72h reporting deadlines — NIS2 appears only as risk management, reporting processes and evidence. 4 2 9 8
The Evidence Integrator
Asset management with criticality, risk assessment, treatment and tracking, and incident capture, assessment and reporting are all named modules, plus automated risk simulation with a ROSI calculator and NIS2 reporting processes for Germany and Austria. We found no public information on a documented risk methodology, protection-need inheritance across asset relations, or the 24-hour and 72-hour reporting deadlines, so the documented depth stays at the functional core. 4 8 2
The Skeptic
The platform's own module list shows asset management with criticality, risk assessment, treatment and tracking, an incident module for capturing, assessing and reporting incidents, NIS2 reporting processes, and a ROSI-based risk simulation — a genuine mid-level ISMS core. We found no public information naming a risk methodology, protection-need inheritance across asset relations, or the 24h/72h reporting deadlines, and much of the build is described as performed by the vendor's expert rather than the tool. 4 8 2 9
Controls, SoA & measures
Show reasoningHide 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.
The CISO
Controls and their evidence sit together with one control reused across frameworks, measures and the statement of applicability are maintained in one place, audits run as questionnaires and results, and continuous checks link an Azure configuration to a named control. The captured pages do not show measure tracking with delegation and escalation, audit findings with corrective actions, or the statement of applicability generated live from control status. 4 2 10 9
The GRC Consultant
Controls live with their evidence ('Controls & Nachweise — einmal erfüllt, in jedem Framework genutzt'), the SoA and measures are continuously maintained in the same place, tasks carry responsibilities and recurring deadlines, and continuous monitoring binds an Azure configuration check to control A.8.9 automatically — that is a control fabric, not a checklist. We found no public information on the SoA being generated from live control status, on delegation and escalation in measure tracking, or on internal-audit findings with corrective actions; internal audit is offered as an expert service rather than documented as a workflow. 4 2 10 9
The Drafted IT Officer
Controls, evidence, measures and the statement of applicability sit in one place and are kept current, with tasks on recurring deadlines and monitoring evidence wired straight to a control like A.8.9 — that is more than a checklist. Internal audit and the management review are offered, but the pages describe the fixed expert taking those over rather than a workflow I run myself, and I found no public information on delegation and escalation in measure tracking. Solid mid-field, with a service-shaped ceiling. 4 2 9 10
The Lead Auditor
Controls, measures and the statement of applicability are run in one continuously maintained system, controls are reused across frameworks, and evidence is linked to individual controls — an Azure check tied to control A.8.9 is documented, alongside automatic control checks. We found no public information on delegation and escalation in measure tracking, corrective actions on audit findings, or versioned catalogue updates, so I place this between an operable control side and a living one. 2 4 10 9
The Evidence Integrator
Assets, risks, measures and the statement of applicability live in one place and are kept current, controls are mapped and reused across every framework, and a continuous monitoring example shows an Azure configuration check filed as evidence against control A.8.9 — evidence attached to a control straight from the live estate is exactly what makes the control side operable. We found no public information on measure escalation, versioned catalogue updates, or corrective-action workflows, which holds this short of the deeper tiers. 4 10 1 2
The Skeptic
Controls, measures, evidence and the statement of applicability are maintained in one place with cross-framework reuse, evidence linked per control, and revision-safe, versioned documentation; the navigator tracks responsibilities and outstanding evidence. Internal audit and management review are, however, presented as services the vendor's expert performs ("Internes Audit und Management-Review übernehmen wir"), and we found no public information on delegation and escalation in measure tracking or on audit findings and corrective actions as software workflows. 4 2 9 1
Framework & standard coverage
Show reasoningHide 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.
The CISO
Fourteen named regimes including NIS2, TISAX, DORA, SOC 2, ISO 9001 and the German VdS standards, one control satisfying many frameworks through cross-mapping on a shared data basis, custom frameworks supported, and new regimes added when regulation moves (EU AI Act and ISO 9001 in 2025). We found no public information on a documented update cadence when a standard changes. 5 2 4 5
The GRC Consultant
A list of fourteen regimes is published — ISO 27001, NIS2, TISAX, DORA, NISG, SOC 2, ISO 9001, EU AI Act, DSGVO and more — with controls explicitly mapped once across all frameworks, TISAX, DORA and SOC 2 running on the same ISMS, and all modules on one shared data basis, which is exactly the reuse model I build for. New frameworks shipped on a visible timeline (NIS2 in 2023, AI Act and ISO 9001 in 2025); industry coverage is presented as expert knowledge across many sectors rather than per-industry product profiles, and we found no published commitment on updating content when a standard changes. 5 2 1
The Drafted IT Officer
Fourteen named regimes — ISO 27001, NIS2, TISAX, DORA, SOC 2, the EU AI Act and more — on one shared data base, with controls mapped across all of them so a control done once counts everywhere, and new frameworks added as they arrive, such as the EU AI Act and ISO 9001 in 2025. That is exactly the multi-compliance promise a half-time security officer needs, and custom frameworks and own requirements can be added alongside. 5 1 2 5
The Lead Auditor
Fourteen named regimes including NIS2, TISAX, DORA, SOC 2, VdS 10000/10100 and the EU AI Act on a single shared data basis, with documented cross-framework control mapping and dated launches as coverage moves (NIS2 in 2023, EU AI Act and ISO 9001 in 2025). That is broad, current coverage with published updates; the dozens-of-regimes scale and per-industry framework profiles are not documented — industry breadth is presented as expertise rather than framework profiles. 5 1 2 5 4
The Evidence Integrator
Fourteen regimes are named — ISO 27001, NIS2, TISAX, DORA, SOC 2, ISO 9001, the EU AI Act, VdS and more — on one management system with one shared data basis, controls reused across frameworks (SOC 2 on ISO 27001 controls, TISAX on the same ISMS), and two new frameworks launched in 2025. That is broad current coverage with a documented cross-mapping and visible movement; we found no public information on per-industry framework profiles or a fixed update cadence. 5 2 5 4
The Skeptic
Fourteen regimes are named — ISO 27001, NIS2, TISAX, DORA, SOC 2, ISO 9001, EU AI Act among them — with one control mapped across frameworks ("Controls werden über alle Frameworks hinweg gemappt"), custom requirements on the same shared data basis, and a record of adding regimes as they arrive (NIS2 in 2023, EU AI Act and ISO 9001 in 2025). Not the top level: per-industry profiles are not documented, and the update behaviour is inferred from launches rather than a published process for standard changes. 5 1 9 2
Audit readiness & evidence
Show reasoningHide 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.
The CISO
Revision-safe documentation is claimed repeatedly, records are central, linked and versioned, evidence is attached per control, internal audit and management review are taken over as services, and document packages plus a public Trust Center exist. We found no public information on auditor evidence packs generated on demand, read-only auditor access, or management report generators at a click. 1 3 4 9
The GRC Consultant
Documentation is claimed revision-safe and versioned centrally in the platform, all measures are declared provable for auditors, authorities and customers, a public Trust Center carries document packages, and security-questionnaire answers are said to already sit in the ISMS. The Azure check linked to A.8.9 shows evidence collected continuously rather than staged before an audit; we found no public information on read-only auditor access, on-demand audit evidence packs, management report generators, or reproducing any record as it stood on a given date. 9 2 10 1
The Drafted IT Officer
Everything revision-safe and versioned in one place, evidence linked per control, document packages plus a public Trust Center, and a dashboard showing progress per framework — that carries a real audit conversation. But the pages describe my dedicated expert preparing everyone and reporting regularly to management, not reports I generate at a click, and I found no public information on read-only auditor access or on reproducing a record as it stood on a given date. Good bones; the audit story still runs through the person, not the tool. 1 2 4 3
The Lead Auditor
Revision-safe, central, linked and versioned documentation is stated on several pages, document packages and a public trust center are documented, and a 100% audit success rate is claimed with the expert reachable during the audit. As a certifier I need more than the word revisionssicher: we found no public information on read-only auditor access, management reports at a click, or reproducing any record as it stood on a given date — the answer to "show me the state on date X" rests on wording, not a documented capability. 1 2 3 9 4
The Evidence Integrator
Documentation is described as revision-safe, linked and versioned centrally, measures are evidenced for auditors, authorities and customers, document packages and a public Trust Center exist, and a dashboard shows progress per framework. We found no public information on read-only auditor access, on-demand evidence packs per framework, or reproducing a record as it stood on a given date. 1 3 4 9
The Skeptic
Documentation is described as revision-safe, central, linked and versioned, evidence attaches to controls — continuous monitoring links an Azure configuration check to control A.8.9 — and a public Trust Center with document packages is offered. 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; the "100% Erfolg bei Zertifizierungsaudits" claims state past outcomes of expert-led projects rather than a documented readiness feature of the system. 9 10 1 8
Integrations & automation
Show reasoningHide 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.
The CISO
A documented REST API, more than sixty integrations across cloud, identity, DevOps, HR and observability including Jira, Okta, GitHub, AWS and Azure, automated control checks whose evidence flows into the ISMS, register import by file, and an MCP server for AI tools. We found no public information on single sign-on with SCIM provisioning, webhooks, or human review steps on the automated checks. 4 10 8 10
The GRC Consultant
More than sixty integrations with named connectors across cloud (AWS, Azure, GCP), identity and DevOps (Okta, GitHub, GitLab, Jira), HR (Personio, Workday, Datev) and knowledge tools (Confluence, Slack), a REST API, an MCP server into AI tools, automatic flow of employee and monitoring data, file-based register import and recurring tasks with automated notifications. Continuous control checks that bind evidence to controls are real automation of the estate; we found no public information on webhooks, single sign-on with SCIM provisioning, or endpoint and CMDB sources, and no documented human-review step on the automated checks. 10 4 8
The Drafted IT Officer
Sixty-plus connectors across HR, cloud, identity and ticketing — Okta, Jira, GitHub, AWS, Azure among them — plus a REST API, file import for the asset, risk and vendor registers, and continuous control checks that pull Azure configuration and link it to a control automatically. Employees and monitoring data flow in without re-typing, which is what I want next to my day job. I found no public information on webhooks or on single sign-on with automated user provisioning, which keeps it a notch below the top. 10 4 4
The Lead Auditor
More than sixty named integrations across HR, cloud, DevOps and identity (Personio, AWS, GitHub, Okta, Jira), a REST API for pulling platform data into your own systems, an MCP server into AI tools, and automatic control checks that feed evidence. We found no public information on webhooks, single sign-on with SCIM provisioning, or automated evidence tests with documented human review. 10 4 10 8
The Evidence Integrator
Over sixty named integrations span cloud (AWS, Azure, GCP), identity and DevOps (Okta, GitHub, GitLab), ticketing (Jira) and HR (Personio, Workday, Datev), a REST API and an MCP server are stated, employee and monitoring data flow in automatically, and continuous control checks file evidence — the Azure check linked to control A.8.9 is live-estate behaviour, not retyping. We found no public information on the API's object coverage, webhooks, or SCIM provisioning, which holds this below the full automation tier. 10 4 8 10
The Skeptic
Sixty-plus integrations are claimed with a named set across cloud, DevOps, identity, HR and knowledge tools, a REST API and an MCP server are stated, file import covers assets, risks and vendors, and automated control checks link evidence to controls — the automation is real. Two cautions: the integration directory itself offers a coming-soon filter without saying how many of the listed tools are live, and we found no public information on single sign-on, SCIM provisioning or webhooks. 10 4 8
European sovereignty
panel opinion
Show reasoningHide 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.
The CISO
A German contracting entity with development, hosting and support in Germany as the stated default, and an EU investor behind the company. The hosting statement is homepage marketing that a data processing agreement or platform subprocessor list does not corroborate, and the privacy policy discloses that the vendor's own website runs on a US host with US-based web analytics. 6 1 7 2
The GRC Consultant
The contracting entity is secjur GmbH in Hamburg with a German register entry, development, hosting and support are claimed entirely in Germany, and GDPR conformity is asserted throughout, with offices in Hamburg, Bern and Lisbon and a Swiss affiliate. The chain is not publicly closed: we found no published data processing agreement, TOMs or platform subprocessor list and no named data centres; the privacy policy names Google and HubSpot for the vendor's own website and CRM operations and discloses that the site itself is hosted by Webflow in the USA, so where platform customer data lives rests on the 'Hosted in Germany' marketing claim. 6 1 7 9
The Drafted IT Officer
A German company in Hamburg, with hosted-in-Germany claims on several pages and development, hosting and support stated as fully in Germany; the privacy policy also names processors, some American like Google and HubSpot, though those serve the vendor's own website and CRM rather than the platform. I found no public information on a data processing agreement for the platform itself, on named data centres, or on corroboration of the platform hosting claim beyond the marketing statement. Workable for my risk appetite, but I would want the data processing agreement in hand before signing. 6 1 7 2
The Lead Auditor
The contracting entity is secjur GmbH in Hamburg with register court Hamburg and HRB 170383, and development, hosting and support are stated as fully in Germany on several pages. The privacy policy names processors for the vendor's own tooling (Personio and sevDesk in Germany, Google Analytics and HubSpot), but the platform hosting statement is marketing copy not corroborated by a platform subprocessor list or a published data processing agreement; we found no public information on other hosting options or a transfer impact assessment. 6 1 9 7 2
The Evidence Integrator
A German GmbH in Hamburg claims development, hosting and support fully in Germany, and the privacy policy names German processors (Personio, sevDesk) for recruiting and invoicing. The Germany-hosting statement is marketing copy not corroborated by a platform data processing agreement or platform subprocessor list, and the privacy policy discloses US-based processors on the website side (Google Analytics; secjur.com hosted by Webflow in the USA), so the chain is only partially proven. 6 7 1 2
The Skeptic
A German GmbH in Hamburg with "Hosted in Germany" stated as the default and European investors and offices — but the "Made & Hosted in Germany" statement appears as homepage copy, and the privacy policy's processor disclosures concern the vendor's own website and operations, including Webflow in the USA for the site itself plus Google and HubSpot. We found no public information on a published data processing agreement, a subprocessor list for the platform's customer data, or named data centres behind the hosting claim. 6 1 7 2
Pricing transparency
Show reasoningHide 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.
The CISO
The model is public — plannable package prices, unlimited consulting at a fixed price, all costs known at project start, no day-rate billing — but no figures appear for any edition or package, so a buyer cannot compute an invoice from public pages alone. 1 4 9
The GRC Consultant
The captured pages describe a fixed-price package model — 'Transparenter Festpreis, alle Kosten sind zum Projektstart bekannt', planbare Paketpreise, unlimited consulting at a fixed price, up to 67% cheaper than hourly consultants — but we found no public price figures: no priced edition (a 'SECJUR Standard' package is named without an amount), no user or entity rates, no billing period, setup fee or VAT treatment. The market norm is unpublished pricing and this matches it: the real invoice remains a sales conversation. 1 9 4 2
The Drafted IT Officer
The pricing model is public and unusually clear in words: planable package prices, all costs known at project start, no daily-rate billing, and unlimited consulting at a fixed price. But the captured pages show no price figures at all — no from-price, no priced edition — so I cannot compute an invoice without a sales conversation. Transparent shape, opaque number. 1 2 9 4
The Lead Auditor
The pricing model is public — fixed package prices with all costs known at project start, unlimited consulting at a fixed price, and no daily rates — but we found no euro amount, edition price or scale step anywhere we read, only percentage savings claims. A buyer cannot compute the invoice from the public pages; this sits below even a single published from-price. 1 9 4 8
The Evidence Integrator
No price figure appears anywhere captured — not a euro amount, edition price or per-user rate — while fixed package prices, all costs known at project start, unlimited consulting at a fixed price and savings of up to sixty-seven percent versus hourly consultants are promised. The billing model is public; the invoice is not computable from these pages. 1 9 4
The Skeptic
Not one euro figure appears on any captured page: the buyer gets "Festpreis", "Planbare Paketpreise", "Unlimitierte Beratung zum Festpreis" and one package name (SECJUR Standard) without a price, so the invoice is not computable from public pages. The captured pages give different savings figures — "50% günstiger" and "bis zu 67% günstiger" than consultants — and software and expert service are sold as one bundle in which the vendor's expert does 80% of the work. 1 8 4 2
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE | 2/2 pts | 6 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The statement is homepage marketing copy, and the privacy policy discloses that secjur.com itself is hosted by Webflow, Inc. in the USA, so where the platform's customer data is stored is not corroborated by a subprocessor list or DPA excerpt. |
4/4 pts | 1 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 SECJUR Digital Compliance Office (ISMS)
Is SECJUR Digital Compliance Office (ISMS) European?
Yes. whats-best.ai classifies SECJUR Digital Compliance Office (ISMS) as EU-Made. Its vendor, secjur GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does SECJUR Digital Compliance Office (ISMS) store data?
SECJUR Digital Compliance Office (ISMS) 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 19 Oct 2026.
Does SECJUR Digital Compliance Office (ISMS) have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to SECJUR Digital Compliance Office (ISMS)?
As of 18 Nov 2026, the panel rates preeco | informationssicherheit (3.5/5), 6clicks (3.5/5) and Secfix (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 preeco | informationssicherheit (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: SECJUR Digital Compliance Office (ISMS) alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 24 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The statement is homepage marketing copy, and the privacy policy discloses that secjur.com itself is hosted by Webflow, Inc. in the USA, so where the platform's customer data is stored is not corroborated by a subprocessor list or DPA excerpt.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 31 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- We read 10 of the 16 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 2 ISMS product page www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 3 ISO 27001 product page www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 4 Platform page www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 5 About page www.secjur.com Checked 16 Nov 2026 +2 earlier captures: 19 Oct 2026, 24 Aug 2026 Details →
- 6 Imprint www.secjur.com Checked 16 Nov 2026 Details →
- 7 Privacy policy www.secjur.com Checked 16 Nov 2026 Details →
- 8 Framework & standard coverage — found from sitemap www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 9 Framework & standard coverage — found from sitemap www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 10 Integrations & automation — found from sitemap www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →