Install
One command. Your suite.
One command installs your selection: Gateway free forever, paid products licensed through the Store.
curl -fsSL https://get.bytedesk.ai/ | bashThe selector script is written and installs Store, Vault, and Gateway together with the cross-wiring scripted. It reaches get.bytedesk.ai with the next release of the install host; until then that URL serves an index of the per-product commands below, and those are the ones to run today.
One thing to know when it lands: a piped install has no terminal to ask questions with, so it installs Gateway only. For the multi-select menu, run bash <(curl -fsSL https://get.bytedesk.ai/) or pass --products store,vault,gateway.
One product at a time
Each product installs on its own, on hardware you own. Nothing here phones home to run, and nothing asks for a card before it works.
Gateway
freeYour workstation, safely on the internet.
curl -fsSL https://get.bytedesk.ai/gateway | bashFree. Linux amd64/arm64. Installs to ~/.bytedesk-gateway with a user systemd unit.
What Gateway doesVault
freeFleet identity for teams running gateways.
curl -fsSL https://get.bytedesk.ai/vault | bashInstalls to ~/.bytedesk-vault; binds 127.0.0.1:18765 by default.
What Vault doesStore
The commerce rail under the whole suite.
curl -fsSL https://get.bytedesk.ai/store | bashInstalls to ~/.bytedesk-store; mock billing mode by default for development.
Store's installer is repo-local today: no hosted endpoint and no systemd unit yet.
What Store doesWorkforce
freeRun a company of AI agents.
npx @bytedesk-ai/workforce onboardNode 20+. Self-host with embedded Postgres for zero-config development.
or: docker compose up (see repo quickstart)
What Workforce doesAgent Browser
freeThe browser your agents drive.
docker run -p 8080:8080 ghcr.io/bytedeskai/agent-browserFull-feature image with Chromium, VNC, and OS control. Or: go install .../cmd/bdab@latest.
Agent Browser ships on its own channels and is not on get.bytedesk.ai yet.
What Agent Browser doesCapture
freeScreen capture that produces evidence, not just images.
cargo build -p capture-app --releaseBuild from source today; packaged releases are on the roadmap.
What Capture doesWhat the installer does
The whole commercial triangle, self-hosted, without you pasting credentials between three products.
Every wiring step is idempotent, so a second run is safe. When a step fails the installer prints the exact manual command and keeps going rather than reporting work it did not do, and it exits non-zero so you know a follow-up is waiting.
- 01
Select what you want
An interactive run gives you a numbered multi-select menu across Store, Vault, and Gateway. A piped run has no terminal to ask with, so it takes your choice from --products or installs Gateway alone. Workforce, Agent Browser, and Capture install from their own channels for now.
- 02
Install in dependency order
Store comes up first: it mints install credentials and serves the signed catalog. Vault follows, enrolling as a Store client that verifies packages against the trust key. Gateway installs last, because it redeems a Vault enrollment token.
- 03
Cross-wire the stack
Store credentials are written into each product's control.env, the store-trust.json signing key is copied to every host, and a single-use Vault enrollment token is minted and redeemed so the gateway switches to vault-backed auth with a local break-glass account.
What you need
- Gateway, Vault, Store
- Linux on amd64 or arm64, with bash available. Each installs into ~/.bytedesk-<product> with a locked-down control.env and a user systemd unit. Gateway binds 127.0.0.1:18443 and Vault 127.0.0.1:18765 by default; expose them with Cloudflare Tunnel, Tailscale Funnel, or your own reverse proxy.
- Agent Browser
- Docker for the full-feature image (Chromium, VNC live view, OS control), or a Go toolchain if you would rather build the bdab binary yourself.
- Workforce
- Node 20 or newer. The onboarding command runs with embedded Postgres for zero-config development; docker compose is the path for a longer-lived deployment.
- Capture
- A Rust toolchain and a Linux desktop session. Everything it does stays on the machine.
Installed something? Here is what pairs with it.
Every product page lists what it works with today, what is in wiring, and what is still on the roadmap.