Persona orchestrates identity, Forest orchestrates the operation around it

Ask a fintech's ops team where a customer "lives" in their systems and you rarely get one answer. The identity record sits in the verification tool. The transactions sit in the core ledger. The support history sits in the ticketing system. The risk signals sit in a fourth place. When a case needs a decision, someone opens four tabs and reassembles the person by hand. The verification was never the bottleneck. Stitching the customer back together was.

Persona took the identity half of that problem seriously, and built something more ambitious than a single check.

Persona lets teams assemble their own KYC, KYB and AML flows

Persona is a configurable identity platform. Rather than shipping one fixed verification, it hands a team the building blocks:

• Dynamic verification flows that adapt by geography and risk.

• Government ID and biometric checks, run inside the flow.

• Third-party data, ingested as another input to the decision.

• Case review, handled in the platform.

• Orchestration logic, so decisioning around identity runs end to end.

Teams assemble those into their own KYC, KYB, AML and fraud processes, across 200+ countries, without heavy engineering.

That configurability is what separates Persona from a plug-and-play checker. Persona returns a verdict and also orchestrates the identity lifecycle that produced it: which checks ran, in what order, and how the record is kept current afterwards. It is worth being precise about, because it is also where the line with Forest gets interesting.

Where Persona's identity layer ends and Forest's operational layer begins

Persona orchestrates identity. Forest orchestrates the operation. Two different layers, and the difference is the whole point.

Persona's orchestration runs deep inside the identity domain: which checks fire in what order, how a verification flow adapts by geography and risk, how identity cases get reviewed, how identity records stay current. It is the best available answer to "is this person or business who they claim to be, and how do we manage that over time."

A regulated operation is bigger than identity. A single onboarding or investigation pulls together the identity verdict, the customer's payment history, their transaction-monitoring alerts, their support tickets, sanctions signals from other providers, and the business rules that decide what happens next. That cross-system work, where identity is one input among several and where an action has to land on core systems and be logged, sits above the identity layer. That is the operation. That is Forest.

How a Persona verdict becomes a logged action on your core systems

A Persona verification flows into a Forest workflow as one authoritative signal. Your operators see the Persona result next to the transaction data, the monitoring alerts and the case history, on one governed surface, and the workflow applies the rules your operations team defined: clear and proceed, or open a case routed to the right reviewer with the full picture already assembled. The operator stops opening four tabs. The person arrives already stitched together.

Because one permission model and one audit trail cover every action on that surface, human or agent, the record spans the entire operation rather than the identity slice alone. When a regulator asks who decided what and on what basis, the answer comes from a single trail covering identity, transactions and everything else, instead of one story in Persona's dashboard and a second story somewhere else.

The two kinds of orchestration reinforce each other. Persona keeps the identity signal trustworthy and current. Forest makes it actionable alongside everything the decision actually depends on.

That's the direction Forest is heading, and one we already deploy with clients through partners like Persona: deep identity orchestration from a platform built for it, feeding an operational layer that runs the rest of the regulated process, with proof spanning the whole stack.

Persona gives you the verdict, Forest turns it into a decision you can prove

Persona made identity a configurable, living process, orchestrated end to end inside its domain. Forest takes that verdict and runs the regulated process around it: on the full picture, under the rules your team set, on the systems where the action has to land.

Whether the operation scales comes down to what happens in the minutes after the verdict arrives. Which signals it meets. Whose rules apply. Where the resulting action lands, and whether anyone can reconstruct the decision six months later.

That is the difference between an onboarding queue that clears and four tabs open every time a case needs a decision.

Get Persona and Forest running on your onboarding queue

If your onboarding runs on one fixed verification and you need flows that adapt by geography and risk, talk to Persona.

If your team already has strong identity orchestration and still reassembles the customer by hand every time a case needs a decision, book a Forest demo and show us the flow you're trying to run.

Forest is the operational infrastructure for regulated fintechs. Compliance, ops, and support teams work on your systems alongside your AI agents, under one permission model and one audit trail. On your own infrastructure. Learn more at forest.app.