Factories > Infrastructure
Warp-hosted execution for Warp Factories
# Warp-hosted execution for Warp Factories Warp-hosted execution runs factory work in managed sandboxes. Warp provisions the compute while your factory definition selects each agent's runner, repositories, setup, and credentials. Use it when your factory's repositories and services are reachable from the public internet. Warp manages capacity and host maintenance. For private services or a network boundary that must contain checkout and execution, use [managed self-hosting](/factories/self-hosting/). ## Sandbox environment Warp-hosted agents run in isolated sandboxes. See [About factory infrastructure and security](/factories/infrastructure-and-security/) for execution, data, and credential boundaries. ## OS and architecture Warp-hosted factory agents use the runner and workspace configuration in your [factory definition](/factories/factory-as-code/). A factory can also use an existing [environment](/platform/environments/) when its definition specifies one. For supported operating systems, architectures, and Linux image requirements, see [runner platform options](/factories/runners/#operating-systems). ## Resources Available CPU and memory depend on your plan. See [Warp pricing](https://www.warp.dev/pricing) for plan information. On [Enterprise](/enterprise/) plans, resources are configurable up to 32 vCPUs and 64 GiB of memory. Contact Warp support about custom provisioning if you need more. ## Concurrency Warp limits concurrent hosted runs per team. Runs started at the limit are queued until another run completes. ## Networking Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp agents, such as in a firewall policy, get Warp's IP address ranges from the "Warp-hosted agent networking" settings for your team. Find it on your team's **Platform** page in the [Admin Panel](https://app.warp.dev/admin/) or on <a href={`https://platform.warp.dev/settings`}>User settings in the Warp Factories web app</a>. --- ## Related pages * [Automation Platform](/platform/overview/) - Review shared cloud-agent capabilities * [Runners for Warp Factories](/factories/runners/) - Choose the operating system, architecture, and instance size * [Self-hosting overview](/factories/self-hosting/) - Run work on infrastructure you manageTell me about this feature: https://docs.warp.dev/factories/warp-hosting/Run factory work on Warp-hosted infrastructure, with managed compute, isolation, networking, and capacity.
Warp-hosted execution runs factory work in managed sandboxes. Warp provisions the compute while your factory definition selects each agent’s runner, repositories, setup, and credentials.
Use it when your factory’s repositories and services are reachable from the public internet. Warp manages capacity and host maintenance. For private services or a network boundary that must contain checkout and execution, use managed self-hosting.
Sandbox environment
Section titled “Sandbox environment”Warp-hosted agents run in isolated sandboxes. See About factory infrastructure and security for execution, data, and credential boundaries.
OS and architecture
Section titled “OS and architecture”Warp-hosted factory agents use the runner and workspace configuration in your factory definition. A factory can also use an existing environment when its definition specifies one.
For supported operating systems, architectures, and Linux image requirements, see runner platform options.
Resources
Section titled “Resources”Available CPU and memory depend on your plan. See Warp pricing for plan information.
On Enterprise plans, resources are configurable up to 32 vCPUs and 64 GiB of memory. Contact Warp support about custom provisioning if you need more.
Concurrency
Section titled “Concurrency”Warp limits concurrent hosted runs per team. Runs started at the limit are queued until another run completes.
Networking
Section titled “Networking”Warp-hosted agents have network egress enabled by default. If you need to allowlist traffic from Warp agents, such as in a firewall policy, get Warp’s IP address ranges from the “Warp-hosted agent networking” settings for your team. Find it on your team’s Platform page in the Admin Panel or on User settings in the Warp Factories web app.
Related pages
Section titled “Related pages”- Automation Platform - Review shared cloud-agent capabilities
- Runners for Warp Factories - Choose the operating system, architecture, and instance size
- Self-hosting overview - Run work on infrastructure you manage