> For the complete documentation index, see [llms.txt](/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Warp-hosted execution for Warp Factories

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 and your team does not need to manage worker capacity or host maintenance. For private services or a network boundary that must contain checkout and execution, use [managed self-hosting](/factories/self-hosting/).

## Sandbox environment

All Warp-hosted agents run in fully-isolated sandboxes. Warp uses a mix of infrastructure providers to ensure reliable sandbox startup.

### 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. They are compatible with any Linux x86-64 image that includes a `bash` shell and core utilities like `ls` and `mkdir`.

### Resources

The resources available to Warp-hosted agents depend on your [plan](https://www.warp.dev/pricing) - see the latest details there.

On [Enterprise](/enterprise/) plans, resources are configurable up to 32 vCPUs and 64 GiB of memory. If additional resources are required, reach out to Warp support about custom provisioning.

### Concurrency

To fairly allocate resources across all Warp users, concurrency of Warp-hosted agents is limited on a per-team basis. If an agent is started while at your concurrency limit, it is automatically queued and will start as soon as another agent completes.

### Networking

Warp’s hosted agents have network egress enabled by default. Outgoing requests may come from the following IP addresses:

-   `64.6.38.192/26`
-   `64.6.39.192/26`
-   `104.128.70.192/26`
-   `104.128.71.192/26`
-   `216.176.224.192/26`
-   `185.212.186.0/24`
-   `50.31.178.128/26`
-   `50.31.146.192/26`
-   `75.102.37.208/28`
-   `44.253.165.189/32`
-   `16.145.188.113/32`
-   `16.145.133.251/32`

* * *

## Related pages

-   [Automation Platform](/platform/overview/) - Configure the shared cloud-agent primitives behind a factory.
-   [Factory runners](/factories/runners/) - Choose the operating system, architecture, and instance shape for factory work.
-   [Managed self-hosting](/factories/self-hosting/) - Run factory work on infrastructure you manage when execution must stay inside your network.