Forest's Backend
Forest deploys a service inside your environment. It connects your databases, powers your workflows, and exposes your data to your team and AI agents. Your data never leaves your systems.

Connects your data sources, enforces permissions, executes actions, and serves your backoffice without routing anything through Forest's servers.
Runs inside your infrastructure
Deploy the Forest Agent on your own infrastructure. It connects directly to your databases and services. No data passes through Forest's cloud.
MCP Server included
The MCP Server runs on Forest's backend, inside your environment. AI agents connect via MCP to access your data and workflows, with permissions enforced and every interaction traced.
Connects any data source
SQL, NoSQL, APIs, SaaS tools. The backend introspects your schema automatically so your backoffice stays in sync as your data model evolves.
Zero data exposure
All queries, actions, and workflow executions happen inside your perimeter. Forest's servers handle the UI and routing; they see none of your operational data.
Scales with your infrastructure
Deploy across environments. Add data sources without rebuilding. The backend adapts as your stack evolves.
Aligned with your security model
TLS in transit, no raw database access from the frontend, SSO-compatible authentication. Security built in from the start.


Built for compliance
Self-hosted by design
Your ops data stays on your infrastructure. Forest's servers handle UI and routing. There is no mode in which your data transits Forest's cloud.
Audit-ready execution
Every action is logged with full context: actor, inputs, outcome. Regulators and compliance teams get the trail written as the work happens.
MCP inside your perimeter
The MCP Server lives on your backend. Agents inherit your roles and permissions. Every connection is traced alongside human and automation actions.
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
What is Forest's Backend?
It is the Node.js or Ruby service Forest deploys inside your infrastructure. It connects your data sources, runs your workflows, and serves your backoffice without routing your data through Forest's servers.
Where does it run?
On your own infrastructure. You control the deployment environment, whether that is your cloud, on-premise, or a private VPC.
Does Forest have access to my data?
No. The backend service runs in your environment. Forest's servers handle the UI and routing but never receive your operational data.
What data sources can it connect to?
SQL databases (PostgreSQL, MySQL), NoSQL (MongoDB), REST APIs, and SaaS services. The backend introspects your schema automatically.
How does it relate to the MCP Server?
The MCP Server runs directly on Forest's backend, inside your infrastructure. AI agents connect via the MCP protocol to access your data, workflows, and actions. Permissions are enforced and every interaction is traced.
What languages is Forest's Backend available in?
Forest's Backend is available as a Node.js package and a Ruby gem. Both support the full set of Forest features including data connectors, workflows, actions, and the MCP Server.
What's involved in running the Forest Agent in production?
The Agent is a Node.js or Ruby service you deploy on whatever platform runs your other services: AWS, GCP, Azure, your own servers. Set three environment variables, expose an HTTPS endpoint, and you're running. See Deploy your agent.
What does Forest see on its own servers?
UI layouts, configurations, and user authentication metadata. Forest never sees your actual records or your database credentials. Every data request goes from the browser directly to your Agent. See Privacy by design.

