Portable by default

Run agents wherever the work needs to happen.

Agents run inside network-isolated runners — local, private cloud, customer cloud, on-prem, or sypho-managed. Wherever they run, the control plane keeps one view and one set of controls.

Control Plane
↓
Runner Pools
Local
Cloud
Customer
On-prem
↓
Agent Runtime

Agent execution is tied to where systems live.

Some agents run fine in managed infrastructure. Others need private APIs, customer systems, internal networks, files, databases, regulated data. sypho makes execution location a runtime decision, not a product limitation — the runner is a lightweight binary plus Docker, network-isolated wherever it runs.

One cloud only
→ limited access
Portable runners
→ local, cloud, customer, on-prem, hybrid

Runners are the execution plane.

A runner connects to the sypho control plane and claims work. It spawns a network-isolated sandbox, attaches the right tools, skills, structured data, and secrets — then streams logs, events, and results back.

Control Plane
→
Scheduler / Queue
→
Runner
→
Agent Runtime
→
Tools / Skills / Structured data
→
Events + Results
runners execute workloads
the control plane coordinates state
execution can happen in different environments
logs and results stream back centrally

Choose the right place to run each agent.

Local

Develop and test agents close to your machine before promotion.

Private cloud

Run inside your own infrastructure with access to internal systems.

Customer cloud

Deploy agents into customer-controlled environments when product or data constraints require it.

On-prem

Support restricted networks and enterprise environments with local execution.

Managed

Use sypho-managed execution when speed and simplicity matter most.

From request to result, every step is visible.

A run is more than a model call. sypho tracks the execution path from claim to runner, sandbox startup, tool usage, skill activation, structured-data access, logs, failures, and final result.

step.claimed
lease.granted
sandbox.started
agent.loop.start
skill.loaded
tool.call
tool.result
step.completed

Scale execution without losing control.

Runner pools scale agent workloads by environment, customer, region, or deployment type. The control plane stays the one place that coordinates all of it.

scale runner pools per environment
isolate workloads by customer or deployment
route runs to the correct execution target
track runner health and activity
preserve centralized observability
Runner Pool: customer-eu
├─runner-01active
├─runner-02active
└─runner-03idle

Execution that scales without losing control.

Execution locality

Run agents close to the systems, data, and users they operate on.

Deployment flexibility

Support managed, private, customer-cloud, on-prem, local, and hybrid environments.

Central visibility

Keep one operational view across distributed execution environments.

Runtime control

Attach policies, skills, structured data, and tool permissions to every run.

Production confidence

Understand where each run happened, which runner executed it, and what it did.

Run agents where production requires them.

Request access and help shape portable execution for agentic software.

Request access