Record it once, replay it across the fleet
The same routine moves from a single recording to every profile you run: steps captured by meaning, secrets handed to variables, and one workflow replayed across many profiles at once.
Record the task, keep the steps
Run the task once in a profile and Oculr saves it as a named workflow. Steps are captured by role and text, so they are re-found that way on every run.
Credentials become variables
Declare per-workflow variables and supply their values at run time. Logins and other secrets stay out of the recorded steps and substitute in at the right moment.
Replay across the whole fleet
Run one workflow across many profiles at once, each with its own per-profile variable values, its own proxy, and its own isolated identity, while the recorded steps stay the same.
The work you do once becomes the work you never repeat
Recording captures the real steps, not a fragile macro. Variables keep secrets out of the steps, and fleet replay puts the same routine to work across every profile at once.
Record the task, keep the steps
Start recording, run the task in a profile, and save it as a named workflow. Steps are captured against what the page means: elements are stored by role and text, so they are re-found that way on every run instead of by brittle pixel positions.
- Record once, no scripting to write
- Semantic selectors: role and text, not pixels
- Edit on a visual node canvas or as a step list
Credentials become variables
Declare per-workflow variables and supply their values when you run. Logins and other secrets are handled as variables, so they are not baked into recorded steps, and replay substitutes the right value at the right moment.
- Secrets run as variables, not stored in steps
- Supply values at run time, per run
- Live per-step status as the run progresses
Replay across the whole fleet
Run one workflow across many profiles at once, each with its own per-profile variable values. The recorded steps stay the same while every profile uses its own inputs, its own proxy, and its own isolated identity.
- One workflow, many profiles at once
- Per-profile variable values throughout
- Each profile keeps its own proxy and identity
Frequently asked questions
How does record and replay browser automation work in Oculr?+
Hit record, do the task once in a profile, then save it as a named workflow. Oculr captures the steps as you go and replays them on demand with the values you supply. There is no scripting to write.
Why do recorded workflows survive page changes better than pixel macros?+
Oculr records against what the page means, not where things sit. Elements are stored by role and text and re-found that way on every run, so a moved button or a shifted layout does not automatically break the step.
Where do logins and other secrets go?+
Credentials become variables. Instead of baking a password into a recorded step, you declare it as a variable and supply the value at run time, so secrets are not stored inside the workflow itself.
Can one workflow run across many profiles?+
Yes. Fleet replay runs a single workflow across many profiles at once, with per-profile variable values, so each profile uses its own inputs while following the same recorded steps.
Can I edit a workflow after recording it?+
Workflows open in a visual node canvas or as a step list, behind a Canvas and List toggle. Reorder steps, adjust variables, and tidy the flow in whichever view fits the task.
Can I see what a run is doing?+
Each run shows per-step status as it progresses, so you can watch a replay move through the steps and see where it is at any moment.
Stop doing the same task twice
Spin up your first two profiles free, record a routine once, and replay it across every profile you run.
No credit card required · Cancel anytime