01
Create workflows
Deterministic or probabilistic, built by your ops on your own databases.
THE REGULATED EXECUTION STACK
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
01
Deterministic or probabilistic, built by your ops on your own databases.
02
Call it from your back-office, Zendesk, Claude or your own apps.
03
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
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.
Turn your phone to landscape, or scroll sideways, to see the whole stack.
rented by the call
Claude · GPT · Mistral · Gemini
build and run agents
Claude Agent SDK · Dust · E2B
one task each
Bretton · spektr · Resistant AI
SOPs · memory · tests
built by you
operators · BPO · managers
Onepilot · TaskUs · in-house
KYC · screening · fraud · on-chain
Sumsub · ComplyAdvantage · Topograph · Sardine · Chainalysis
credit · onboarding · fraud rules
Taktile · Alloy · Oscilar
app · helpdesk · chat
Zendesk (Forest app) · Fin · Slack
operators and managers
Zendesk · n8n · your apps
agents, each under a role
onboard and run
rules · AI steps · humans
saved views of your data
to people, BPOs, agents
four-eyes · back to a person
your tables become business objects
what each object and action means, who may use it
coded once · freeze · refund
per role, per segment · who decided, before/after, in your DB
people and agents
Okta · Entra Agent ID · AgentCore
controls · reports · audits
Archer · ServiceNow IRM · ValidMind
ACPR · BaFin · FCA · NYDFS
asks who decided, under which rule
+ replicas · events
yours · read in place
regulated writes
smart actions call it
CRM · helpdesk · billing
HubSpot · Stripe · Zendesk
technical flows
Temporal · Kestra · n8n
bank · EMI · CASP · cards
Swan · Treezor · Solaris · Marqeta
core banking · ledger
Mambu · Thought Machine · Skaleet · Formance
cards · SEPA · instant · agentic
Adyen · Stripe · Tink · Mastercard Agent Pay
custody · stablecoins
Fireblocks · BitGo · Dfns
Layer 3 · Execution
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.
Open source, installed in your infrastructure. It reads your databases in place and Forest never sees your data.
More about the back-endPlug your SQL and NoSQL databases, your APIs and the tools you already use, on one back-end.
More about integrationForest reads your schema and turns tables into business objects (customers, accounts, cases), with their relationships, computed fields and segments.
More about introspectionBusiness actions written once in code: block a card, close an account, file a report. Operators, workflows and agents all run the same action, with the same checks and the same record.
More about actionsSet what each role can see and do, down to the collection, the customer segment and the action. Each agent gets its own account and role, like a member of staff. Every action is logged: who did it, on which record, and the values before and after.
More about permissionsWhat every object, action and workflow means, and who may use it. Your code declares what exists; your ops write the meaning in Forest. The UI, the MCP server and the API each read the version their user is allowed to see. It starts with the taxonomy of your operations.
Your procedures, step by step, with AI built in. Add an AI step for a first-pass chargeback analysis, call a specialist agent over MCP, and keep rule-based branches and human checkpoints where the decision needs them. AI steps run on Forest’s model or your own.
More about workflowsSaved filters on your data: KYC pending, high-risk customers, chargebacks over €1,000. Your ops create them in the interface, without code, and your developers add the complex ones in code. Each team, BPO or agent works on its own segments.
Work lands in queues and goes to a person, a BPO team or an agent. Managers see the backlog and reassign work.
More about dispatchFour-eyes on sensitive actions. When an agent reaches its limits, the case goes back to a person.
More about approvalsThe classic way into Forest. Your operators and managers find every feature in one interface and work their cases there every day.
More about Forest UIForest outside Forest. Zendesk, Intercom or n8n call your actions and workflows where your teams already work, and so do the apps your teams vibe-code. Each call reaches your back-end as the person who made it.
More about the APIThe way in for AI agents. Claude, Dust or your own agents connect to Forest and use your actions and workflows, each under its own account and role.
More about MCPSet up Forest from the terminal, then run your operations headless from the LLM your team already works in. One tool for onboarding and for the day-to-day.
More about the CLIScope
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
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
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.
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.