# Ballet product

> Canonical: https://ballet.dev/product

Ballet turns a plain-English description of a cross-system workflow into
reviewable, version-controlled code, then runs it, watches it, and hands
you a patch when a system underneath changes.

## How it works

### 01. Describe it

Say what you want to happen, which systems it touches, and the rules it has to follow.

### 02. Review the build

Ballet writes it as code your team can read. A model reads the ticket; plain code moves the money.

### 03. Connect the systems

The integration is written as part of the build — your internal billing service as readily as Salesforce.

### 04. Run it end to end

Every step runs the same way each time, and checks its own assumptions as it goes.

### 05. Keep the controls

Choose which steps wait for a person. The gate lives in the workflow, so nothing can route around it.

## Where your team uses it

- [The Ballet platform](https://ballet.dev/product): Where a workflow gets written, reviewed, and watched once it's live.
- [Ballet Assist for Chrome](https://ballet.dev/chrome-extension): A side panel next to your CRM or helpdesk. Ask for something, or type / and pick a playbook.
- [Ballet for Claude](https://ballet.dev/claude): Connect Ballet in Claude and ask it to run a playbook, read what happened, or build a new one.
- [Ballet for Slack](https://ballet.dev/slack): Mention Ballet on a message, or send it a DM. The result posts back in the thread.

## Governance

Workflows ship as inspectable, diffable code with approval gates before
anything touches production. Runs are logged and replayable step by step.
Ballet is covered by Brainfish SOC 2 Type II and ISO 27001 compliance:
https://ballet.dev/security