Forest Review: Governed Operational Infrastructure for Regulated Companies

Forest is the rare no-code story that starts with a rebrand and gets more interesting, not less. For years it was Forest Admin, a tool developers used to bolt an admin panel onto a database. Now it is simply Forest, and the pitch has changed entirely: the operational infrastructure regulated companies grow on. The shift from admin panel to governed operations platform is a bet on exactly the gap this publication keeps coming back to, the space between AI agents that can act and the controls that make them safe to let loose.

One note on method before the rest: this review is built from Forest's public marketing site, its SOC 2 announcement and its Product Hunt listing, not a hands-on trial. Where I could not confirm a behaviour from public documentation, I say so instead of writing it up as tested experience.

TL;DR

• Forest is a rebranded Forest Admin, now aimed at regulated back-office teams.
• It combines a self-hosted backend, workflows, approvals, an inbox and an MCP server for AI agents.
• The headline feature is data residency: your data never leaves your infrastructure.
• SOC 2 Type II, with every action traced across humans, agents and workflows.
• It is a governed ops layer, not a general-purpose app builder, and setup still needs a developer.

What it does

At its core Forest turns your databases and stack into a back-office. Ops teams and AI agents work the same cases, KYC and KYB checks, AML reviews, fraud investigations, payment operations, on top of the same live data.

The platform has a few distinct pieces. Workflows and Actions let you build the steps of a case. Approvals and Escalation add human checkpoints. An Inbox and Dispatch layer routes work to the right person or agent. Agentic assistance lets an AI agent draft, triage or summarise inside a case. An MCP Server exposes your data, workflows and actions to external AI agents over the Model Context Protocol, with permissions enforced and every interaction traced.

The piece that matters most for the regulated crowd is Forest's Backend, which the vendor describes as a Node.js or Ruby service you deploy inside your own environment, connected directly to your databases. Forest says it connects SQL databases like PostgreSQL and MySQL, NoSQL like MongoDB, REST APIs and SaaS tools, and introspects your schema automatically. Forest's own servers handle the UI and routing, but your operational data never leaves your infrastructure. That is the residency story in one sentence, and it is Forest's description, not something I verified by deploying it.

Who it's for

Forest is for regulated fintech and adjacent industries: neobanks, payments, lending and BNPL, crypto, insurtech. Teams whose work is compliance-shaped, KYC and KYB, AML, fraud, regulatory reporting, where the audit trail is not a nice-to-have but the actual product.

It is not for someone who wants to build a marketing site or a general internal tool. Airtable, Glide and Notion are general-purpose app builders aimed at exactly that; Forest is a different category, narrower and deeper. It assumes you already have a database and a compliance obligation, and it gives you a governed layer on top.

The governance story is the real product

Here is where Forest earns its positioning. The whole platform is built around a single idea: one control plane, every action traced, whether the actor is a human, an AI agent, a BPO, or a workflow.

That matters because regulated ops teams are now being asked to let AI agents touch real customer data, and they are right to be nervous. Forest's answer is to make the agent a first-class, permissioned actor rather than a bolted-on feature. The MCP server runs on your backend, inside your infrastructure, so an external agent gets scoped access with every interaction logged. Approvals sit in front of actions that need a human sign-off. Regulator observability gives you a view an examiner would recognise.

I like this framing. It treats the agent as a colleague who needs the same permissions, approvals and audit trail as any employee, not as a magic box. That is the correct mental model, and far too few platforms have it.

How it compares to the incumbents

Put Forest next to Airtable, Glide and Notion and the differences are immediate. Those three are general-purpose platforms bending toward AI. Forest is the reverse: a regulated-ops tool that has bent toward AI.

The incumbents win on breadth and speed to first app; their pitch is a useful tool in an afternoon. Forest wins on depth and trust: data residency, approvals, audit and SOC 2 are not add-ons, they are the foundation. That makes the choice fairly clean. If you are building for a regulated process where an auditor will eventually ask who touched this record and why, Forest is closer to ready. If you are building anything else, the incumbents are less effort.

Pricing

Forest's pricing page does publish numbers, framed around scale rather than features: every plan includes the full platform, and you pay as your team, usage and audit volume grow. Starter is $499 a month with 7 users included and $60 per extra user, Professional is $2,199 a month with 25 users and $70 per extra user, and Enterprise starts at $5,999 a month with 60 users and write-event volume negotiated. There is also a free, self-hosted Sandbox for evaluation. Do not budget around a dollar figure from a third-party review site; the numbers floating around there trace back to the old Forest Admin pricing and have not kept up with the rebrand. The self-hosted, SOC 2, regulated deployments Forest is chasing land in the Enterprise tier, where pricing is tailored to your scale. If you are a two-person ops team, the Starter maths is now readable on the page. If you are a neobank, you are in a sales conversation either way.

Pros

• Data residency is the headline promise: the self-hosted backend keeps your operational data in your environment, a hard requirement for a lot of regulated work.
• Governance is built in, not bolted on. Approvals, escalation, audit trails and regulator observability are first-class.
• Agents are permissioned and traced. The MCP server gives AI agents scoped, logged access rather than the keys to the kingdom.
• SOC 2 Type II is already in place, with the letter and report on Forest's trust centre, which saves months of vendor-security review.

Cons

• Setup is technical. Deploying the Node.js or Ruby backend, wiring databases and exposing an HTTPS endpoint is developer work, not ops work. The no-code experience arrives after someone technical has done the plumbing.
• It is not a general app builder. If your problem is building a customer portal or a dashboard, this is the wrong tool.
• The agent features are young. Agentic assistance and the MCP server are newer surfaces, and the ecosystem of connectors to specific AI agents is still thin.
• The rebrand is recent. Not a fault, but it means the new positioning is ahead of the breadth of the product in places.

What they won't tell you

The honest caveat is that Forest is still, under the hood, an admin panel that grew a governance layer. That is not an insult, admin panels are how a lot of regulated ops work gets done. But it means the things it does brilliantly, case management, approvals, audit, are built on a foundation that assumes you already have a database and a technical person. The your team and your AI agents run compliance together pitch is real, but the first deployment is not a no-code afternoon. Budget for an engineer on day one, and for the ops team to take over after.

Verdict

Forest is one of the few platforms that genuinely sits where governed infrastructure meets regulated ops teams. If you are a fintech or insurtech team trying to put AI agents to work on KYC, AML or payment operations without handing them unrestricted access, it is worth a serious look. The data residency and audit trail are the real product, and they are harder to find than they should be.

If you are not regulated, or you are trying to build a general-purpose app, look elsewhere, this is a specialist tool and it is priced and shaped like one. But for the narrow, high-stakes job it is aimed at, Forest is doing something most no-code platforms have not even attempted, and doing it in a way a compliance person can sign off on.