OpenCompute

OpenCompute is a self-hosted orchestrator for agent sandboxes and a provisioning backend for Environments. It runs in infrastructure your organization controls, such as your cloud accounts or data centers. When a session, Automation, or other feature that uses an Environment needs a sandbox, Factory's control plane requests it from OpenCompute, which provisions the sandbox in your infrastructure.

Why OpenCompute#

Environments define how features such as sessions, Automations, and Delegations run in the cloud, and Factory's control plane manages the lifecycle of each sandbox. Those sandboxes can be provisioned on Factory-managed infrastructure or, through OpenCompute, inside infrastructure you control. OpenCompute is intended for organizations that need agent workloads to stay within their own infrastructure.

When to use it#

• You need agent workloads to run in your own cloud accounts or data centers for security, compliance, or data-residency reasons.
• You want Droids to reach internal repositories, package registries, and services without exposing them to the internet.
• You need sandboxes that are created on demand and scale with workload across many teams and concurrent tasks.
• You want Droid sandboxes to run on platforms your organization already approves and operates.

OpenCompute requires your team to deploy, operate, and maintain the underlying infrastructure and the OpenCompute deployment on an ongoing basis.

How it works#

At a high level:

• OpenCompute runs inside your infrastructure and connects out to Factory, so you do not open inbound firewall ports for Factory.
• When a session or Automation that uses an Environment needs a sandbox, Factory's control plane requests it from OpenCompute. OpenCompute provisions the sandbox in your infrastructure, and Factory's control plane manages its lifecycle.
• Sandboxes can reach internal repositories, registries, and services from inside your network, without those systems being exposed publicly.
• OpenCompute is designed to be flexible about where and how sandboxes run, so it fits the infrastructure and runtimes your team already uses. For example, sandboxes can run as workloads on Kubernetes clusters you already operate.

Prerequisites and setup steps are shared with your team during onboarding.

Choose your compute#

Environments can run on Factory-managed compute or on OpenCompute. Factory-managed compute is the recommended default for most teams. Consider OpenCompute only when sandboxes must run inside infrastructure your organization controls. Remote Control is a separate option for running Droid on individual machines you manage yourself.

Request access#

Access to OpenCompute is limited during Private Preview. To request access, fill out the form at factory.com/contact or contact your Factory account team.