> For the complete documentation index, see [llms.txt](https://docs.warp.dev/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](https://docs.warp.dev/factories/self-hosting/).

## Sandbox environment

All Warp-hosted agents run in isolated sandboxes. Warp uses a mix of infrastructure providers for sandbox capacity.

### OS and architecture

Warp-hosted factory agents use the runner and workspace configuration in your [factory definition](https://docs.warp.dev/factories/factory-as-code/). A factory can also use an existing [environment](https://docs.warp.dev/platform/environments/) when its definition specifies one. Linux runners accept any x86-64 or aarch64 image that includes a `bash` shell and core utilities like `ls` and `mkdir`; macOS runners run in a Warp-provided VM. See [runners](https://docs.warp.dev/factories/runners/) for the options.

### Resources

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

On [Enterprise](https://docs.warp.dev/enterprise/) plans, resources are configurable up to 32 vCPUs and 64 GiB of memory. If you need more, contact Warp support about custom provisioning.

### Concurrency

To allocate resources fairly across all Warp users, Warp limits how many hosted agents a team can run at once. An agent started at the limit is queued and starts 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](https://docs.warp.dev/platform/overview/) - Configure the shared cloud-agent primitives behind a factory.
-   [Factory runners](https://docs.warp.dev/factories/runners/) - Choose the operating system, architecture, and instance shape for factory work.
-   [Managed self-hosting](https://docs.warp.dev/factories/self-hosting/) - Run factory work on infrastructure you manage when execution must stay inside your network.