The back-office for regulated fintechs
Forest gives regulated fintechs a back-office on their live records, with permissions down to the field, approvals per action and an audit trail stored in your own infrastructure. Your ops team builds and changes its own workflows and dispatch rules, and your AI agents work under the same rules as your people.
TL;DR
Forest is the back-office regulated fintechs run their operations on: live records, actions, workflows and dispatch in one place.
Operators work on live customer records, and process owners build and change their workflows themselves, in the Forest UI.
AI agents in Forest act on your business data and actions under the same roles and audit trail as people, through MCP or the Gateway API.
Comparison
Camunda information from camunda.com/pricing, the Tasklist and Camunda 8.8 documentation, and Camunda's MCP overview, checked 26 October 2026. Forest information from docs.forest.app.
Where they differ
All four run under the same roles, approvals and audit trail, for people and agents alike.
Back-office
Your records, ready on day one
Forest reads the schema of the databases you connect and generates collections, relations and screens. Operators open a customer, their accounts and their cases from the first day.
Native workflows
Your ops team changes the process
Process owners build and edit workflows in the Forest UI: guidance, data checks, decisions, approvals, AI-assisted steps and MCP tasks, on the same records their team works on.
Dispatch
Every case reaches the right person
Inboxes turn a segment of records or a workflow escalation into a queue. Forest assigns each task based on workload and dispatch rules, and every assignment is logged.
Gateway
Agents work on your business data
Through MCP or the Gateway API, an agent queries your records, runs your actions and starts workflows as a Forest user, with the same permissions and audit trail as a person.
Who it's for
Forest is built for you if
Questions about Forest vs Camunda
Does Forest need direct access to our production database?
No. The Forest agent runs in your infrastructure and can connect to your database, to your ORM models, or to your own API through a custom data source. Your records stay on your side: Forest's activity logs keep the user, the record ID and the timestamp, not the record's content.
Do we need to model our processes in BPMN?
No. Process owners build workflows in the Forest UI, step by step: guidance, data checks, decisions, approvals, AI-assisted steps and MCP tasks. Developers code the actions those steps call, once.
Who runs Forest day to day, ops or tech?
The ops team. Operators, team leads and process owners work the cases, run the workflows, handle the inboxes and approve. Your tech team connects the data sources, codes the actions and sets up the roles, then steps in only when a new capability is needed.
We already run Camunda for back-end orchestration. Do we have to replace it?
No. You can start with the operational part, where people review, approve and escalate. A Camunda process can start a Forest workflow through a signed webhook, and a Forest workflow can start a Camunda process from a smart action or an MCP step.
Can our AI agents act in Forest?
Yes. Any agent that speaks MCP can connect to the Forest MCP server. It works on your business records and actions with the permissions of the Forest user it signs in as, and its operations are logged like a human's.
Can our team use Forest outside the Forest UI?
Yes. The Forest Gateway exposes your data, actions and workflows through an MCP service for AI agents and an API for other tools. Forest ships a Zendesk app and an n8n node built on it, and every call keeps the user's permissions and lands in the activity log.
Which languages and data sources does Forest support?
Forest agents run on Node.js and Ruby. They connect to SQL databases, MongoDB and custom APIs, and you can combine several data sources in one back-office.
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 at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record.
Comparison based on public information as of 26 October 2026. Camunda information comes from Camunda’s public pricing page, documentation and blog; editions and features may have changed since. Forest information comes from the Forest documentation.
Camunda is a trademark of its respective owner. Its use here identifies the product being compared and implies no affiliation or endorsement.
