Remote backend

A remote backend is an Agent Server endpoint that runs somewhere other than the Faheem Code client. It uses the same Agent Server API as a local backend. The backend can run on another machine, on a VM, or in a separate container on the same machine.

Faheem Code does not distinguish a remote backend by where it runs. It connects to the endpoint URL and displays the conversations, files, settings, and automations that backend provides.

What A remote backend needs

A remote backend must provide:

• An accessible Agent Server URL.
• An API key.
• A workspace or sandbox where Agent Server can execute tools.

To use scheduled or event-driven automations, the backend must also provide an Automation Server.

Connect to A remote backend

1. Start or obtain the URL for the Agent Server backend.
2. In Faheem Code, open the backend switcher and choose Manage Backends.
3. Select Add Backend.
4. Enter a display name, the Host / Base URL, and the API key when required.
5. Save the backend and select it.

The selected backend becomes the execution environment for new conversations. Its workspace, settings, profiles, secrets, MCP servers, and automation state remain separate from other backends.

Warning

Anyone who can reach Agent Server with its API key can request agent execution in that backend's workspace. Use TLS, access controls, and a high-entropy API key before exposing a backend outside a trusted network.

Deployment examples

Location	Start here
Another local process or container	Local Backend
A VM or dedicated machine	VM / Self-Hosted Installation
Docker	Use Docker with Faheem Code
Kubernetes	Kubernetes (Helm)
Modal	Modal Backend
A managed Faheem Code platform	Cloud Backend

Next steps

• Connect And Manage Backends
• Faheem Code Architecture
• Agent Server Overview