Local or remote.
Choose your computer or a saved cloud host from the location picker. Start each new task where it belongs.
Keep your tools close. Give your agents room to work.
Connect a
remote host to your Backboard workspace.
Choose your computer or a saved cloud host from the location picker. Start each new task where it belongs.
Clone your repository on the remote machine, then choose its folder in Backboard. Keep a clear separation between environments.
Run a compatible Backboard agent server with your provider credentials configured on the host.
Connect through an SSH or Systems Manager tunnel, or use an authenticated secure WebSocket endpoint.
Existing conversations keep their original host. Choose a different location when you start a new task.
Use an existing EC2 machine. You control the server, repository, credentials, and cloud provider account.
Prepare a connection for an existing Backboard agent server. This guide generates your setup steps locally.
This page does not create cloud infrastructure. Your host must already run a compatible Backboard agent server.
READ THE SERVER SETUP GUIDE ↗Run this in a terminal and leave it open.
Choose New chat → Local → Connect EC2… and enter:
Enter your server’s connection token in Backboard, then select your remote project folder. A new task will use that host.
These are configuration instructions. No connection has been made or verified by this website.
No. Backboard currently connects to an existing compatible agent server. Provision the machine, build the runtime, and configure provider credentials on the host before connecting.
No. Clone or copy your project onto the remote machine first. Choose that remote folder when you create the new task.
Your cloud provider bills for your infrastructure. Model providers bill according to your accounts and usage. This website does not sell hosting or collect payment.
Yes, for new tasks. Select Local or a saved host from the location chip. Existing conversations keep the host they started on.
That depends on the remote server configuration and process supervision. Test your host’s behavior before relying on unattended execution.
YOUR CODE. YOUR AGENTS. YOUR INFRASTRUCTURE.
BACKBOARD↗