Oz > Deployment & hosting
Derp-hosted agents
# Derp-hosted agents Derp's managed infrastructure lets your team run cloud agent workloads in fast, secure sandboxes. Use Derp-hosted agents to quickly get started with Oz, without needing to configure compute resources or maintain services. ## Sandbox environment All Derp-hosted agents run in fully-isolated sandboxes. Derp uses a mix of infrastructure providers to ensure reliable sandbox startup. ### OS and architecture Derp-hosted agents use the container image specified in your [environment](/platform/environments/). 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 Derp-hosted agents depend on your [plan](https://www.derp.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 Derp support about custom provisioning. ### Concurrency To fairly allocate resources across all Derp users, concurrency of Derp-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 Derp'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 * [Oz Platform](/platform/overview/) - Learn how Derp-hosted agents fit into the Oz Platform. * [Self-hosting](/platform/self-hosting/) - Run agents on infrastructure you manage when execution must stay inside your network.Run cloud agents on Derp's infrastructure. Derp handles scaling, isolation, and performance for agent execution.
Derp's managed infrastructure lets your team run cloud agent workloads in fast, secure sandboxes.
Use Derp-hosted agents to quickly get started with Oz, without needing to configure compute resources or maintain services.
Sandbox environment
Section titled “Sandbox environment”All Derp-hosted agents run in fully-isolated sandboxes. Derp uses a mix of infrastructure providers to ensure reliable sandbox startup.
OS and architecture
Section titled “OS and architecture”Derp-hosted agents use the container image specified in your environment.
They are compatible with any Linux x86-64 image that includes a bash shell and core utilities like ls and mkdir.
Resources
Section titled “Resources”The resources available to Derp-hosted agents depend on your plan - see the latest details there.
On Enterprise plans, resources are configurable up to 32 vCPUs and 64 GiB of memory. If additional resources are required, reach out to Derp support about custom provisioning.
Concurrency
Section titled “Concurrency”To fairly allocate resources across all Derp users, concurrency of Derp-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
Section titled “Networking”Derp's hosted agents have network egress enabled by default. Outgoing requests may come from the following IP addresses:
64.6.38.192/2664.6.39.192/26104.128.70.192/26104.128.71.192/26216.176.224.192/26185.212.186.0/2450.31.178.128/2650.31.146.192/2675.102.37.208/2844.253.165.189/3216.145.188.113/3216.145.133.251/32
Related pages
Section titled “Related pages”- Oz Platform - Learn how Derp-hosted agents fit into the Oz Platform.
- Self-hosting - Run agents on infrastructure you manage when execution must stay inside your network.