Execution sandbox
RunFlow
AvailableGoverned execution of containers over HTTP, with full lifecycle control.
A place to run code you cannot fully trust, including code a machine wrote. Each job runs in its own hardened, isolated sandbox on a dedicated host, and is submitted, paused, resumed and watched over the web, with no shell access and no shared runner between jobs.
Who it is for. Teams that run untrusted or machine-generated code and need isolation, observability and control over it.
- Status
- Available
- Part of
- Core platform
- Product site
- runflow.rodmena.app
- Tags
- Isolated executionPipelinesAgent-readySandboxedPause and resume
What it does
-
Hardened sandbox
Each job gets dropped capabilities, a read-only root filesystem, no new privileges and network isolation.
-
Freeze and resume
Pause a live computation with its in-memory state and resume exactly where it stopped.
-
Pipelines with approval gates
Work fans out and joins back together, with conditional branching, retries, data passed between steps and a point where a person signs off.
-
Live observability
Follow streaming logs, live CPU, memory and network use, and the full state history of every run.
-
Queue and schedule
At capacity, jobs queue with a position and estimated start. Schedule them for later or for business hours.
-
Usable by software agents
An agent connects with a URL and a key, and every operation it needs is already exposed to it.
Documentation and access details are on the product site, runflow.rodmena.app. For a pilot, an integration or procurement questions, contact us.