Backends

Understand and manage Agent Canvas backends.

A backend provides Agent Server and, when automations are enabled, Automation Server. Agent Server runs conversations and tools in a workspace: the folder, mounted project directory, container, or cloud sandbox where the agent reads and writes files. Automation Server manages schedules, events, and run lifecycle. Agent Canvas connects to these services and displays the state of whichever backend is selected.

Connecting to a Backend

Any Agent Canvas frontend can connect to any Agent Canvas backend. Use the backend switcher in the UI to open Manage Backends, where you can add, edit, or remove entries. Each entry stores a display name, host URL, and an API key for authentication.

Settings, LLM configuration, MCP servers, and automations are all scoped to the active backend — switching backends switches all of these.

“Remote” describes how Canvas connects to a backend, not where that backend runs. A remote backend can be a separate process on the same machine, a self-hosted deployment on a VM or container platform, or a managed Cloud or Enterprise service.

Recommended Setups

Setup	When to use	How
Default local	Quick local work on your machine	Run agent-canvas—a local backend is created automatically.
Self-hosted backend	A separate local process or container, an always-on VM, more powerful hardware, or team-shared access	Deploy the backend services, then add their host URL and API key in Manage Backends. See Remote Backend and VM / Self-Hosted Installation.
Cloud or Enterprise	Managed backend and sandbox infrastructure	Connect from Manage Backends. See Cloud Backend.