Custom proxy pools
Allocate resources by target, identity, location, protocol, and workload.
Evaluate custom pools and high-bandwidth capacity in one project, planned around targets, identity, location, useful throughput, and deadline.
Custom pools address routing and isolation. High bandwidth addresses large objects and completion windows.
Allocate resources by target, identity, location, protocol, and workload.
Project capacity for media, images, code archives, and public documents.
Capacity changes, routing adjustments, escalation, and review.
Targets, connections, workers, object sizes, and storage all affect completion.
URLs, object sizes, protocol, location, and failure rules.
Measure target, proxy, worker, and storage limits.
Define pools, connections, workers, and run window.
Use completed objects and remaining time to adjust.
Downloaders, scheduling, resume, checks, and storage are customer responsibilities unless managed data delivery is scoped.
Evaluate the solution across resources, cost model, and useful output.
| Dimension | Custom pool | High bandwidth |
|---|---|---|
| Primary goal | Routing and isolation | Transfer and deadline |
| Configuration | Target, identity, location | Objects, workers, storage |
| Core metric | Useful requests | Useful throughput |
| Scale | Resource and policy mix | Connections and workers |
10Gbps+ is aggregate project capability. Actual throughput depends on targets, connections, workers, object sizes, and storage.
200Gbps+ is total network bandwidth; 10Gbps+ is an enterprise per-project capability.
No. It means traffic is not billed by accumulated GB in the project model.
No by default. Proxy projects deliver network infrastructure.
Use representative targets, objects, workers, storage, and deadline.
Share targets, object scale, workers, and deadline to assess resources and capacity.