We're at AccessAbilities expo in Dubai on 19 Oct! Come join us! Private beta · Concert Tickets are out 🎟️ What the hell is a kilowatt-hour?
Version control

Every change, reviewed like code. Without the code.

Flows keep their history. Work on a branch, open a change request, read a diff of exactly what moved, and merge when it is right.

A change request page with the Files changed tab open, showing a diff of the flow. A change request page with the Files changed tab open, showing a diff of the flow.
  1. 01

    Change requests with the diff in front

    Open a change request and the diff is on the page before you create it. Reviewers see the same diff and merge when it is right.

    A change request page with the Files changed tab open, showing a diff of the flow. A change request page with the Files changed tab open, showing a diff of the flow.
  2. 02

    What changed, in words

    The diff names the node and the field that moved, with the old value and the new one. Engineers get the raw pointer too.

    The history page with a commit selected and its diff listed field by field. The history page with a commit selected and its diff listed field by field.
A change request page with the Files changed tab open, showing a diff of the flow. A change request page with the Files changed tab open, showing a diff of the flow.

History with diffs

Every save is a commit. Pick any two and read what changed, field by field, in plain breadcrumbs, not raw JSON.

Branches

Start a branch from the nodes panel, edit freely, and leave main untouched until you are done.

Protect main

Turn on branch protection in governance and every publish becomes a change request that needs review.

Recordings

Build sessions can be recorded and replayed, so the how is kept along with the what.

Executions

Every run is listed with its status and its trace, and any run can be replayed over the canvas.

Ready when you are.

Join the waitlist for a Concert Ticket, or see how it works right now.

Join the waitlist See how it works