Studio is the workshop where you build all of it.
The environment in Core where you build, test and release. No save button, no refresh: you watch your colleagues’ cursors move and blocks appear while they work.
The Flow Editor in Studio. The coloured avatars top right are your colleagues, live in the same flow. See the Flow Editor
What you do in Studio
Build, work out why something is not doing what you expected, and extend. Without leaving the environment.
Build together, live
Everyone works in the same flow and sees the others working in real time, down to the cursor. Stuck? A RUAL engineer can look along remotely, inside your own environment.
Debug on the real thing
Click a block and watch the actual data running through it, as it happens. No log lines to add, no redeploy, no guessing.
Custom blocks
Using a tool that does not have a block yet? We build that block into the platform and maintain it for you. Your team only has to drag it into place.
2,800 blocks are already waiting for you.
For logic, data and dates, and just as much for Exact, Mollie, DOBOT robots, ZPL printers and Claude from Anthropic. You search, drag and connect. Missing a block? File a request and it is in there within a week, built and maintained by us.
- Block templates for the patterns you use more than once
- Groups and copy/paste for large blueprints
- Every block documented on docs.rual.nl
search for a block… ⌘K
date
104 blocks
array
99 blocks
condition
68 blocks
files
56 blocks
query
53 blocks
users
49 blocks
http connection
40 blocks
anthropic
27 blocks
dobot
22 blocks
zpl
21 blocks
mollie
18 blocks
floriday
8 blocks
Real counts, from the block library in Core 14.
All blocks →Changes take minutes, not sprints.
Studio is approachable enough that the kid next door who was playing Minecraft yesterday is helping build your fleet management today. Because your flows are visual, everyone can see how the process runs, including your operations manager. You discuss a change at the screen and make it there and then. Internal questions resolve themselves before they turn into tickets.
- Change existing flows without a development project
- Insight into what your development team is building and where the time goes
- Usage statistics per environment, so you keep a grip on your IT
Nothing goes missing, nothing happens quietly.
A blueprint belongs to your whole team, so Studio records everything that happens to your flows.
Full history
Every change to a blueprint is recorded: who, what, when. Looking back and rolling back come with it.
Comments on blocks
Discussion happens where it belongs: on the block itself, inside the flow, not in a separate mail thread.
Validation before go-live
Studio validates your blueprint and points out broken connections and missing fields before they reach production.
Deploy management built in
Want to roll changes out in a controlled way instead of straight to live? Studio has deploy management built in: stage it, review it, release it when you say so.
Time tracking built in
Development time is tracked automatically per developer and per project. You see where the hours go, without a separate timesheet tool beside it.
Who builds Studio
We are the heaviest user of Studio ourselves, and it shows in the pace.
By developers, for developers
We have been building business applications for fifteen years and we work in Studio every day ourselves. Anything that annoys us gets fixed, and every environment benefits.
Improvements within a week
Changes to the platform or to Studio are usually live within a week of approval. The changelog on docs.rual.nl updates live from our code deployments: what we build, you see appear there.
Want to hold Studio in your own hands?
In a demo you build a flow yourself. That is when you feel whether it fits your team.