Multi-supplier orchestration
Forest is the orchestration layer above your providers. KYC, KYB, screening, payments, comms run as configured workflow steps. Every response logs to the case.
Forest is where your team plugs providers into your operations as configured workflow steps. Pick one per step, swap as your stack evolves, run two in parallel when it helps, all auditable.
Providers as configured steps, not code
Each provider call is a step in the workflow your team designs. Sumsub at step 2, ComplyAdvantage at step 4, Stripe at step 6. Configure without engineering.
Routing per segment, jurisdiction, product
Set provider routing rules at step level. IDV through Sumsub in France, IDnow in Germany, Persona in the US. One workflow, the right call per case.
Parallel running and A/B testing
Run two providers on the same step to compare coverage or cost. Forest captures both responses on the case and lets your team consolidate the result.
Connectors, MCP, datasources, APIs
Forest reaches your providers through MCP connectors (for action calls inside workflows) and datasources (for systems of record). Direct API integrations cover the rest.
Switch a provider in a config change
Replacing one provider with another is a reconfiguration of the step, not a re-platforming. The workflow keeps running, the audit trail follows, no migration project.
Every response logged on the case
Provider payload, latency, status, and reasoning attach to the case as part of the audit trail. The full chain of who called whom is regulator-ready.

Built for fintechs that pick their own stack
A single workspace, every provider
Every provider call, every response, every decision on the same case. Your team works one view, not a tab per vendor portal.
Governance across providers
RBAC, approvals, and audit apply across vendor calls the same way. Switching a provider does not break your governance.
Swap and stack, by design
Add a provider, swap one for another, or run two in parallel as a configuration change. No re-platforming, no lost audit, no lock-in.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
Why orchestrate providers instead of picking one stack?
One provider rarely covers every market, every segment, and every product. Regulated fintechs end up with three to seven providers across IDV, KYB, screening, payments, and comms. Forest gives you one workspace above all of them, with the freedom to switch as requirements evolve.
How does Forest connect to providers?
Forest reaches providers through MCP connectors (for action calls inside workflows, like calling Sumsub) and datasources (for systems of record, like reading from your CRM). Direct REST API integrations cover providers that ship neither.
Can I switch providers without losing the audit trail?
Yes. The audit trail is anchored to the case, not the provider. Switching Sumsub for Onfido on a step preserves every prior decision on prior cases, while new cases route to the new provider. The historical record stays intact.
How do I A/B test two providers?
Configure two parallel provider calls on the same step. Forest captures both responses on the case. Your team or your AI agents consolidate the result per your rules (best score, consensus, escalate on disagreement).
How do AI agents fit into multi-provider workflows?
AI agents fit in two ways. They can connect to Forest's MCP Server to read operational data and trigger actions in your workflows. Or your workflows can call AI agents through MCP tasks, the way they call any other provider. Either way, permissions and audit apply.
How does Forest handle data residency when calling providers?
The Forest backend runs inside your infrastructure. Customer data travels to a provider only at the moment its service is called, and only the data the step requires. The response logs back to the case. Data stays in your systems of record.
How do I include a new provider in an existing workflow?
On Forest, adding a provider is a reconfiguration: pick the step, select the connector, set the routing rules. The workflow keeps running, the audit trail extends, no engineering ticket needed for most providers.

