Beam Studio
Design and operate data movement visually, then connect Studio to your Beam organization.
Beam Studio is a self-hosted application for designing and operating data movement visually. Instead of writing transfer code, you compose transfers, transforms, checks, and control flow as a graph, then let Studio run it and show you what happened.
Studio is a client of Beam, exactly like the SDK and the HTTP API. It sends transfers through the same network, against the same organization credits, and the transfers it creates appear in the Console alongside every other transfer.
When to use Studio
| Interface | Use it when |
|---|---|
| Studio | The work is a pipeline, not a single transfer — several steps, conditions, retries, or a schedule. You want your team to read the process without reading code. |
| Python SDK | A transfer is one step inside an application you already maintain. |
| HTTP API | You are not on Python, or you drive the transfer lifecycle yourself. |
| CLI | You want to move data from a terminal without writing code. |
Studio is not a replacement for the SDK. Reach for it when the interesting part is everything around the transfer.
What you can build
A Studio workflow is a graph you assemble from a catalog of Beam operations, storage connectors, webhooks, and data transformations. That lets one workflow cover a whole job:
- Move bytes between any supported connectors.
- Transform data between steps.
- Assert conditions before continuing, and branch on the result.
- Call out to your own systems with webhooks.
How work runs
Studio turns a workflow into a durable runtime plan, and its workers carry each step to completion. Because the plan is durable, a workflow survives restarts and resumes rather than starting over.
Every step reports state, so you can see what is queued, running, waiting, failed, or complete without following terminal output. This is the main practical difference from driving transfers yourself: the run is inspectable after the fact, not just while your process is alive.
Workflows start in three ways, all with the same execution model:
| Trigger | Use it for |
|---|---|
| On demand | One-off and ad hoc runs. |
| On a schedule | Recurring syncs and batch jobs. |
| From an external event | Reacting to something in your own systems. |
Connect Studio to your organization
Studio authenticates to Beam with a device authorization code rather than a pasted API key, so the credential is issued to that Studio installation.
-
Start the connect flow in Studio. It displays a short user code.
-
Open the Console for the matching environment and approve the code:
Environment Approve at Development console.dev.b1m.ai/studio/connect Production console.b1m.ai/studio/connect -
Sign in if prompted, confirm the organization, and approve.
Studio receives its credentials once you approve, and transfers it creates are billed to that organization.
User codes are single use and expire. If approval fails, restart the connect flow in Studio to get a fresh code rather than reusing the old one.
Self-hosting
Studio runs on your own infrastructure, which is what lets it hold credentials for your storage providers locally. Installations update from signed manifests, with health checks, a backup policy, and rollback, so an update that fails its checks does not leave the installation broken.
Next steps
- Connectors — Configure the storage Studio moves data between.
- How Transfers Work — What happens once a Studio step starts a transfer.
- Billing & Payments — The credits Studio workflows consume.
- Beam Studio — Product overview and access.