COMPLIANCE INTELLIGENCE / REQUIREMENTS BEFORE REASSURANCE

The right requirements.
The evidence to decide.

Start with the rules and assurances that matter to your work. Find the published evidence, understand its limits and know what to ask before you commit.

01 / FIND THE EVIDENCE

Your requirements.
A more precise shortlist.

Find published claims that discuss your framework. A matching mention can describe a capability, condition or limitation. Read the statement before drawing a conclusion.

Purpose labels are curated against exact current evidence. Workflow support does not establish supplier assurance. Unclassified mentions remain available under “All published mentions”.

22 products with published SOC 2 mentions

FRAMEWORK MENTION / INSPECT THE SCOPE

Braintrust ↗

Braintrust describes inspecting agent traces and comparing prompts and models using datasets and automated or human scoring.

Vendor-reported assurance

Request the current full report, auditor opinion, period, exceptions, subservice carve-outs and customer controls.

vendor asserted · Reviewed 11/2/2026
Braintrust's public product page describes SOC 2 Type II and annually audited security controls. This is a vendor assertion: GovernAtlas has not inspected the underlying auditor opinion, reporting period, exceptions or system boundary.
Braintrust — official product or documentation page ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Collibra AI Command Center ↗

Collibra documents AI Command Center as the evolution of AI Governance, bringing AI registries and governance workflows together.

Vendor-reported assurance

Obtain the current document and confirm AI Command Center, purchased features, entities, cloud regions, dates and exclusions are covered.

vendor asserted · Reviewed 11/2/2026
Collibra's company trust center lists SOC 2 among its organizational certifications and attestations. GovernAtlas has not reviewed the underlying document or established that its precise scope covers AI Command Center; a company-wide listing must not be treated as product-specific assurance.
Collibra — Company trust center ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Credo AI Governance Platform ↗

Credo AI describes a platform for AI inventories, risk assessment, governance workflows and policy mapping.

Customer compliance workflow support

Inspect the current policy-pack version, control mappings, evidence exports and reviewer responsibilities; do not infer assurance from a supported framework.

vendor asserted · Reviewed 11/2/2026
Credo AI's product page describes pre-built SOC 2 policy packs, automated governance workflows and evidence generation. This is a vendor-described support capability, not evidence that Credo AI or a customer has passed a SOC 2 assessment.
Credo AI Product ↗
vendor asserted · Reviewed 10/14/2026
Credo AI presents policy packs and controls mapped to the EU AI Act, NIST AI RMF, ISO/IEC 42001 and SOC 2. Scope: vendor-described governance content. Framework mapping is not certification or a finding that a customer meets those requirements.
Credo AI Product ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Dataiku ↗

Dataiku describes model registries, approval workflows, lineage and performance monitoring within its enterprise AI platform.

Vendor-reported assurance

Request the current report and map its system boundary to Cloud versus installed software and the controls remaining with your team.

vendor asserted · Reviewed 11/3/2026
Dataiku states that it has completed SOC 2 Type II assessments and directs customers to an account representative for the report. GovernAtlas has not reviewed the report's period, opinion, exceptions or service coverage; the statement does not establish assurance for every self-managed deployment.
Dataiku — Product capabilities and published scope ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

DataRobot AI Platform ↗

DataRobot's documentation index lists deployed-workload monitoring, OpenTelemetry metrics and logs, and deployment approval policies. This index does not establish feature availability in every edition or deployment.

Vendor-reported assurance

Obtain the current report and reconcile the exact SaaS service, regions, integrations and customer controls.

vendor asserted · Reviewed 11/3/2026
DataRobot's trust page states that its cloud control environment undergoes an annual SOC 2 Type II assessment. GovernAtlas has not reviewed the report, operating period, auditor opinion or exceptions, and does not extend cloud assurance to every deployment model.
DataRobot, Inc. — Product capabilities and published scope ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Fiddler ↗

Fiddler describes agent monitoring, evaluations, inline request and response enforcement, and recorded governance decisions.

Vendor-reported assurance

Request the report through the appropriate confidentiality process and compare the purchased deployment and customer controls with its scope.

vendor asserted · Reviewed 11/3/2026
Fiddler describes an annually audited SOC 2 Type II report covering Security, Confidentiality and Availability, available to customers and prospects under NDA. GovernAtlas has not obtained that report or reviewed its period, opinion, exceptions and system boundary.
Fiddler AI — Product capabilities and published scope ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Helicone ↗

Helicone documentation distinguishes an AI Gateway workflow from use of customer-managed provider keys. It describes tracking request costs, latency and errors; its competitor comparisons and absolute uptime or latency promises are not independently established by this documentation.

vendor asserted · Reviewed 11/2/2026
Helicone's pricing page lists SOC 2 and HIPAA compliance with the Team plan, with Enterprise inheriting Team features. Scope: vendor-advertised plan support. This source does not establish BAA execution, eligible downstream providers or a compliant healthcare configuration.
Helicone — Plan scope and security options ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

HoneyHive ↗

HoneyHive describes agent tracing, online evaluations, experiments, datasets, annotation queues and prompt management. Its site distinguishes SaaS, hybrid and self-hosted operating models and describes exporting telemetry and evaluation records.

vendor asserted · Reviewed 11/2/2026
HoneyHive's pricing FAQ asserts HIPAA, GDPR and SOC 2 Type II compliance and says data is encrypted at rest and in transit. These are vendor assertions; GovernAtlas has not reviewed an assurance report or tested the controls.
HoneyHive — Plan scope and security options ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Hyperproof ↗

Hyperproof describes control mapping, risk workflows, audit evidence requests and third-party assessments.

Vendor-reported assurance

Obtain the complete report and determine whether the commercial or separate government environment is in scope.

vendor asserted · Reviewed 11/3/2026
Hyperproof's security FAQ describes SOC 2 coverage for Security, Availability and Confidentiality. GovernAtlas has not reviewed the auditor report or established its type, period, exceptions and exact system boundary from that public statement.
Hyperproof — Product capabilities and published scope ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Immuta ↗

Immuta describes authoring data policies and applying masking or access restrictions through supported data infrastructure.

Vendor-reported assurance

Request the full current report and compare the SaaS services, integrations and complementary customer controls.

vendor asserted · Reviewed 11/3/2026
Immuta's trust page lists SOC 2 Type 2 assurance. GovernAtlas has not reviewed the underlying report, audit period, opinion or exceptions; the public label alone does not establish the precise service boundary or customer configuration.
Immuta — Product capabilities and published scope ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

Langfuse ↗

Langfuse documents tracing, prompt version management, datasets and evaluation workflows.

Vendor-reported assurance

Request the current report and reconcile cloud service boundaries, reporting period, subservice organizations and customer controls.

vendor asserted · Reviewed 11/2/2026
Langfuse documents completion of a SOC 2 Type II audit for Langfuse Cloud and makes the report requestable on Pro, Team or Enterprise plans. GovernAtlas has not reviewed the restricted report, period, auditor opinion or exceptions; this statement is not an assessment of self-hosted installations.
Langfuse — Cloud security: soc2 ↗
vendor asserted · Reviewed 11/2/2026
Langfuse's compliance FAQ states that its cloud offering supports SOC 2 Type II, ISO 27001 and GDPR requirements and offers a HIPAA-ready region. These remain supplier assertions; GovernAtlas has not inspected an auditor's report or determined regulatory compliance.
Langfuse — Compliance FAQ ↗
Read the full dossier & evidence ↗

FRAMEWORK MENTION / INSPECT THE SCOPE

LangSmith ↗

LangChain describes LangSmith tracing and monitoring for model calls, tool activity, latency, cost and online evaluations.

Vendor-reported assurance

Obtain the actual document and reconcile service, deployment, hosting region and customer-operated infrastructure with its scope.

vendor asserted · Reviewed 11/3/2026
LangChain's EMEA page states SOC 2 Type 2 assurance for LangSmith and directs buyers to its trust center for supporting documents. GovernAtlas has not reviewed the underlying report or certificate, current validity, exceptions or coverage across cloud, hybrid and self-hosted offerings.
LangChain — Product capabilities and published scope ↗
Read the full dossier & evidence ↗

READ THE DISTINCTIONS

What does a compliance claim
actually tell you?

A framework mention is a lead.

A current published claim makes a product discoverable here. Its original classification remains visible. A negative statement, a restricted feature or a qualified promise can also mention a framework: matching text is not a positive compliance assessment.

A BAA is a scoped agreement.

HHS explains that a cloud provider handling ePHI on behalf of a covered entity or business associate may itself be a business associate, even when it cannot decrypt the data. Establish the relationship, obtain the appropriate agreement and assess the safeguards for the service you intend to use.

Read HHS cloud guidance ↗

A report is not the same as a law.

SOC 2 is an assurance report; ISO 27001 concerns an information security management system. Neither label alone answers your HIPAA deployment question. Ask for the relevant report or certificate, its scope, date and exclusions, and evaluate what it actually covers.

AICPA SOC resources ↗ · ISO/IEC 27001 scope ↗

Your use still needs a review.

The HIPAA Security Rule addresses administrative, physical and technical safeguards. Your risk analysis, workforce practices, integrations and configuration remain part of the assessment. Review before sharing PHI and when material circumstances change.

Read the HHS Security Rule summary ↗

PRIVACY & AI / TWO DIFFERENT REVIEWS

Start with your role.
Follow the actual use.

GDPR: follow the processing.

Identify who decides the purposes and who processes on instructions. Review the DPA, subprocessors, transfers, rights assistance and retention for the actual service. A vendor privacy claim or an EU hosting option leaves those questions open.

Read the DPC contract guidance ↗

EU AI Act: identify the system and role.

Assess the intended purpose, operator role and current applicable obligations before selecting controls. A mapping platform can help organize work; its policy pack does not establish legal applicability, a completed conformity assessment or customer compliance.

Use the official applicability checker ↗

02 / TAKE BETTER QUESTIONS INTO THE ROOM

A claim starts the conversation.
Evidence moves it forward.

Review the auditor's report for the system you will actually use. A badge or platform readiness score leaves the most important questions unanswered.

SOC 2 is an assurance report, not a product certification or a guarantee that every control operated without exceptions. These questions prepare a review; they are not an exhaustive assessment.

Answers stay in this page’s memory. Export before leaving or switching frameworks; switching clears answers. Record source links and review notes, never patient information or credentials. “Evidence received” is not a finding of compliance.

Primary references: AICPA: SOC suite of services ↗

01 / Report identityIs this the actual SOC 2 report from the issuing CPA firm?

Request the complete report through the approved access process. Record the service organization, issuing firm, report type and intended-use restrictions. An engagement letter or readiness assessment is not the completed report.

02 / Period & continuityWhat point in time or operating period does the report cover?

Record the as-of date for Type 1 or the period for Type 2. Assess any gap since period end and request information about subsequent changes or a bridge letter where appropriate. A bridge letter is management's statement, not another audit.

03 / System & categoriesAre the purchased service and relevant trust-services categories covered?

Read the system description, boundaries, locations and selected categories. Reconcile the exact product, edition, cloud deployment and integrations. Do not generalize from a parent company or unrelated service.

04 / Opinion & exceptionsWhat does the auditor conclude, and what tests found exceptions?

Review the opinion, test procedures, results, exceptions and management responses. Assess relevance to your use; neither the existence of an exception nor a clean headline replaces that assessment.

05 / Subservice organizationsWhich providers are included or carved out?

Identify the inclusive or carve-out approach and complementary subservice controls. Obtain relevant downstream evidence when needed. A cloud provider's report does not automatically establish the vendor's application controls.

06 / Your controlsWhich complementary user-entity controls must we operate?

Extract applicable customer controls, assign owners and test the configuration. Include identity, access reviews, secure integrations and incident escalation. Record unmet controls before approving use.

07 / Decision & renewalWhat remains unresolved, and when will we revisit it?

Keep a dated review record with document version, findings, service scope, acceptance owner and follow-up. Reassess after a new report, material change or incident. Never publish a restricted report without authorization.

QUESTIONS ANSWERED

Before you shortlist.

Does GovernAtlas certify these products?

No. Discovery links published claims to their sources. Inclusion, payment and a framework mention do not establish compliance or suitability for your deployment.

What if a vendor has no matching evidence?

Our current coverage may be incomplete. Use the checklist to ask the vendor for documents and submit public sources for editorial review. An unknown result is not an adverse finding.

Can I use the checklist for a clinical AI tool?

Use it for the PHI-handling review, then separately evaluate clinical safety, intended use, human oversight and any applicable medical-device requirements. HIPAA alone does not establish clinical safety or effectiveness.

Can companies pay for a better evidence classification?

No. Public research and this checklist stay free. Company subscriptions do not change editorial gates, evidence classifications or search eligibility.

Continue your review: vendor risk assessment ↗ · security questionnaire review ↗ · submit an evidence issue ↗

GovernAtlas editorial buying method · reviewed November 2, 2026. Primary references: HHS business associates, HHS risk analysis. The checklist is a preparation aid, not an exhaustive legal assessment.