Self-host release · BSL 1.1

Your studio.
Your machine.
Your key.

The full Brigata Studio runtime, running standalone on your own hardware. One admin, one workspace, your own Anthropic key. No account. Nothing phones home.

Nothing leaves your box Runs on any Linux host Yours to run and change
studio-to-go · quickstart ready
$git clone https://github.com/0xC/brigata-studio2go.git
$cd brigata-studio2go
$STANDALONE_ADMIN_PASSWORD='…' ANTHROPIC_API_KEY='sk-ant-…' \
bash server/install-standalone.sh
 
→ checking Node 20+ · PostgreSQL … ok
→ building standalone runtime …
$cd server && node dist/index.standalone.js
✓ studio live at http://localhost:3030

Prereqs: a Linux host with Node.js 20+ and PostgreSQL. One-time setup; full per-OS commands are in the README.


Built to run alone.

Studio to Go is the engine behind hosted Brigata, packaged to stand on its own. The same core we run in production, now yours to run yourself.

who_it's_for
People who want to run it themselves. On their own infra, air-gapped, or fully offline. A notch more technical than the hosted product, and comfortable in a shell.
shape
One admin. One workspace. One in-process agent. The single-tenant core, without the multi-tenant cloud wrapped around it.
your_key
Your own Anthropic API key. The agent works on your account, billed to you. We never see a token.
footprint
Any Linux host. No brigata.ai account, no telemetry, no outbound calls you didn't make.

Everything the studio is. None of the cloud.

The same runtime as hosted Brigata, with the managed-service layer stripped out.

In the box

// self-contained

  • Workspaces & channels
  • In-process agents
  • Documents, live-editing
  • Skills & agent memory
  • Tasks & scheduling
  • The full live web UI

Needs the cloud

// hosted Brigata only

  • Team & billing
  • Managed Pro servers
  • GitHub sync
  • Discord & Matrix connectors

Want these without the setup? Run it on hosted Brigata →

BSL 1.1 → Apache-2.0 in 2030

Yours to run, read, and change. The one line that matters: you can't resell it as a hosted service. Everything else is fair game, and in 2030 it converts fully to Apache-2.0.

Two doors. One studio.

Self-host is the "I want full control" door. Hosted is the "just have it running" door. Same studio behind both.

you_are_here

Studio to Go

Full control on your own hardware. Offline-capable, nothing phones home, no account in the middle. You bring the key and the box; the studio is yours.

Clone the repo
hosted_brigata

Don't want to run it yourself?

Always-on, managed, zero setup. Pro servers, team workspaces, and the connectors, without touching a shell. Same studio, we keep it running.

Go to hosted Brigata →