Skip to content

Built for the people who have to prove what their AI did.

Who uses Dobby today, and what each side of a vendor review gets out of the same evidence pack.

AI vendor selling into banks

Passing a bank's vendor-risk review

Procurement asks for the EU AI Act evidence, the DORA ICT third-party register and the SOC 2 controls mapping. Today your engineers scramble a deck. Dobby connects out-of-band to the workloads you already run and produces the artifact instead.

Every run scanned against EU AI Act (Art 12, 14, 28), DORA and SOC 2 Type II

A four-state verdict per control: compliant, violated, needs review, or unverifiable

An evidence pack per framework: control matrix, gap report, findings, SHA-256 manifest

Enforced non-custodial: raw payloads land in your own dataset, never Dobby's

Risk team at a bank or fintech

Comparing twenty AI vendors on one scale

Each vendor arrives with a different deck and a different controls story. Dobby gives every one of them the same shape, so a reviewer compares control matrices and gap reports rather than slides.

The same control matrix for every vendor, mapped to the frameworks you require

A gap report ranked by severity, with the remediation each gap needs

A tamper-evident manifest the auditor can re-hash to confirm nothing changed

Nothing in the request path: Dobby reads run telemetry, it never gates traffic

Platform or security team

One policy hierarchy over every framework you run

Product teams ship agents on CrewAI, LangChain, Google ADK and custom SDKs. You need one set of rules over all of them, enforced at the layer that owns each rule, and a record you can hand to an auditor.

Four policy layers, stricter wins: Platform, Org, Tenant, Process

Connectors for CrewAI, LangChain, OpenAI, Google ADK, AWS Bedrock, Mastra and a custom SDK

Immutable audit trail with 365-day retention, RBAC and enterprise SSO

Regional data residency pinned at workspace creation: IL, EU or US

Compliance lead

Knowing what cannot be proven yet

A dashboard that reports green when nothing was measured is the risk. Dobby's verdict has a fourth state, unverifiable, so a coverage gap is reported as a gap and never as a pass.

A coverage figure that excludes what could not be evaluated

Findings written for the procurement reviewer, not only the engineer

Scans run against the compliance modules each workspace activates

Fintech AI Evidence is live today; additional modules are in development

The shape of the platform

3
Frameworks in Module #1
4
Policy layers, stricter wins
3
Data regions: IL, EU, US
SOC 2
Type II in progress
Out-of-band
Never in the request path

Get your AI through the review.

Start with Fintech AI Evidence: connect a workflow, scan it against EU AI Act, DORA and SOC 2, export the evidence pack.

Who Dobby Is For | Dobby AI