Thoropass
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Thoropass (formerly Laika), Inc. · thoropass.com
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.
Thoropass at a glance
- Vendor
- Thoropass (formerly Laika), Inc.
- Headquarters
- Not stated on the vendor’s pages as of 1 Oct 2026
- Data hosting
- Outside the EU by default source, captured 30 Sep 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Oct 2026
- Panel verdict
- The AI panel rates Thoropass 2.5/5, the mean of 6 judges. Thoropass (formerly Laika) pairs an audit lifecycle platform with its in-house CPA firm, Laika Compliance, LLC dba Thoropass Assurance. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 1 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
Thoropass (formerly Laika) pairs an audit lifecycle platform with its in-house CPA firm, Laika Compliance, LLC dba Thoropass Assurance. Strongest categories are framework coverage, audit readiness and integrations and automation, at 6-7: nine frameworks from SOC 1 to NIST CSF 2.0 are answered once through a unified control mapping, evidence is pulled daily from AWS, GCP and Azure accounts, Jira Cloud and ServiceNow automations turn ticket populations into evidence, and auditors can fulfill most evidence requests directly. Sovereignty scores sit at 1-2: the captured pages state hosting and personal-data processing in the United States, with AI processing on Google Vertex AI and Azure OpenAI in US data centres, and no public information on an EU hosting option. Information security management runs 2-4 and controls 4-6; the spread reflects how much weight judges gave the live asset and control inventory against an unevidenced risk side, where the only artefact shown is an AI risk assessment template and no public information appears on a generated statement of applicability. No prices appear on the captured pages.
Speaks for it
- Nine frameworks — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — are answered once through a documented unified control mapping.
- Automated evidence collection pulls daily from connected AWS, GCP and Azure accounts, with per-monitor status history, re-run, watch alerts and XLSX export.
- Jira Cloud and ServiceNow automations turn a project-and-tag rule into an evidence collector that surfaces matching tickets at audit time.
- Auditors from the vendor's in-house CPA firm can fulfill most evidence requests directly, and exclusions with compensating controls are visible to the auditor.
- A published DPA provides Standard Contractual Clauses (Modules 2 and 3), Data Privacy Framework certification and a subprocessor list with a 30-day objection window.
Held against it
- We found no public information on a risk register, risk methodology, risk treatment with owners or incident workflows with reporting deadlines — the only risk artefact shown is an AI risk assessment template.
- Custom controls are not connected to a framework, receive no integrations or automations, and can't be considered in-scope for audit.
- Dynamic framework updates were documented for SOC 2, ISO 27001 and HIPAA only as of May 1, 2024, with other frameworks promised soon.
- Export and audit reporting tools, MDM device support and code repositories are listed as coming soon on a published roadmap.
- The captured pages state hosting and processing in the United States and flag subprocessor exposure as US Cloud Act, and we found no public information on an EU hosting option.
Best for
- You need multiple certifications and attestations from a single audit, across frameworks such as SOC 2, SOC 1, HIPAA, HITRUST and PCI DSS.
- Your estate runs on AWS, GCP or Azure and your audit evidence lives in Jira Cloud or ServiceNow ticket populations, so automated collection fits your stack.
- You want the audit performed in-tool by the vendor's in-house CPA firm, whose auditors can fulfill most evidence requests directly.
- You are a first-time compliance owner and want templates and walkthroughs to guide a non-specialist.
Avoid if
- You need EU data residency — the captured pages state hosting and personal-data processing in the United States, and we found no public information on an EU hosting option.
- Your obligations include NIS2, TISAX, DORA or BSI IT-Grundschutz — ask the vendor: the public pages we read do not show it
- You need custom controls inside audit scope — the vendor's help pages state they are not framework-connected and can't be considered in-scope.
- You need to manage risk, not only assets — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Asset & risk management depth | 1 of 5 |
| Controls, SoA & measures | 2 of 5 |
| Framework & standard coverage | 3.5 of 5 |
| Audit readiness & evidence | 3 of 5 |
| Integrations & automation | 3.5 of 5 |
| European sovereignty | 1 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 asset side is real — an Asset Inventory module with automatic discovery from AWS, GCP and Azure accounts and daily metadata pulls — but I find no documented risk register, no risk methodology, no inheritance of protection needs and no incident workflow with reporting deadlines; the nearest artefacts are an AI risk assessment template and pulling incident-ticket populations as audit evidence. For an ISMS backbone that is inventory without the risk chain. 4 5 6 13
The GRC Consultant
The asset side is real: an Asset Inventory module with automatic discovery through connected AWS, GCP and Azure accounts, daily metadata pulls and tag-based scoping. But I found no public information on a risk register, a risk methodology, risk treatment with owners, or an incident register — the ISMS core beyond the asset list is undocumented, and the only risk artefact shown is an AI risk assessment template. 4 5 6
The Drafted IT Officer
The asset side pulls its own weight — cloud accounts across AWS, GCP and Azure are discovered automatically with daily metadata pulls, and the inventory connects to MDM tools and is built to be audit-ready. But I was handed this job to run risk, and I find no risk register, no risk matrix, no documented risk methodology and no incident workflows with reporting deadlines anywhere in the captured pages; the only risk artefact is an AI risk assessment template. 4 5 6
The Lead Auditor
The help centre documents a genuine asset side — an inventory module with automatic discovery from AWS, GCP and Azure and daily metadata pulls — but the risk side reduces to an AI risk assessment template: I found no public information on a risk register with likelihood and impact, a risk methodology, treatment with owners, or incident workflows with reporting deadlines. An ISMS whose risk half is unevidenced is a filing exercise, not an ISMS. 1 4 5 6
The Evidence Integrator
The asset side is genuinely live — cloud assets are discovered automatically from connected AWS, GCP and Azure accounts with daily metadata pulls, and the asset inventory connects to MDM tools — but I found no public information on a risk register, a configurable risk matrix, a documented risk methodology beyond an AI risk assessment template, or incident workflows with reporting deadlines. A strong live asset inventory without the risk chain lands this mid-scale. 4 5 6
The Skeptic
An asset inventory with automatic discovery through connected AWS, GCP and Azure accounts, daily metadata pulls and tag-based scoping is well documented. On the risk side the only artifact we found is an article title for an AI Risk Assessment Template; we found no public information on a risk register with likelihood and impact, a documented risk methodology, risk treatment with owners, or incident workflows with reporting deadlines. 4 5 6 1
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
Unified Controls map one control across frameworks with owners, action items act as measures that update when a framework is added, and monitors give live status with automated evidence attached per control — more than a checklist. I find no public information on a statement of applicability generated from control status or on internal audit workflows with findings and corrective actions, and custom controls sit outside the framework fabric with no automations and no audit scope. 1 6 7 9 11
The GRC Consultant
Unified Controls map overlapping controls across frameworks, with control owners, and automated monitors that flip between Healthy and Violations Found with evidence requests linked to each control — a live status, not a checklist. I found no public information on a generated statement of applicability, internal audit checklists, or any link from controls to risks, and the captured help article states that user-created custom controls are not connected to a framework, cannot benefit from integrations or automations, and can't be considered in-scope for audit. 6 7 8 11
The Drafted IT Officer
Unified Controls map one control across many frameworks, action items act as the measures with named control owners, and templates and walkthroughs exist to guide a non-specialist like me. I find no statement of applicability generated from live control status and no linkage between controls and risks, and user-created custom controls sit outside the framework, the automations and the audit scope — with the create button possibly needing a customer success manager to switch on. 6 7 8 9
The Lead Auditor
Controls are clearly operable rather than a checklist: unified controls mapped across frameworks, control owners, action items, automated evidence attached per control, and a real-time view of control progress. But the statement of applicability generated from live control status — my touchstone — never appears in the captures, nor do internal audit workflows or corrective actions, and the vendor's own help pages state that user-created custom controls can't be considered in-scope for audit and aren't connected to a framework. 1 6 7 8 9 11
The Evidence Integrator
Unified Controls map overlapping controls across frameworks, action items update dynamically when a framework is added, and continuous monitors keep control status live with automated evidence attached — the control side is operable, not a checklist. I found no public information on a generated statement of applicability, internal audit workflows with findings and corrective actions, or delegation and escalation in measure tracking, and custom controls sit outside the framework mapping and the automations entirely. 6 7 8 9 11 12
The Skeptic
Unified Controls mapped across frameworks, named control owners, multi-framework action items and automated evidence tied to controls go beyond a plain checklist, and exclusions are explicitly visible to the auditor. However, custom controls are documented by the vendor as unconnected to any framework and ineligible for audit scope, and we found no public information on a generated statement of applicability, due-date tracking and delegation on measures, or internal audit workflows in the software — the audit itself is sold as a service from the vendor's in-house CPA firm. 6 7 8 11 12
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
The catalogues are long — SOC 1 and SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0, PCI DSS, plus ISO 27001/27002 mappings in the help centre — and the one-control-many-frameworks claim is documented with up to 90% crossover and UPDATED tags when a standard changes. The European regimes I need — NIS2, TISAX, DORA, BSI IT-Grundschutz — appear on none of the captured framework lists, and dynamic updating was live for only SOC 2, ISO 27001 and HIPAA at capture. 1 6 8 9
The GRC Consultant
Nine named regimes — SOC 1 and SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS, plus ISO 27001/27002 mappings — are answered once through a documented unified-control mapping with up to 90% crossover claimed, which is exactly the answer-a-control-once architecture I build for. Dynamic updates when a framework is added and NEW/UPDATED tags on standard changes are documented, though as of the captured May 2024 date only SOC 2, ISO 22 and HIPAA update dynamically; we found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz coverage. 6 8 9
The Drafted IT Officer
A genuinely broad list is published — SOC 1, SOC 2, ISO 27001/27002, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — with a documented unified-control mapping claiming up to 90% crossover and multiple certifications from a single audit. But the regimes a European operator like me actually needs — NIS2, TISAX, DORA, BSI IT-Grundschutz — do not appear, and dynamic framework updates are documented for three frameworks only, with the rest on a promised-soon basis. 1 6 8 9
The Lead Auditor
Nine regimes are named — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — with unified controls satisfying many frameworks through a documented mapping (the vendor claims up to 90% crossover) and NEW and UPDATED tags surfacing framework additions and standard changes. I found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz coverage, and dynamic updates were documented for only three frameworks as of May 2024, with the rest promised. 1 6 8 9 12
The Evidence Integrator
Nine-plus regimes — SOC 1 and SOC 2, ISO 27001, HIPAA, HITRUST, GDPR, CCPA, PCI, CMMC Level 1, NIST CSF 2.0 and Cyber Essentials — are served through one Unified Control mapping with up to 90% stated crossover, and action items carry new/updated tags when a framework is added or a standard changes, with dynamic updates rolling out across the catalogue. I found no public information on NIS2, TISAX, DORA or BSI IT-Grundschutz, so the documented coverage stays below the broadest level. 1 6 8 9
The Skeptic
Nine frameworks are named consistently across the homepage, privacy policy and product pages, with per-framework mapping articles into the unified control set and NEW/UPDATED tags when a standard changes — documented mapping work, not just logos. Two cautions: dynamic action-item updates were documented for only SOC 2, ISO 27001 and HIPAA as of May 2024 with all other frameworks promised "soon", and the marketing pages list nine frameworks while help-centre pages reference an ISO 27001 mapping, so the captured pages give different framework lists. The "up to 90% crossover" headline is a marketing figure we could not verify from the captured pages. 1 2 6 8 9
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
Evidence collection is genuinely automated — daily pulls, per-monitor status history, XLSX export, exclusions with compensating controls visible to the auditor — and the in-house audit firm consumes it directly. Export and audit reporting tools were still roadmap items at capture, and I find no public information on revision-safe history, on-demand evidence packs or management reports. 1 4 8 10 11 12
The GRC Consultant
Automated evidence is deep: daily collectors with per-monitor status history, auditor-visible exclusions backed by compensating controls, a thirteen-article evidence-request catalogue, a real-time SOC 2 readiness view, and auditors who can easily fulfill most evidence requests directly, working with integrations vetted by the vendor's own auditors. We found no public information on management report generators, revision-safe history for records beyond monitors, or reproducing a record as it stood on a given date. 1 10 11 12
The Drafted IT Officer
This is the product's spine: compliance data is collected automatically, integrations vetted by the vendor's own auditors satisfy evidence requests directly, my auditor can pull most evidence themselves, monitors keep a status history and export to XLSX, and exclusions with compensating controls are visible to the auditor. It falls short of the top because export and audit reporting tools are explicitly listed as coming soon, and I find no management-report generator or full revision-safe record history. 1 8 11 12
The Lead Auditor
This is the vendor's centre of gravity: compliance-relevant data collected automatically, daily monitor refreshes with status history per collector, auditors able to fulfil most evidence requests directly, and exclusions visible to the auditor. What I miss for revision safety is exactly what I demand — no public information on point-in-time reproduction of records, management reports, or evidence packs generated on demand, and export and audit reporting tools are themselves listed as coming soon on the roadmap. 1 4 10 11 12
The Evidence Integrator
Evidence collection is automated and continuous: collectors and monitors run against the connected estate with status history, XLSX export, auditor-visible exclusions, a real-time SOC 2 readiness view, and auditors who can fulfil most evidence requests directly. The defensible paper trail is thinner — export and audit reporting tools appear only on a roadmap, and I found no public information on on-demand evidence packs, management reports, read-only auditor access, or reproducing a record as it stood on a given date. 1 4 10 11 12
The Skeptic
Automated evidence collectors, continuous compliance monitors with violation status and remediation instructions, per-monitor status history, XLSX export, and auditors who "can fulfill most evidence requests directly" are strong — evidence is collected automatically rather than re-typed. But "export and audit reporting tools" appear on a published roadmap, and we found no public information on revision-safe change history for records, management report generators, or proof packs reproducible as of a past date; the certification itself comes from the vendor's own assurance firm. 1 4 10 11 12
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 connector set is named and real: AWS, GCP and Azure for asset discovery, Jira Cloud and ServiceNow automations that turn tagged ticket populations into evidence collectors, MDM connections for the inventory, and daily metadata pulls. The pages name "Integrations and APIs" as a service, but I found no public information on an API surface, webhooks or SCIM provisioning. 4 5 12 13
The GRC Consultant
Named connectors cover cloud accounts (AWS, GCP, Azure) with daily infrastructure metadata pulls plus Jira Cloud and ServiceNow, where an Automation turns a project-plus-tag rule into an Evidence Collector that surfaces matching ticket populations at audit time, with re-run, watch alerts and XLSX export — recurring evidence collection that is genuinely documented. Continuous monitors run against the connected estate; we found no public information on a documented REST API, webhooks, or single sign-on with SCIM provisioning, only Integrations and APIs as a named service. 4 11 12 13
The Drafted IT Officer
Real connectors to the real estate: cloud discovery from AWS, GCP and Azure with daily pulls, Jira Cloud and ServiceNow automations that turn tagged ticket populations into evidence collectors, MDM connections for the inventory, and email alerts plus re-run on the monitors. But the captured pages show no documented API detail, no webhooks and no SCIM provisioning, and MDM support for the asset intelligence view is still listed as coming soon. 4 5 12 13
The Lead Auditor
A real connector set — Jira Cloud, ServiceNow, AWS, GCP, Azure and MDM tools — feeds automated evidence collectors that pull daily, re-run on demand, filter to violations, and email alerts, which approaches continuous control monitoring against the live estate. The API appears only as a service name (Integrations and APIs) on the platform pages, and I found no public information on documented REST coverage of core objects, webhooks, or SSO with SCIM provisioning. 2 4 5 11 12 13
The Evidence Integrator
This is what I look for, and it is real: AWS, GCP and Azure accounts feed asset intelligence daily, MDM tools feed the asset inventory, Jira Cloud and ServiceNow automations turn ticket populations into evidence collectors, and monitors can be re-run, watched and alerted on the live estate. The API layer is the gap — integrations and APIs are named as a service, but the captured pages document no REST API, webhooks, SCIM provisioning or directory import, so the automation surface falls short of infrastructure-grade. 4 5 12 13
The Skeptic
Named connectors for AWS, GCP and Azure with daily pulls, Jira Cloud and ServiceNow automations that pull ticket populations as audit evidence, and exportable, re-runnable automated evidence show real plumbing into the estate. Two flags: one help page documents connecting to MDM tools while another lists MDM device support as upcoming — the captured pages give different pictures — and "Integrations and APIs" appears only as a service name; we found no public information on a documented API for core objects, webhooks, or SCIM provisioning. 4 5 11 12 13
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 whole chain sits under US jurisdiction: Thoropass, Inc. and the Laika Compliance assurance firm at a New York address, service hosting and all personal-data processing in the United States, and AI processing on Google Vertex AI and Azure OpenAI in US data centres, with a US Cloud Act exposure flagged on the subprocessor list. The DPA machinery is genuine — SCC Modules 2 and 3, Data Privacy Framework certification, a published subprocessor list — but the captured pages give no EU hosting option, and disputes go to the American Arbitration Association. 2 3 8
The GRC Consultant
Everything the pages affirm points away from Europe: the contracting entity is a New York firm subject to FTC enforcement, the service and customer personal data are stated to be hosted and processed in the United States, and AI processing runs in Google Cloud Platform and Microsoft Azure data centres in the United States. A DPA covering GDPR with SCC modules 2 and 3, a subprocessor list attached as an exhibit, and Data Privacy Framework certification keep this just above the floor; we found no public information on an EU hosting option. 2 3
The Drafted IT Officer
The captured pages prove a US setup end to end: Thoropass, Inc. with a New York mailing address, the service hosted and personal data processed in the United States, and all AI processing in Google and Microsoft data centres in the US, with no EU hosting option stated. Credit where due — a GDPR data processing agreement with Standard Contractual Clauses, a published subprocessor list, 72-hour breach notification and cooperation with EU authorities are all committed — but my risk register itself would sit under US law, with the subprocessor exposure flagged around the US Cloud Act. 2 3 8
The Lead Auditor
The chain is United States end to end: an entity with a New York mailing address under FTC enforcement, hosting and processing explicitly in the United States, and all AI processing on Google Vertex AI and Azure OpenAI in US data centres, with the subprocessor list itself exposing US-headquartered parents. A GDPR-grade DPA with Standard Contractual Clauses, Data Privacy Framework certification, a linked subprocessor list and a 30-day objection window is published, so this sits above nothing — but I found no public information on any EU hosting option. 2 3 8
The Evidence Integrator
Everything proven sits on the US side: Thoropass, Inc. is a New York entity, hosting and processing are stated to be in the United States, and AI processing runs in Google and Microsoft data centres in the United States, with FTC enforcement and no EU hosting option stated on the captured pages. GDPR machinery does exist — a published DPA with standard contractual clauses and Data Privacy Framework certification, and a subprocessor list with a 30-day objection window — which keeps this off the bottom of the scale. 2 3 8
The Skeptic
The chain is stated on the vendor's own legal pages as American end to end: Thoropass, Inc. with a New York mailing address, the service and all personal information hosted and processed in the United States, and all AI processing on Google Vertex AI and Azure OpenAI in US data centres, with the subprocessor exposure flagged as US Cloud Act. A published DPA with Standard Contractual Clauses, a linked subprocessor list and Data Privacy Framework certification keeps this off the bottom, but we found no public information on any EU hosting option. 2 3
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 not rated — no public information
We found no public pricing information on any captured page: the homepage, privacy policy and integrations pages name the services and frameworks — Thoropass Audit, Compliance Suite, penetration testing, AI, integrations — without a single price figure, edition boundary or billing period. 1 2 12
The GRC Consultant not rated — no public information
We found no public information on pricing transparency: the captured homepage, framework and platform pages name the services and frameworks but state no prices, editions, billing periods, user or entity boundaries, or setup fees. 1 8 12
The Drafted IT Officer not rated — no public information
I found no public information on pricing in any of the captured pages: no prices, editions, modules or billing periods appear anywhere I read, so working out the real invoice is not something I can attempt from public material. 1 2 8 12
The Lead Auditor not rated — no public information
I found no public information on pricing in the captured pages — the homepage, the multi-framework and platform pages, the privacy policy and DPA, and the help centre articles carry no edition, module, user or scale price. Pricing transparency therefore cannot be assessed from this evidence. 1 2 3 8 12
The Evidence Integrator not rated — no public information
We found no public information on pricing transparency: the homepage, multi-framework and platform pages name the services — audit, compliance suite, penetration testing, AI — but show no prices, editions, modules or billing terms of any kind. 1 8 12
The Skeptic not rated — no public information
We found no public information on pricing: no edition, price, billing period or setup fee appears on any page we read, including the homepage, the multi-framework product page and the integrations page. The captured pages are silent, so we report pricing as unknown rather than asserting it is unpublished. 1 8 12
European sovereignty — proven facts
1 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 | 0/4 pts | 2 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 Thoropass
Is Thoropass European?
Not determined: the vendor’s pages as captured do not say where Thoropass is based.
Where does Thoropass store data?
Thoropass stores customer data outside the EU by default, per the vendor’s page captured 30 Sep 2026.
Does Thoropass have a free plan?
Not stated on the vendor’s pages as of 1 Oct 2026.
What are the best alternatives to Thoropass?
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: Thoropass alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- We found no public information on pricing on the pages we read (thoropass.com, thoropass.com/privacy-policy, thoropass.com/data-processing-addendum, help.thoropass.com/en/articles/11887300-asset-intelligence, help.thoropass.com/en/collections/14300359-asset-inventory, help.thoropass.com/en/collections/3334200-controls and 7 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 13 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
- 2 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 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
- 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page thoropass.com Checked 22 Sep 2026 Details →
- 2 Privacy policy — found from the homepage www.thoropass.com Checked 30 Sep 2026 Details →
- 3 Data processing agreement (dpa) — found from the homepage www.thoropass.com Checked 30 Sep 2026 Details →
- 4 Asset & risk management depth — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 5 Asset & risk management depth — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 6 Controls, SoA & measures — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 7 Controls, SoA & measures — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 8 Framework & standard coverage — found from sitemap www.thoropass.com Checked 1 Oct 2026 Details →
- 9 Framework & standard coverage — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 10 Audit readiness & evidence — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 11 Audit readiness & evidence — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 12 Integrations & automation — found from sitemap www.thoropass.com Checked 1 Oct 2026 Details →
- 13 Integrations & automation — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →