One platform.
Two layers.
Dossiers OS is where your team and your systems work: customer records, monitoring, review, and the API you integrate with. Dossiers Cloud runs in our infrastructure and provides the verification and screening services Dossiers OS relies on.
Your work happens in Dossiers OS.
The services run behind it.
Your systems and your team connect to Dossiers OS. When a workflow needs identity verification or screening, Dossiers OS sends the request to Dossiers Cloud and keeps the result on the customer record.
Your environment
Your systems and team
- Customer and account systems
- Payment and event sources
- Analysts and reviewers
- Your AI agents
Where the work happens
Dossiers OS
- Customer, account, and counterparty records
- Rules, monitoring, and alerts
- Investigations and review history
- Access, configuration, and audit trail
Dossiers infrastructure
Dossiers Cloud
- Identity and document verification
- Liveness checks
- AML screening
- Operated by our team
Dossiers OS
The operating system your team works in. It holds the records, evaluates activity against your rules, and carries alerts through review. Your systems connect to it through its own API.
Dossiers Cloud
Verification and screening services hosted and operated by Dossiers. It processes the requests Dossiers OS sends and returns the results. It is not a separate product your team logs in to.
The record stays in Dossiers OS
Verification outcomes, screening matches, and the decisions made on them are kept with the customer in Dossiers OS, where your team reviews them.
How the layers work together.
Do our systems call Dossiers Cloud directly?
No. Your systems connect to the Dossiers OS API. Dossiers OS sends verification and screening requests to Dossiers Cloud and brings the results back to the customer record.
What does Dossiers Cloud receive?
The details a verification or screening request needs, such as the identity information or documents for that check. We’ll review the data flows, retention, and hosting location with your team as part of deployment planning.
Can we use other providers?
Identity verification can use Dossiers Cloud or another supported provider. Your own custom screening lists are checked alongside screening results. We’ll confirm the supported options for your deployment.
Build on
the Dossiers OS API.
Dossiers OS has its own authenticated API. Send records and activity in, manage configuration, and take outcomes back into the systems that act on them.
- Customers and parties
- Create and update individuals, entities and their stakeholders, accounts, counterparties, and identification documents. Use your own references so later activity finds the same records.
- Activity ingestion
- Send transactions and custom events as they happen. Supported transactions are evaluated against your rules on ingestion, and the outcome is returned in the response.
- Screening and verification
- Screen customers, read screening history, and start identity verification sessions. Manage custom screening lists that are checked alongside screening results.
- Configuration
- Manage rules, products, currencies, constants, event definitions, alert workflows, and webhook destinations. Backtest rule changes against historical or sample transactions before applying them.
- TypeScript SDK and Tenant Sync
- Use the typed SDK for API resources. Keep configuration in version-controlled files and plan, confirm, and apply changes with the Tenant Sync CLI.
- Outcomes and webhooks
- Receive rule outcomes in API responses or send configured events to your systems. Plan how the receiving system handles retries, duplicate messages, and delivery failures.
Connect the systems
behind the review.
Map customer information and activity from your systems into Dossiers OS, then pass configured outcomes back to the systems that act on them.
Data flow
Keep the references connected
From your systems
- Customer
- Haruka Tanaka
- Customer reference
- CUS-00482
- Account reference
- AC-4821
- Evidence
- Identity and due diligence results
In Dossiers OS
- Individual
- Customer profile and identifiers
- Account owner
- CUS-00482 owns AC-4821
- Review context
- Supporting evidence on the record
- Available to
- Screening, monitoring, and investigation
Work with the systems you have.
Can we bring existing verification results?
Yes. Customer information and verification evidence can be brought through the Dossiers OS API. We’ll review the required fields and how your team will access the supporting evidence.
Where do device and session signals come from?
Your applications or connected providers supply device, session, and location evidence. Dossiers OS connects that information to the relevant records; the capture method is part of the integration scope.
Can a detection stop a payment?
For a pending transaction, a configured rule can return a blocked outcome in Dossiers OS. Your payment system must use that outcome to enforce a hold or rejection.
AI and agents,
within the scope you set.
Connect compatible AI assistants and agents through the Dossiers OS MCP server. Decide which records they can read, which tools they can call, and where a person has to approve.
- MCP server
- Connect compatible AI assistants and agents to Dossiers OS through the Model Context Protocol (MCP).
- You set the scope
- Choose the model, instructions, and permitted tools through organization-scoped connections.
- The sources stay visible
- Each run retains its definition and output. Inspect the run history alongside the records used.
- Actions have controls
- Dossiers record tools provide read access. Connected write tools can request approval with the proposed arguments.
- Review the data flow
- Data available to a model depends on the tools, instructions, and provider you configure. Review those flows and the provider’s terms as part of deployment.
- Bring your own agents
- Use permitted Dossiers OS API tools from your own agents. Define the records they can access and the actions available to them.
Set access around the work.
Define who can use Dossiers OS, what connected systems can access, and how information moves to Dossiers Cloud and other providers. Agree the controls and supporting evidence your institution needs.
People and permissions
Use roles and permissions to control access to customer information, operational work, and configuration.
Scoped API access
Give integrations the permissions their task requires. Separate access to ingestion and configuration when setting up system connections.
Reviewable history
Inspect recorded activity, review outcomes, and configuration versions. Agree the records and export requirements your institution needs.
Plan deployment before connecting production data.
How do we plan the deployment environment?
Discuss your cloud, private-network, or on-premises requirements for Dossiers OS with our team. Review hosting, network boundaries, data residency needs, the connection to Dossiers Cloud, and other connected systems or providers. Agree the supported configuration for your environment.
Who manages the deployment?
Dossiers Cloud is hosted and operated by our team. For Dossiers OS, agree who manages access, updates, backups, recovery, delivery monitoring, and incident response. Review operations and support responsibilities before launch.
Can we review your security controls?
Share your security questionnaire, documentation requirements, and review, approval, or audit needs. We’ll work through the applicable controls for Dossiers OS and Dossiers Cloud with your team.
Start where your
team needs it.
Choose the first workflow around your operation. Agree the data, rules, and review process, then test the journey with your team.
- 1
Connect the context
Map customer, account, and counterparty references across transactions, attempts, and events. Agree the identifiers, timestamps, and evidence each workflow needs.
- 2
Configure the review
Set up verification and screening, and define detection conditions with the rule builder. Set product scope, event definitions, access, and assignments around your institution.
- 3
Handle the outcome
Use Dossiers OS API responses or configured webhooks in your workflow. When Dossiers OS blocks a pending transaction, your payment system enforces the hold or rejection.
- 4
Test the workflow
Test representative activity, duplicate submissions, failed deliveries, and review outcomes. Agree monitoring and operational responsibilities before rollout.
Bring your architecture. We’ll map the integration.
Walk through your data sources, providers, and deployment requirements with our team.