Crypto
With Forest, run onboarding, AML, custody reconciliation, and MiCA reporting on top of your custody and chain analytics providers.
Forest hosts the off-chain side of crypto ops: customers, KYC, AML, fiat reconciliation, regulator reporting. On-chain stays with your custody provider.
Customer onboarding for crypto
Retail and institutional KYC, KYB, source-of-funds checks, and initial sanction screening run as steps. Risk routing per customer tier and jurisdiction.
Custody reconciliation
Balances and transactions read live from Fireblocks, Anchorage, BitGo, Copper, or your custody provider. Breaks become cases routed to your treasury team.
Sanctions and PEP at sub-second latency
Screening against your list provider runs at deposit, withdrawal, and counterparty creation. True hits route to a reviewer with the case bundle attached.
Travel rule workflow
Inbound and outbound transfers carry the originator and beneficiary data your jurisdiction requires. Forest enforces the workflow; providers carry the message.
MiCA and partner-bank reporting
Regulatory submissions, reserve reports, and partner-bank statements package automatically and route through your existing transmission channel.
Audit across on-chain and off-chain
Every action by your team, your AI agents, and your custody provider lands at the record level. Regulator-ready bundles export on demand.

Built for regulated crypto
A complete view per customer and wallet
Customer, fiat accounts, wallets, transactions, screening, and prior cases live on the same record. Treasury and compliance work from one view.
Governance for humans and AI agents
Roles, approvals, and escalations apply to your team and your AI agents the same way. Every action lands in one audit trail.
Plug into your custody and analytics stack
Fireblocks, Anchorage, Chainalysis, TRM, and your providers fully connected, ready to tap from your workflows. Adding a tool is configuration.
Plug into your crypto stack
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
Does Forest hold custody or sign transactions?
No. Custody and signing stay with your custody provider. Forest reads balances, triggers approved actions via the provider's API, and records the result. Private keys never enter Forest.
How does Forest connect to my custody and analytics providers?
Forest reaches your stack through datasources (for customer, wallet, and transaction data) and through MCP connectors (for calling Fireblocks, Chainalysis, TRM, or your providers inside workflows).
How does Forest support travel rule compliance?
Travel rule data exchange runs as workflow steps that call your travel rule provider (TRP, Notabene, Sumsub Travel Rule). Forest enforces the workflow, the audit, and the case bundle; your provider carries the message.
How does Forest handle MiCA and partner-bank reporting?
Reports run as scheduled workflows. Forest assembles each one from operational data, runs internal review and approval, and exports for transmission. Each submission is logged with the case.
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 when its service is called, and the response is logged back to the case. Data stays in your systems of record.
