Hyperproof
Provenance unknown 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 Hyperproof Inc. · hyperproof.io
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.
Hyperproof at a glance
- Vendor
- Hyperproof Inc.
- Headquarters
- Not stated on the vendor’s pages as of 26 Oct 2026
- Data hosting
- Outside the EU by default source, captured 26 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 26 Oct 2026
- Panel verdict
- The AI panel rates Hyperproof 3/5, the mean of 6 judges. Hyperproof, a US-based compliance operations platform, scores highest on framework coverage and controls and statement-of-applicability work. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 26 Oct 2026; evaluated by the panel 27 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Hyperproof, a US-based compliance operations platform, scores highest on framework coverage and controls and statement-of-applicability work. The judges credit a library naming NIS2, TISAX, DORA, BSI C5 with its 2026 edition, the EU AI Act and ISO 27001:2022; overlap identification so one control and its evidence serve many frameworks; a statement of applicability generated from the live control status field; evidence pulled daily with source, timestamp and setup-user metadata; and 200-plus integrations across twenty categories plus an SDK for custom connectors. Weakest is sovereignty: the pages state a US entity and hosting in the United States, the application-and-storage subprocessor Amazon Web Services lists the USA as its only territory, and we found no public information on an EU hosting region. Information security management holds at 4: a real risk register is documented, but we found no public information on asset inventory, a named risk methodology or incident workflows with reporting deadlines. Scores sit close together — the widest spread across criteria is 7-9 on integrations and automation — and no public prices appear on the captured pages.
Speaks for it
- Framework coverage scored 8-9, with NIS2, TISAX, DORA, BSI C5 (2026 edition listed), the EU AI Act, ISO 27001:2022 and SOC 2 among dozens of named regimes
- Overlapping requirements are identified so one control and its evidence satisfy many frameworks — proof collected once and applied across audits
- The statement of applicability is generated from the live control status field, with custom fields, grid and tree views and exportable not-applicable justifications
- Evidence arrives daily or on a chosen cadence carrying source-system, timestamp and setup-user metadata, and auditors can be invited into a workspace with selective document sharing
- Two hundred plus integrations across twenty categories come with a Hypersync SDK, a developer portal and a test builder whose Excel-like syntax needs no engineering support
Held against it
- Sovereignty scored 1-2 — US hosting stated in the privacy policy, the application-and-storage subprocessor Amazon Web Services lists the USA as its only territory, and we found no public information on an EU hosting region for the platform
- Information security management scored 4 — a real risk register is documented, but we found no public information on asset inventory, a named risk methodology, protection-need inheritance or incident workflows with reporting deadlines
- We found no public information on internal audit workflows with findings and corrective actions, or on reproducing any record exactly as it stood on a given date
- The captured pages give different figures for library size — 160-plus pre-built frameworks on the homepage and 12 common frameworks on another page — and we found no public information on a documented update cadence when a standard changes
- The documented programmatic surface is a Hypersync SDK and developer portal — we found no public information on webhooks, SCIM provisioning or a documented REST interface for core objects
Best for
- You run several regimes at once — SOC 2 or ISO 27001 alongside NIS2, TISAX, DORA or BSI C5 — and want one control set with evidence collected once and reused across audits
- Your security function is small and needs continuous control testing without engineering support, using tests written in Excel-like syntax
- You must show auditors where each piece of evidence came from — items carry source, timestamp and setup-user metadata and are shared selectively from a controlled workspace
- Your evidence lives in Jira, Slack, Microsoft Teams, AWS, Azure, HRIS or vulnerability scanners and you want it pulled live on a cadence or on demand
Avoid if
- You need EU-resident hosting or a European contracting entity for your compliance data — the captured pages state a US entity with US hosting, and Amazon Web Services lists the USA as its only territory for application and storage
- Your risk register and its evidence must not sit under US law — the privacy policy states information is governed by U.S. law and names Hyperproof, Inc. as controller for EEA individuals
- You need to reduce seats or exit during the term — the terms set a one-year default initial term with non-cancellable, non-refundable fees and quantities that cannot be decreased mid-term
The scores
| Criterion | Panel median |
|---|---|
| Asset & risk management depth | 2 of 5 |
| Controls, SoA & measures | 3.5 of 5 |
| Framework & standard coverage | 4.5 of 5 |
| Audit readiness & evidence | 3.5 of 5 |
| Integrations & automation | 4 of 5 |
| European sovereignty | 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
The risk work is real: assessments are recorded and linked to controls, owners and evidence, remediation tasks carry due dates and real-time tracking, and third-party risk feeds the same register. But we found no public information on asset inventory, a documented risk methodology, inheritance of protection needs across assets, or incident workflows with the 24-hour and 72-hour reporting clocks — the risk treatment discussion sits in a statement-of-applicability FAQ. 5 6 8
The GRC Consultant
The risk module is genuinely operable — assessments recorded and linked to specific controls, owners and evidence, remediation tasks with due dates tracked in real time, third-party risk in the same platform, and risk treatment discussed in the statement-of-applicability guidance. But we found no public information on an asset inventory, a configurable risk matrix, protection-needs inheritance across asset relations, or an incident register with the NIS2 24-hour/72-hour reporting clocks, so the ISMS core is only half covered on the evidence I can see. 5 6 8
The Drafted IT Officer
The risk module is real — risk assessments recorded and linked to controls, owners and evidence, with remediation tasks, due dates and a risk treatment plan referenced in the FAQ — but I found no public information on an asset inventory, a named risk methodology, protection-need inheritance across assets, or an incident register with reporting deadlines. For a one-person security function that covers the register side but not the asset chain a certifier would ask me about. 5 6 8 11
The Lead Auditor
Risk work is real and documented: assessments recorded and linked to controls, owners and evidence, remediation tasks with due dates tracked in real time, plus vendor-risk and policy modules. But we found no public information on asset inventory, a documented risk methodology such as ISO 27005 or BSI 200-3, inheritance of protection needs across assets, or security incident handling with reporting deadlines — the incident side I would need for NIS2-style operations is invisible to me here. 5 6
The Evidence Integrator
Risk work is documented as a genuine register: assessments recorded and linked to controls, owners and evidence, with remediation tasks, due dates and real-time progress, and treatment addressed beside the statement of applicability. We found no public information on an asset inventory, a configurable risk matrix, a documented methodology, protection-need inheritance, or any incident register with reporting deadlines — without the estate feeding it, the risk view is only as current as what someone typed. 5 6 8
The Skeptic
The risk-management pages document a real register — risk assessments recorded and linked to controls, owners and evidence, with remediation tasks, due dates, real-time tracking and integration into enterprise risk management — which is more than a bare list. But we found no public information on an asset inventory, a configurable risk matrix with likelihood and impact, a named risk methodology, protection-need inheritance, or incident workflows with NIS2-style reporting deadlines, so the deeper ISMS chain rests on nothing I can see. 5 6 8
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
The statement of applicability is built from the live control status field with custom fields and not-applicable justifications exported on demand, controls link to risks with owners and reminders, test failures trigger configurable notification and escalation, and evidence attaches to each control through automated collection. We found no public information on internal audit workflows with findings and corrective actions, or on versioned catalogue updates, which keeps this below the top band. 7 8 11 14 1
The GRC Consultant
The statement of applicability draws from the live control status field with custom fields and grid and tree views, controls map across frameworks with owners, and continuous testing runs on a no-engineer Excel-like test builder with configurable failure responses, notification and escalation paths. Evidence sits on each control with source, timestamp and setup-user metadata — that is the living control fabric I want for client twelve. We found no public information on internal-audit findings and corrective-action workflows or recurring audit schedules. 1 7 8 11 12 14
The Drafted IT Officer
Controls come in from a spreadsheet or are built from scratch with owners and criticality, the statement of applicability is generated straight from the Status field and a Grid View filtered by section, and evidence attaches per control. The continuous testing side is genuinely friendly to someone like me — the test builder syntax "will feel familiar if you've used Excel functions" and needs "no engineering support", with failure responses, notifications and escalation configurable per control; I found no public information on internal audit workflows with findings and corrective actions. 1 7 8 11 14
The Lead Auditor
This is the pattern I insist on: a statement of applicability generated from the live control status field, section-filtered exports carrying statuses, mapped controls and not-applicable justifications, sitting on continuous automated testing with configurable failure notification and escalation paths. Evidence attaches per control, refreshed daily with source and timestamp metadata. We found no public information on internal-audit workflows with findings and corrective actions, or on delegation of measure tracking. 7 8 14 14
The Evidence Integrator
The control side is operable and live-fed: controls linked to risks and mapped across frameworks with owners, automated continuous testing, configurable escalation when a test fails, and a statement of applicability built from the status field over Annex A requirements with custom fields. We found no public information on internal audit workflows with findings and corrective actions, or on delegation of measures. 1 7 8 11 14
The Skeptic
The control side is operable rather than a checklist: controls carry owners and map across frameworks, a statement of applicability is built from the live status field with custom fields, and controls are tested continuously with configurable failure escalation and evidence attached via the Hypersync connectors. Customization is documented down to spreadsheet import and self-built tests; we found no public information on internal audit workflows with findings and corrective actions, or on versioned catalogue updates. 1 7 8 14
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
Coverage is a living catalogue: TISAX, NIS2, DORA, BSI C5 and the EU AI Act sit in a claimed 160-plus library alongside ISO 27001:2022 and SOC 2, one control set is reused across frameworks through documented overlap identification, and current standard versions are listed. What the pages do not document is a published update cadence or per-industry framework profiles. 9 1 14 14 10
The GRC Consultant
160+ pre-built frameworks including NIS2, TISAX, DORA, BSI C5 with the 2026 version listed, the EU AI Act and ISO 27001:2022, with overlap identification and AI-assisted mapping so one control and its evidence answer many regimes — exactly the answer-once economics I build around. We found no public information on a documented update cadence when a standard changes, which is what separates a large library from a living framework product. 1 8 14 9 14
The Drafted IT Officer
160+ pre-built frameworks in a browsable library including ISO 27001:2022, TISAX, NIS2, DORA, BSI C5, EU AI Act and current versions such as NIST CSF 2.0 and PCI DSS 4.0.1, and overlapping requirements are identified so one control and its evidence serve multiple regimes — you "collect proof once and apply it across multiple audits". I found no public information on a documented update cadence when a standard moves, or per-industry framework profiles. 1 10 14 9 14
The Lead Auditor
The catalogue lists dozens of named regimes — NIS2, TISAX, DORA, GDPR, BSI C5 including its 2026 edition, several ISO 27001 versions — though the captured pages give different figures for library size, one claiming 160-plus pre-built frameworks and a resource page naming 12 common ones. Documented overlap identification lets one control with its evidence satisfy many frameworks, collected once and reused across audits. We found no public information on a published cadence for updating frameworks when a standard moves. 1 10 14 9
The Evidence Integrator
Dozens of regimes are individually named — NIS2, TISAX, DORA, BSI C5, the EU AI Act, ISO 42001 among them — with the captured pages giving different figures for library size (12 common frameworks in one guide, a claim of 160-plus pre-built frameworks on the homepage), and overlapping requirements identified so one control and its evidence serve many frameworks on one data basis. We found no public information on a documented update cadence when a standard moves. 1 10 9 14
The Skeptic
Coverage is broad and current — NIS2, TISAX, DORA, BSI C5, ISO 27001 in three versions, SOC 2, EU AI Act — with a documented mechanism that identifies overlapping requirements so one control and its evidence satisfy many frameworks, and 2026 editions of C5 and SCF already listed. The 'largest framework library on the market' claim sits beside different figures for library size across the captured pages — 160-plus pre-built frameworks on the homepage claim and a count of 12 common frameworks on the framework-library page — and we found no public information on a documented update cadence when a standard moves. 1 9 10 9 14
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
Collected evidence carries source system, timestamp and the user who set it up, changes to settings and access levels are recorded over time, auditors are invited into a controlled module with selective document sharing, and statement-of-applicability and program data export on demand. We found no public information on record-level revision safety, explicitly read-only auditor access, or reproducing any record as it stood on a given date. 7 12 12 14 8 11 11
The GRC Consultant
Auditors can be invited in with only chosen documents shared, every piece of evidence carries source, timestamp and setup-user metadata so auditors can trust it was not hand-modified, and exports plus dashboards cover the requirements and mapped-controls report and the executive view. We found no public information on revision-safe version history of the platform's own records, on read-only auditor access, or on reproducing any record as it stood on a given date. 7 8 11 11 12 14
The Drafted IT Officer
Evidence is pulled in daily with metadata — source system, timestamp, the user who set it up — so the trail "hasn't been modified by human operators", change records show when encryption, password or access settings shifted over time, auditors can be invited into a workspace sharing only chosen documents, and programs export to CSV with statuses and mapped controls. I found no public information on read-only auditor access or on reproducing any record exactly as it stood on a given date. 7 8 14 12 14
The Lead Auditor
The evidence chain is the strongest part: collection from named sources on a cadence or on demand, metadata with source system, timestamp and the user who set it up — which the vendor says lets auditors trust it has not been modified by human operators — plus a timestamped paper trail from SIEM and logging connections and an auditor workspace with selective document sharing. The change records documented cover monitored system settings over time; we found no public information on revision-safe history of the compliance records themselves, or on reproducing any record as it stood on a given date — the question I always put to a vendor. 7 8 12 14
The Evidence Integrator
Evidence arrives machine-made: fresh data pulled daily from live sources carrying metadata — source system, timestamp, who set it up — change records showing what moved and when, auditors invited into a controlled workspace with only chosen documents shared, and dashboards and reports for executives. We found no public information on auditor access being read-only, or on reproducing any record exactly as it stood on a given date. 7 8 14 12 14
The Skeptic
Evidence arrives with source-system, timestamp and setting-user metadata and daily refresh, change records are retained over time, auditors can be invited into a workspace with selective document sharing, and CSV exports plus dashboards and AI-generated reports cover auditors and management. I stop short of the top because we found no public information on evidence packs generated on demand or a record reproduced as it stood on a given date — and the auditor portal is described as selective sharing, not stated as read-only access. 8 11 14 12 14
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
The platform feeds from the real estate: two-hundred-plus connectors across twenty categories including identity, endpoint management, vulnerability scanning and ticketing, an SDK for building custom connectors, evidence pulled daily or on a chosen cadence, and automated control tests with configurable failure notification and escalation. We found no public information on a REST API over the core data model, webhooks, or SCIM provisioning. 13 12 1 14 7 2
The GRC Consultant
Hypersyncs pull live data from identity providers, endpoint platforms, vulnerability scanners and cloud sources on a cadence or on demand, 200+ integrations across 20 categories, Jira/Slack/Teams for workflow, a public SDK with a developer portal for custom connectors, and automatic test recommendations feeding continuous control monitoring. We found no public information on webhooks or SCIM provisioning, so it sits just under infrastructure-grade. 1 7 13 14 11 14
The Drafted IT Officer
Two hundred plus integrations across twenty categories — Jira, ticketing, HRIS, device management, vulnerability scanners, AWS and Azure — with Hypersyncs pulling live data on a cadence or on demand and automatic test recommendations from the collected data, plus an SDK and developer portal for custom connectors. That is the automation a shop without a security team lives on; I found no public information on webhooks, SCIM provisioning or a documented REST API for the core objects. 1 7 13 14 12
The Lead Auditor
Hypersyncs pull live data from identity providers, endpoint management, vulnerability scanners and cloud platforms on demand or on a preferred cadence and feed automated control tests, Livesyncs gather continuously from cloud storage, and an SDK with developer documentation supports custom connectors; one page claims 200-plus integrations across 20 categories with Jira named among them. Automated evidence collection with daily refresh is fully documented. We found no public information on webhooks or single sign-on with SCIM provisioning. 1 7 13 14
The Evidence Integrator
This is the closest thing to infrastructure the pages describe: 200-plus integrations across twenty categories including identity providers, endpoint management, vulnerability scanners and ticketing; Hypersyncs pulling live data on a cadence or on demand, Livesyncs gathering continuously, a no-engineer test builder, and an SDK with a Developer Portal for custom connectors. The plumbing I check first is thinner on paper — we found no public information on a documented REST API for core objects, webhooks, or SCIM provisioning. 2 7 13 11 12
The Skeptic
Two hundred-plus integrations across twenty named categories — Jira, Slack, Teams, AWS, Azure, HRIS, device management, vulnerability scanners — with an SDK for custom connectors, a developer portal and documentation site, and automated evidence tests with recommendations and configurable failure paths, with professional services separately disclosed for custom integration builds. We found no public information on webhooks or SCIM provisioning, and the programmatic surface is evidenced as an SDK and developer portal rather than a documented REST interface for core objects. 1 7 13 14 11
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
The captured pages prove a US entity operating under US law with US-based hosting — the application and storage subprocessor lists the USA as its only territory, and no page we captured offers an EU hosting region for the platform. GDPR-facing commitments and a published subprocessor list soften the edges, but a European operator's entire risk register would sit under US jurisdiction here. 3 4
The GRC Consultant
The captured pages state a US entity under US law using US-based hosting providers, and the subprocessor list shows the primary application-and-storage processor's only territory as the USA; we found no public information on an EU hosting option for the platform. GDPR processor commitments, breach-reporting undertakings and a published subprocessor list exist, but a European client's risk register would live under US jurisdiction — for me that decides the criterion. 3 4
The Drafted IT Officer
Hyperproof, Inc. is a US company stating "we are based in the United States", uses US hosting providers, and the published subprocessor list shows the platform's Application & Storage processor, Amazon Web Services, with the USA as its only territory; I found no public information on an EU hosting option for the platform itself. GDPR-facing commitments do exist — breach reporting, EEA legal bases, a processor role and DPAs with service providers — but my risk register and its evidence would sit under US law with several US-only processors in the chain. 3 4 11
The Lead Auditor
The captured pages prove a United States entity stating it is based in the United States, governed by US law and hosted by providers in the United States, with the application and storage subprocessor listing USA as its only territory, and we found no public information offering an EU hosting region for the platform. GDPR engagement is documented — processor role for customer data, EEA legal bases, a breach-reporting commitment — and a subprocessor list is published, but on this evidence the risk register itself sits under US jurisdiction. 3 4
The Evidence Integrator
The captured pages prove a US contracting entity and US hosting — "data hosting service providers in the United States" — with the primary application and storage processor Amazon Web Services listing USA as its only territory, under stated US law, and no captured page offers an EU hosting region for the platform. A published subprocessor list and GDPR-facing commitments show some transparency, but we found no public information on a customer-facing data processing agreement. 2 3 4
The Skeptic
What is proven is American end to end: Hyperproof, Inc. of Washington State is the controller for EEA individuals under U.S. law, the privacy policy states hosting in the United States, and the primary application-and-storage subprocessor Amazon Web Services lists the USA as its only territory, with no excerpt offering an EU hosting region for the platform. A subprocessor list and GDPR commitments are published, and some processors such as Microsoft Azure and Auth0 show EU territories, but we found no public information on a customer-facing data processing agreement or any EU hosting option. 2 3 4
Pricing transparency
not rated — the vendor publishes no price
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 captured pages show no public price: subscription scope is tied to programs and modules per individual order, the published terms cover only currency, term length, renewal mechanics and refund conditions, and every engagement starts with a demo request. A buyer cannot compute an invoice from public information. 2 12 12
The GRC Consultant
We found no public information on prices for any edition or module — scope is configured per order across programs and modules, and the entry point is a demo sign-up. The public commercial mechanics are unusually clear though: a one-year term in US dollars, 30-day notice before renewal to cancel, 45-day notice of fee increases, and non-refundable fees with a pro-rata refund if the customer terminates for the vendor's material breach. 2 12
The Drafted IT Officer
I found no public prices at all — the documented route in is a personal demo — and the terms state that access rights are tied to programs and modules as specified in each order. The published terms do state the commercial mechanics plainly, which helps: fees in US dollars, a one-year initial term, fees non-cancellable and non-refundable, no mid-term seat decreases, 30 days' cancellation notice before renewal and 45 days' notice of fee increases. 2 12 12
The Lead Auditor
No public prices appear anywhere in the captured pages; the commercial facts are contractual mechanics only — fees denominated in US Dollars, a one-year initial term, 45 days' notice of fee increases, non-refundable and non-cancellable fees, quantities not reducible mid-term. The stated route to a figure is a personal demo, so every invoice is a sales conversation. 2 12
The Evidence Integrator
No price appears anywhere captured: the terms set the mechanics — annual initial term, fees in US dollars, 45 days' notice of fee increases, non-refundable and non-cancellable — while access is tied to programs and modules per order, and the route in is a personal demo. We found no public prices for any edition or module. 2 12
The Skeptic
We found no public information on prices — editions, modules, per-seat figures or a 'from' price — and the documented path to any figure is a demo sign-up. The terms of use do publish the commercial mechanics: a one-year default term, fees in U.S. Dollars, quantities not reducible mid-term, 30-day cancellation notice, 45-day notice of fee increases, and non-refundable fees with pro-rata refund only on termination for material breach. 2 12
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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?The statement covers "the information we collect" broadly and the subprocessor list shows several processors also operating in EU/Germany environments, so it is a US default rather than a precise statement that all customer platform data stays in the USA. |
0/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source |
Proprietary
unverified
Why unverified?"Proprietary" appears as a descriptor in the Terms of Use; no specific licence is named for the platform. |
0/1 pts | 2 Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Hyperproof
Is Hyperproof European?
Not determined: the vendor’s pages as captured do not say where Hyperproof is based.
Where does Hyperproof store data?
Hyperproof stores customer data outside the EU by default, per the vendor’s page captured 26 Oct 2026.
Does Hyperproof have a free plan?
Not stated on the vendor’s pages as of 26 Oct 2026.
What are the best alternatives to Hyperproof?
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: Hyperproof alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Open source. "Proprietary" appears as a descriptor in the Terms of Use; no specific licence is named for the platform.
- Weak sourcing — Hosting location. The statement covers "the information we collect" broadly and the subprocessor list shows several processors also operating in EU/Germany environments, so it is a US default rather than a precise statement that all customer platform data stays in the USA.
- 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
- 1 data 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
- 1 subprocessors 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 support 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page hyperproof.io Checked 26 Oct 2026 Details →
- 2 Terms of service — found from the homepage hyperproof.io Checked 26 Oct 2026 Details →
- 3 Privacy policy — found from the homepage hyperproof.io Checked 26 Oct 2026 Details →
- 4 Subprocessor list — found from the homepage hyperproof.io Checked 26 Oct 2026 Details →
- 5 Asset & risk management depth — found from sitemap hyperproof.io Checked 26 Oct 2026 Details →
- 6 Asset & risk management depth — found from sitemap hyperproof.io Checked 26 Oct 2026 Details →
- 7 Controls, SoA & measures — found from sitemap hyperproof.io Checked 26 Oct 2026 Details →
- 8 Controls, SoA & measures — found from sitemap hyperproof.io Checked 26 Oct 2026 Details →
- 9 Framework & standard coverage — found from sitemap hyperproof.io Checked 26 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 10 Framework & standard coverage — found from sitemap hyperproof.io Checked 26 Oct 2026 Details →
- 11 Audit readiness & evidence — found from sitemap hyperproof.io Checked 26 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 12 Audit readiness & evidence — found from sitemap hyperproof.io Checked 26 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
- 13 Integrations & automation — found from sitemap hyperproof.io Checked 26 Oct 2026 Details →
- 14 Integrations & automation — found from sitemap hyperproof.io Checked 26 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →