Identity verification
Forest orchestrates identity verification across the customer lifecycle: KYC for individuals, KYB for businesses. Unify review queues, AI extraction, UBOs, audit in one workflow.
Forest is the workspace your team uses to take every applicant, individual or business, from submission to opening. Provider calls, screening hits, AI agent reasoning, reviewer decisions all live on the same case.
One review queue, every case type
KYC, KYB, re-verification, sanctions hits land in one inbox on Forest. Your team filters by type, jurisdiction, or risk and assigns the work in a click.
Multi-provider, multi-source orchestration
Sumsub, Onfido, IDnow, Dotfile, Ondorse, Pappers, Companies House, ComplyAdvantage all plug in. Forest reaches them through datasources and MCP connectors.
AI agents under your governance
Your AI agents extract passport data, parse incorporation docs, follow ownership chains. Your reviewers approve or override. Every action lands in one audit trail.
Continuous, not point-in-time
Perpetual KYC refreshes and KYB ownership-change workflows are part of the same workspace. Re-verifications surface as cases with the reason logged.
Compliance, underwriting, ops on one case
Compliance handles regulatory, underwriting handles risk, ops handles execution. Forest gives all three teams shared visibility with field-level RBAC.
The audit your regulator expects
Every provider call, AI agent reasoning step, reviewer decision, and document version logs against the record. Filtered exports for ACPR, DORA, 6AMLD, MiCA in a click.

Why Forest
One backend for every identity case
KYC for individuals, KYB for businesses, sanctions screening, re-verification on changes, all in one workflow your team owns. No more tool-switching, no more reconciling data across dashboards.
Every team, same case
Compliance, underwriting, ops, AI agents all working the same case under shared visibility and field-level RBAC. Decisions are coordinated, not chained through email or Excel.
Every decision, traceable end-to-end
Every action (human, AI, or provider) logs with the full causal chain. Export for any framework, any entity type, any time period, in one click.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
What is the difference between KYC and KYB on Forest?
KYC verifies individuals (customers, account holders, UBOs). KYB verifies businesses (legal entity, ownership chain, sanctions). On Forest, both run from the same workspace with the same RBAC and audit. See the dedicated deep dives: [[kyc]] and [[kyb]].
Can I keep my existing IDV and KYB providers?
Yes. Forest connects to Sumsub, Onfido, IDnow, Veriff, Persona, Dotfile, Ondorse, Pappers, Companies House, ComplyAdvantage, and most major providers through datasources, MCP connectors, or direct APIs. You add Forest above your stack, no migration needed.
How do I manage an identity verification workflow in Forest?
Each step is a configurable task: document upload, IDV call, registry lookup, sanctions screening, UBO discovery, reviewer approval. Rules and provider routing are set per step. Forest ships templates for KYC and KYB workflows that your team configures without engineering.
How does Forest handle ongoing monitoring after onboarding?
On Forest, your team configures perpetual KYC refreshes (risk-based, anniversary, watchlist) and KYB ownership-change re-verifications. Forest surfaces the case when triggered and logs the reason. KYC and KYB stop being point-in-time.
How do AI agents fit into identity verification?
Forest is an AI agent runtime. Your AI agents read passports, parse incorporation documents, follow ownership chains across jurisdictions, score risk. Forest is both an MCP Client (consumes AI agents) and an MCP Server (exposes workflows to AI agents), under the same RBAC and audit trail as your reviewers.
How do you ensure customer data never leaves our environment?
The Forest backend runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record.
How does Forest support our compliance posture under DORA, 6AMLD, MiCA, and GDPR?
Forest supports your obligations under those laws by giving you the operational evidence layer: audit trails, RBAC, 4-eyes validation, workflow governance, and self-hosted deployment so your data stays in your infrastructure. Forest holds SOC 2 Type II. Your team holds the licences and the policies; Forest provides the proof of how your controls ran. Compliance with any specific framework still depends on your policies and procedures.

