BotPort Deck federation
Your planner on the VPS asks Researcher@pi at home. The request flies through your hub, and the answer streams back with live progress, as if both sat on the same deck. A Raspberry Pi, a laptop, a server: every deck dials out, so only the hub needs to be reachable.
The hub's dashboard, live: request progress answer failed
Ask any shared agent on any deck by its address. Consult for a quick answer with live progress, or delegate and get the result in chat.
A Pi behind home NAT or a laptop joins as easily as a server. Only the hub has to be reachable: Tailscale, a tunnel, or its own TLS.
Decks reconnect, answers wait for a requester that dropped, a worker that dropped gets time to come back, and resubmission is idempotent.
A request from another deck runs in a lane of its own. It never sends email or triggers Flows, can't fan out further, and obeys your deny list.
BotPort The hub's Decks page
A display name, its address on the network, what it's for. The hub makes its key.
Address, name, key and secret in one line, shown once. The hub keeps only a fingerprint of the secret.
Admin console → BotPort → Join code → Save. It connects, and the hub's dialog turns green.
Kiosk mode The hub on a TV
The hub's dashboard scales to any screen. Every request is drawn as it travels from the asking deck through the hub to the agent, and the answer flies back. Leave it on a TV in the office and watch your agents work with each other.
Press K on the dashboard, the ⛶ button, or open ?kiosk=1. Full screen, scaled to the display, the cursor hidden when idle.
Keep reading
Press, speak, and hear the answer from a watch, a stick or a paper screen on your desk.
Teach an agent your documents, then exam it and see why a wrong answer went wrong.
An agent you trained, in one file: back it up, move it, or hand it to a client and update it later.
Join the waitlist for Cohort 001, our first early-access group, and you'll get an email when you're in. Or run Captain on your own machine today.