THE REGULATED EXECUTION STACK

Turn your back‑office into an execution layer

Forest is the foundation your people, BPOs and AI agents call to run critical actions on your regulated databases. Every call gets the right permissions on the right data, and every case goes to whoever should handle it next.

Your stack

Layer 04

Agents & models

Suggest

Layer 03 · Forest

Execution

Decide & record

Layer 02

Your systems

Run the product

Layer 01

Regulated core

Hold the money

With Forest as your execution layer, you can

01

Create workflows

Deterministic or probabilistic, built by your ops on your own databases.

02

Encapsulate your business logic

Call it from your back-office, Zendesk, Claude or your own apps.

03

Build your semantic layer

One taxonomy of your actions on top of your endpoints, so your ops, BPOs and agents act on their own, within your rules.

The stack

Your regulated ops stack, agent‑ready

Forest is the execution layer that lets you put AI agents into your processes today, and stop rebuilding your stack every time a new model ships.

Follow a process

Turn your phone to landscape, or scroll sideways, to see the whole stack.

4 · Agents & models · suggest

Models

rented by the call

Claude · GPT · Mistral · Gemini

Agent builders

build and run agents

Claude Agent SDK · Dust · E2B

Specialist agents

one task each

Bretton · spektr · Resistant AI

Your harness

SOPs · memory · tests

built by you

People · decide

People

operators · BPO · managers

Onepilot · TaskUs · in-house

Above: agents suggestBelow: checked actions
Signals · raise cases

Signals & screening

KYC · screening · fraud · on-chain

Sumsub · ComplyAdvantage · Topograph · Sardine · Chainalysis

Decision engines

credit · onboarding · fraud rules

Taktile · Alloy · Oscilar

Channels

app · helpdesk · chat

Zendesk (Forest app) · Fin · Slack

3 · Execution · Forest · what the supervisor examines
Work interface

Forest UI

operators and managers

Gateway API

Zendesk · n8n · your apps

MCP server

agents, each under a role

CLI & headless

onboard and run

Run operations

Workflows

rules · AI steps · humans

Segments

saved views of your data

Dispatch & collaborate

to people, BPOs, agents

Approval & escalation

four-eyes · back to a person

Build your back-office

Introspection

your tables become business objects

Semantic layer

what each object and action means, who may use it

Smart actions

coded once · freeze · refund

Roles & permissions

per role, per segment · who decided, before/after, in your DB

Control · proves

Identity

people and agents

Okta · Entra Agent ID · AgentCore

GRC & reporting

controls · reports · audits

Archer · ServiceNow IRM · ValidMind

Supervisor

ACPR · BaFin · FCA · NYDFS

asks who decided, under which rule

2 · Your systems · run the product

App database

+ replicas · events

yours · read in place

Core API

regulated writes

smart actions call it

Business tools

CRM · helpdesk · billing

HubSpot · Stripe · Zendesk

Orchestration

technical flows

Temporal · Kestra · n8n

1 · Regulated core · holds the money · licence · PSD2 / EMD · safeguarding · MiCA

Licence, BaaS & issuing

bank · EMI · CASP · cards

Swan · Treezor · Solaris · Marqeta

Core & ledger

core banking · ledger

Mambu · Thought Machine · Skaleet · Formance

Rails & open banking

cards · SEPA · instant · agentic

Adyen · Stripe · Tink · Mastercard Agent Pay

Blockchain & custody

custody · stablecoins

Fireblocks · BitGo · Dfns

ForestYour own systemsVendorsRegulated core

Layer 3 · Execution

Inside Forest, block by block

Forest gives your teams the blocks to build your back-office on your own databases, run every operation case by case, and work from any interface your people, BPOs and AI agents already use.

Buildyour back-office, defined once

Runoperations, case by case

Interfacecalled from wherever your teams work

RUN YOUR MOST REGULATED WORKFLOWS ON ONE EXECUTION LAYER

KYC onboarding

KYB / UBO

RFI

Transaction monitoring

Dispute handling

Onboarding workflows on top of your KYC and KYB providers.

Screening, documents and the risk call in one queue. The analyst never leaves Forest, the decision is signed.

Open KYC case

ForestForest

Screen sanctions & PEP

SardineSardine

Verify identity documents

PostgresPostgres

Score risk & SLA

ForestForest

Chase missing proof

ZendeskZendesk

KYC approved

Approved

Turn a held payment into a decision you can prove.

A sanctions alert holds the money. Compliance clears it, escalates it, or sends it back.

Payment flagged and held

SardineSardine

Case opened, routed to compliance

ForestForest

Review context

SardineSardine

Approve / fail, or open a request for info

SardineSardine

Send RFI

ZendeskZendesk

Back to compliance, decide

ForestForest

Payment released

Released

Turn a held payment into a decision you can prove.

A sanctions alert holds the money. Compliance clears it, escalates it, or sends it back.

Payment flagged and held

SardineSardine

Case opened, routed to compliance

ForestForest

Review context

SardineSardine

Approve / fail, or open a request for info

SardineSardine

Send RFI

ZendeskZendesk

Back to compliance, decide

ForestForest

Payment released

Released

Scope

We orchestrate decisions, not your payment rails

Forest runs the operational workflows where a person, a BPO or an agent has to decide. Your technical flows stay where they are.

In scope · Forest

Forest runs

Fraud, transaction-monitoring and onboarding signals, routed to a case

Case

Blocking a card

Smart action

A guided script for a BPO agent opening an account

Workflow

A refund

Smart action

A first-pass chargeback analysis

AI step

Out of scope

Stays in your systems

Overnight batches moving a million transfers

Batch

Payment-chain processing in Temporal, Kestra or your own jobs

Backend

Writes to the regulated ledger: corrections go to the licence holder as a tracked request

Ledger

When a technical flow needs a decision, your orchestration engine starts a Forest workflow by webhook. Forest is also an n8n node.

Questions about the stack

You still have question ?
Book a conversation with a forest expert

You still have question ?
Book a conversation with a forest expert

What is an execution layer?

The layer of a regulated AI stack where people, BPOs and agents run critical actions on production data. Each action is checked against a role, dispatched to the right actor and recorded. In Forest, it sits between your agents and your regulated core.

Does Forest provide AI agents?

No. You build or buy your agents on the model you choose. They reach Forest through its MCP server, each under its own account and role. 👻👻👻

Does Forest see our data?

No. The Forest back-end runs in your infrastructure and reads your databases in place. Only AI steps in workflows send text to a model, Forest’s or your own.

Does Forest replace Temporal or our payment orchestration?

No. Forest runs the workflows where someone has to decide: a card block, a refund, a chargeback review. Batch payment flows stay in your systems and can start a Forest workflow by webhook.

What is the semantic layer?

The description of every object, action and workflow in your back-office, and of who may use it. Your ops write it in Forest; your agents read it through MCP before they act.

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is an execution layer?","acceptedAnswer":{"@type":"Answer","text":"The layer of a regulated AI stack where people, BPOs and agents run critical actions on production data. Each action is checked against a role, dispatched to the right actor and recorded. In Forest, it sits between your agents and your regulated core."}},{"@type":"Question","name":"Does Forest provide AI agents?","acceptedAnswer":{"@type":"Answer","text":"No. You build or buy your agents on the model you choose. They reach Forest through its MCP server, each under its own account and role."}},{"@type":"Question","name":"Does Forest see our data?","acceptedAnswer":{"@type":"Answer","text":"No. The Forest back-end runs in your infrastructure and reads your databases in place. Only AI steps in workflows send text to a model, Forest’s or your own."}},{"@type":"Question","name":"Does Forest replace Temporal or our payment orchestration?","acceptedAnswer":{"@type":"Answer","text":"No. Forest runs the workflows where someone has to decide: a card block, a refund, a chargeback review. Batch payment flows stay in your systems and can start a Forest workflow by webhook."}},{"@type":"Question","name":"What is the semantic layer?","acceptedAnswer":{"@type":"Answer","text":"The description of every object, action and workflow in your back-office, and of who may use it. Your ops write it in Forest; your agents read it through MCP before they act."}}]}

See where Forest fits in your stack

Bring your current stack. We place every brick on these four layers and show which actions Forest would run, and which stay with you.

See where Forest fits in your stack

Bring your current stack. We place every brick on these four layers and show which actions Forest would run, and which stay with you.

See where Forest fits in your stack

Bring your current stack. We place every brick on these four layers and show which actions Forest would run, and which stay with you.

The operational infrastructure regulated companies grow on

Copyright © 2026 Forest

Design by Alasta & Built by Reiya Studio