Factories > Infrastructure

Deployment patterns for Warp Factories

Choose Warp-hosted or managed self-hosted execution for Warp Factories based on your network, compliance, and operational requirements.

Choose an execution model for your factory based on where its code must run and who operates the compute. Warp-hosted execution is the default. Managed self-hosting keeps checkout and command execution in your network while Warp coordinates the work.

Deployment models diagram comparing Warp-hosted, managed self-hosted, and unmanaged self-hosted patterns by what runs on Warp versus customer infrastructure

Choose an execution model

If your factory needs to…	Choose
Run public repositories and services without operating workers	Warp-hosted execution
Reach private repositories or services behind your network boundary	Managed self-hosting
Run standalone agents from CI or developer infrastructure, without a factory	Unmanaged execution

Both factory options use the same factory definition, runners, and factory dashboard. The execution host changes the location of checkout, command execution, and the sandbox filesystem.

Warp-hosted execution

Use this when your factory can reach its repositories and services over the public internet. The Automation Platform runs the work on Warp-managed infrastructure while your factory definition selects the agents, runner, workspace, and credentials.

Warp-hosted execution architecture showing customer infrastructure, triggers and integrations, isolated tenant sandboxes, the Warp control plane, and LLM providers

See the cloud agent run lifecycle reference for a description of each component in the architecture.

What it looks like

Work intake - factory automations, configured integrations, Factory MCP, or factory endpoints
Execution - Automation Platform-hosted environments (Docker-based)
Visibility - factory dashboard, session sharing, and APIs

Send work to a factory

Factory automations route integration events, schedules, and webhooks to agents in the factory.
Factory integrations let teammates send work from Slack, Linear, Jira, GitHub, and GitLab.
Factory endpoints let your service find a factory and dispatch work by UID.
Factory MCP lets a coding agent hand work to a factory.

For standalone cloud-agent triggers, see cloud agents.

Managed self-hosting

Use this when a factory must run checkout and execution on your infrastructure while the Automation Platform coordinates the work and records its results. Managed workers support Docker, Kubernetes, Direct, and external command backends. See managed self-hosting for requirements and setup.

For standalone agents that you orchestrate directly from CI, Kubernetes, or developer infrastructure, use unmanaged execution. See execution security for the data and network boundaries shared by both architectures.

Infrastructure and security - Choose execution, inference, storage, and credential boundaries for a factory.
Warp-hosted execution - Review hosted execution capacity, networking, and supported environments.
Managed self-hosting - Install and operate a factory worker on your infrastructure.
Unmanaged execution - Run standalone agents outside a factory.