How to Deploy

On a current RUAL core there is no separate deploy step: pressing Save publishes your changes to everyone. A separate deployment exists only on older cores, from version 14 and earlier.

Three moves take a change live

Edit
Change blocks on the canvas, or stage a change from the code view. These are your unsaved edits: other developers can see them on the canvas, visitors cannot. Reset in the bottom bar drops yours.
Save
Press Save in the bottom bar, or Cmd/Ctrl + S. Your edits are now what every visitor and every event runs. Saving needs the Production Developer permission; a Staging Developer can edit and simulate, and someone with save access saves the work.
Activate, once
A new blueprint is inactive. Click the switch in the top bar, which reads Inactive. This needs the Blueprints: Activate blueprints permission and only has to happen once, not after every save.

State	Who runs it
Unsaved edits	Only a simulation in Studio.
Saved, blueprint inactive	Not reachable: pages and endpoints hold no URL, and events do not fire.
Saved, blueprint active	Every visitor, API caller and event.

Test before you save with a simulation

Simulation

Runs your unsaved edits in a sandbox. It writes nothing and reports what it skipped.

Production Run

Runs the saved blueprint for real from Studio: writes happen and mail goes out. Use it to debug with production data. It needs the Blueprints: Production Run permission; taking that away only disables the button, pages still run for visitors.

About ?development RUAL Studio still adds ?development to the URLs it opens. On a current core the parameter changes nothing: you get the saved version, the same as any visitor.

Older cores keep a separate deployment

Ask your cluster which kind it is:

Terminal

curl -s https://<your-cluster>/api/v1/info

A current core answers "has_bp_deploy": false under flags. Studio treats a core that does not send the flag at all as an older one, from version 14 or earlier, and offers deployment there. On those cores, since version 13.0.7:

Saving keeps changes in the development environment. To publish, open the Menu and select Deployment, where you find a list of recently modified blueprints, components and more to deploy.
Pages opened with ?development show the non-deployed blueprint when you are logged in with a RUAL Developer account. Everyone else gets the production blueprint.
By default, only cluster owners may deploy. You can grant deployment permissions to your developers while managing user access.
The compare button compares your deployed production blueprint with your development blueprint.

Next steps

Debugging Blueprints Run a flow in simulation with the console open, and read what it did. Version Management Core versions, stable and development releases, and how to upgrade safely. Permissions Who may edit, save, activate and run blueprints.

Frequently asked

How do I deploy a RUAL blueprint to production?

Press Save. On a current core saving publishes the blueprint, so there is no separate deploy step, and a new blueprint needs activating once. Only cores from version 14 and earlier deploy separately; flags.has_bp_deploy on GET /api/v1/info tells you which you have.

Why do my changes not show up for users after saving?

Check that the blueprint is active: saving publishes it, but an inactive blueprint does not respond at all. Then check for a cached query, and for a browser or shared cache holding the old page.