Remoco
Provision isolated compute, data, and models through one API.
What it does.
Remoco hides cloud-specific machinery behind a resource contract built for agents. A run asks for a sandbox or service. Remoco admits it, leases capacity, watches cost and health, and tears it down. Project and workflow state stay in the systems that own them.
Lease the sandbox. Keep the cloud behind the API.
Remoco checks the request, leases an isolated environment from a provider, watches the run, and cleans it up. It does not own Project state or workflow history.
GKE, E2B, Daytona, or Kubernetes can implement the same runner API.
CENTARI owns Projects. ZFlow owns run history. Remoco owns leases.
Identity, cost, network, time, and cancellation are enforced by the control plane.
Latency, failures, cost, and benchmark results decide which providers receive new work.
What it owns
One resource API
Ask for a workstation, service, database, queue, model, network, or domain the same way.
Isolated runs
Each workload gets its own lease, credentials, network rules, and cancellation handle.
Reconciled lifecycle
Remoco watches health, cost, quota, and cleanup after the initial create call.
Bring the provider
Use GKE, Kubernetes, E2B, Daytona, or a private cloud behind the same runner contract.
