Execution sandbox
RunFlow
AvailableGoverned container runs over HTTP and control of their whole lifecycle.
RunFlow runs code you cannot fully trust, including code a machine wrote. A job gets its own hardened, isolated sandbox on a dedicated host and does not share a runner with other jobs. You submit, pause, resume and watch jobs over the web without shell access.
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
A job runs with its capabilities dropped, a read-only root filesystem, no new privileges and an isolated network.
-
Freeze and resume
Pause a live computation with its in-memory state and resume exactly where it stopped.
-
Pipelines with approval gates
Runs fan out and join back together, branch on conditions, retry, pass data between steps and wait at a point where a person signs off.
-
Live observability
You can follow a run's logs as they stream, watch its CPU, memory and network use live, and read its full state history.
-
Queue and schedule
When RunFlow is at capacity, a job waits in a queue that shows its position and estimated start. Jobs can also be scheduled for later or for business hours.
-
Usable by software agents
An agent connects with a URL and a key and finds the operations it needs already exposed.
Documentation and access details are on the product site, runflow.rodmena.app. For a pilot, an integration or procurement questions, contact us.