Deployment modes
How the fleet’s compute capacity is provisioned.Routing policies
How incoming work is distributed.Capacity profiles
The responsiveness-versus-cost tradeoff.Isolation profiles
How fleet workloads are isolated from each other.Egress policies
What outbound network access is permitted.Choosing a configuration
Cost implications
Cost implications
always_on + dedicated has the highest baseline cost but lowest latency variance. serverless + cold_start_ok has near-zero idle cost but occasional cold-start latency. fluid + warm_pool balances the two for most production workloads.Multi-region deployments
Multi-region deployments
Use
geo routing with fluid or dedicated mode to serve users from the nearest region. Combine with failover for resilience across regions.Choosing a configuration
Start conservative and tighten as traffic becomes predictable. Reserve
always_on for latency-critical fleets — it minimizes cold starts but maximizes idle cost.
A
primary_region is required when you create a fleet. Routing policies such as geo and failover build on it to place and fail over work.Related pages
Fleets
Where these settings apply.
Tasks
Work that runs under these settings.
Fleets (concept)
The conceptual model.
Billing & Usage
How configuration affects cost.

