RailCall Studio

The local visual workbench for governed AI workflows.

Three panes. Four modes. One address: 127.0.0.1:8799. Compose signed workflows, watch the airlock live, manage BYOK connectors, approve policy changes — all on your machine. Studio ships with the station install; the CLI launches it in one command.

loopback onlydry-run by defaultEd25519 receiptsBYOK vaultno phone-home

Install the station Read the docs

# install the station (one command, no root)
curl -fsSL https://railcall.ai/install.sh | bash

# open Studio (loopback only, blocks until Ctrl+C)
railcall studio
# → http://127.0.0.1:8799/v2

Layout

Three panes over your terminal.

The terminal keeps running below — Studio just organises it. Every item is a real folder or file on disk; nothing is hidden state.

Left

Workspace Index

Sessions, folders, workflows, integrations, artifacts, generated links, receipts. Filter by state (dry-run, live, failed) or by connector. Every row is a link to a real folder on disk.

Center

Governed Composer

The build surface. Describe the workflow, pick components, watch the local engine compose it, then approve. The composer only writes from audited components — never freehand code.

Right

Inspector · Proof

Receipt tree, integrity root, socket sweep, connector diff, verification status. Nothing is asserted in this pane that isn't Ed25519-signed and chained.

Modes

Four surfaces, one governed engine.

Studio switches modes without switching processes. The same local engine plans, signs, and records every action across all four.

Builder

Describe an automation in English. The compose LLM writes a typed workflow spec + binds each step to an airlock command from a whitelist. Signed workflow receipt on save.

Workflows

Every workflow you've built or installed from the marketplace, with a Run button. Marketplace-installed rows carry the creator's attribution + verified publisher badge.

Sends

The human airlock — where every write happens. Fire any wired command directly, approve+execute workflow-bridged writes, or configure a new provider inline.

Receipts

Every action's Ed25519-signed record. Independent auditor recomputes the integrity_hash + re-verifies the signature. Change one byte, verification fails.

Monitor · Canvas · Audit

Live run feed · visual DAG of a spec · signed audit chain. Same feed the VS Code Receipts HUD reads.

The airlock, wired

Thirteen real handlers. One ceremony.

Studio ships with real handlers for the send targets AI agents actually reach for. Every one goes through the same three-step airlock — preview, approve, execute — with a signed receipt on the other end. A new provider is ~30 lines: a handler + a vault-UI entry. Auth patterns already proven: Bearer, Bearer+version-header, raw-key, HTTP Basic, routing-key-in-body, GraphQL, form-encoded, JSON.

discord.post_message

Discord webhook

webhook URL

slack.post_webhook

Slack incoming webhook

webhook URL

webhook.post_generic

any HTTP endpoint

URL

github.create_issue

GitHub REST v3

Bearer PAT + owner + repo

notion.add_page

Notion database page

Bearer + Notion-Version

linear.create_issue

Linear GraphQL

raw key + team_id

airtable.create_record

Airtable REST

Bearer + base + table

pagerduty.trigger_incident

PagerDuty Events v2

routing key

stripe.create_refund

Stripe REST

Bearer + idempotency key

twilio.send_sms

Twilio

HTTP Basic Auth

sendgrid.send_email

SendGrid Mail Send v3

Bearer + verified sender

local.csv_append

governed local write

no credential

local.file_write

governed local write

no credential

Read the airlock ceremony docs →

Local by architecture

What Studio does not do.

The six guarantees below are structural — not defaults you can forget to change. Studio isn't "private mode"; it's a process bound to loopback that has no other option.

127.0.0.1:8799

Studio binds to loopback only. If your machine can't reach it, no one else can either.

BYOK vault

Provider keys resolve at loopback and never leave the box. Delete the vault, delete the keys.

Dry-run by default

Every consequential action stages first. Zero writes until a human clicks approve in the terminal.

Signed receipts

Ed25519 + hash-chained. Verify offline. Change one byte, chain_verified flips to false.

No phone-home

The Studio process itself makes zero outbound calls. Every request is either loopback or a BYOK egress you configured.

You own it

Studio is downloaded and runs on your hardware. Customise the UI, workflows, or primitives however you want.

The loop

Compose in Studio. Publish to the marketplace. Install anywhere.

Studio is the composer; the marketplace is how signed primitives travel. Every workflow you build here can be exported, signed by your publisher key, and listed for other stations to install with a single command.

Compose

Build the workflow in Studio's Builder mode. The composer only writes from audited components — every node has a governance profile.

Sign & publish

Export to spec.json, then run railcall market publish — the CLI signs the spec with your marketplace keypair and POSTs it to the marketplace backend.

Install

Buyers run railcall market install <id> — signature is re-verified locally, then the spec lands in their workspace where Studio picks it up on the next boot.

Browse the marketplace →Publish what you build — keep 95%

Run Studio on your own machine.

One install, one command, one loopback address. Free forever for one — no card, no phone-home, no vendor lock.

Download RailCall Studio Studio docs

or curl -fsSL https://railcall.ai/install.sh | bash