F5 Distributed Cloud Pricing: Packages, Entitlements, and Quote Inputs

F5 publishes the structure of Distributed Cloud Services packaging, but its current public materials direct buyers to sales for pricing information. The useful procurement question is therefore larger than a per-request rate. Buyers need to identify the package and included capacity before asking F5 for a written quote. They also need to document regional usage, required add-ons, retention needs, and traffic growth.

TL;DR

• F5 packages Distributed Cloud Services as Essentials and Enterprise, with advanced security capabilities concentrated in Enterprise.
• The September 2026 package sheet includes 30 million requests in each base package. It provides different allowances for load balancers and CDN transfer, plus logs.
• Bot Defense and customer edge capacity may be add-ons. Several other capabilities also depend on the package and deployment.
• F5 does not publish a complete public dollar rate card. Build a workload sheet and obtain a written quote for the actual regions and services under the proposed term.

Public pricing stops at the package structure

The F5 Distributed Cloud Services product page presents one SaaS platform spanning web application and API protection, plus application delivery. It also covers edge distribution and networking. The page links to a package datasheet and sends commercial inquiries to F5 rather than displaying a complete dollar schedule.

F5's pricing and subscription contact page asks buyers to submit a form for pricing information and free trials, as well as partner opportunities. That makes the current buying motion quote-led. Contract term and region mix can affect the final price. Support, capacity, and negotiated discounts can also change it, so an uncited number from a reseller page is a poor basis for a 2027 budget.

I would reject a procurement worksheet with one row labeled "F5 Distributed Cloud" and no workload assumptions.

It gives finance nothing to reconcile when the quote arrives. Put the architecture beside the commercial request. Document public applications and expected monthly requests first. Then add peak rate, origin locations, protected domains, and CDN regions. Record log retention and the security services each application needs.

Essentials and Enterprise set the first boundary

The September 2026 F5 Distributed Cloud Services package sheet defines two packages. Essentials targets secure delivery of public-facing web applications. Enterprise adds capabilities for higher security and compliance needs across hybrid environments. Both packages include web application firewall functions and service policies. They also include rate limiting, Layer 7 DDoS controls, secure caching, and core API controls. DNS and CDN are included, along with observability and platform administration.

Enterprise includes additional capabilities in the package matrix. Examples include malicious-user detection and malware protection, along with AI-enabled request risk scoring. API schema validation and sensitive-data detection also appear there. Compliance reporting and client-side protection are included. Advanced API discovery is included with Enterprise and listed as an add-on for Essentials.

Package selection should follow the controls the deployment will use in production. Counting checkmarks without tracing traffic produces an inflated edition choice or a late add-on. Take one public API and mark its WAF policy and schema checks. Then add sensitive-data inspection and bot controls. Record client-side scripts and the log path. Repeat that exercise for every materially different application class.

Included entitlements shape the quote

The package sheet uses requests as the traffic measure for application delivery and security inspection, as well as policy enforcement. It lists 30 million requests in both Essentials and Enterprise. A request is counted once as it traverses the configured application delivery and security services. That definition belongs in the forecast. Browser pages and mobile clients create one request profile. APIs and retries create others, as does health traffic.

Infrastructure allowances differ.

The sheet lists one public or distributed load balancer for Essentials and four for Enterprise. CDN data transfer is 5 TB for Essentials and 15 TB for Enterprise. Essentials includes 1 million logs, while Enterprise lists 50 million. Each package includes one tenant virtual IP and 500,000 synthetic-monitoring executions. Each also includes three web-scanning applications. The same sheet lists five DNS zones and five DNS load balancers for Essentials, compared with 10 of each for Enterprise.

Those are dated commercial inputs, not permanent product facts. Save the exact package sheet used for the estimate and require the quote to resolve every allowance. A screenshot of the entitlement page beside the signed order is far more useful than a bookmark that changes during renewal.

Add-ons can dominate the final scope

Several controls in the F5 matrix carry an add-on label. AI agent detection and advanced bot protection are add-ons for both base packages. Credential-stuffing defense and web-scraping prevention sit in the same bot-protection group. Device fingerprinting and data intelligence are there too. Mobile app protection is also an add-on in both columns.

Deployment architecture creates another branch. Enterprise includes three medium customer edge nodes with WAF in the cited sheet, while Essentials lists customer edge nodes as an add-on. Enterprise includes 20 Mbps of public non-HTTP application traffic and 1 TB of data transfer between customer and regional edges. Essentials marks those entries as add-ons. Additional capacity can change the commercial scope for either package.

This is where the whiteboard earns its keep. Draw the public virtual IP and origin. Add the customer edge and regional edge. Mark HTTP and non-HTTP traffic separately. Add expected transfer by region, then note each advanced security service attached to that path. The AI security buying guide uses the same principle: evaluate a product against the control point and evidence you need, rather than buying a category label.

Build a quote sheet the vendor can price

Start with a 12-month baseline and a peak-month case. Record monthly requests and peak requests per second for each application class. Add public or distributed load balancers and domains. Document DNS zones and DNS load balancers. Then record CDN transfer by region and non-HTTP throughput. Estimate request and security log volume separately because one retained event can have a different cost and operational owner than one processed request.

List the controls beside the workloads that require them. Include advanced API discovery and schema validation. Add sensitive-data detection and bot protection. Record account-takeover controls and client-side defense. Include malware scanning and mobile shielding, plus routed DDoS where applicable. Record customer edge node size and count. Add synthetic-monitoring executions and scanning targets. Finish with support terms, onboarding, and required retention.

Ask F5 to return the quote in the same shape.

The response should identify the base package and add-ons. It should state included capacities and overage treatment. Regional adjustments and the minimum term should be explicit. The quote should also document renewal assumptions and support. It should define what counts as a request for each enabled service. A clean quote lets procurement calculate an effective cost per protected application and per million requests without pretending those figures are F5's public list prices.

Application security and LLM policy cover different routes

F5 Distributed Cloud Services protects web applications and APIs at a broad delivery and security edge. Its package sheet includes WAF and API protection. It also covers DDoS controls and bot functions, plus application delivery. An LLM policy gateway decides whether an authenticated user or agent may send a given prompt and data class to a model route. That decision follows the current policy.

The AI firewall, gateway, and proxy comparison separates those control points. A general web application control can protect the public API that receives a user request. The LLM inference gateway can carry identity and prompt context on the downstream model call. Some deployments need both because the application edge and the model route see different identities and payloads, along with different policy decisions.

Budget them against their actual jobs. Avoid crediting either layer with controls it cannot exercise. The F5 quote should follow protected applications and delivery traffic, with the selected security services listed separately. An AI policy budget should follow authenticated model requests and identity integration. It should also account for classifications, policy evaluation, and retained decision evidence.

DeepInspect

DeepInspect covers authenticated HTTP traffic between users or agents and LLM endpoints. It evaluates application-supplied identity and role before forwarding a model request. The decision also considers data classification and destination under the applicable policy. Each decision produces evidence tied to the route and policy version.

That boundary complements an application-edge service.

DeepInspect does not replace F5 WAF, CDN, DDoS, bot, or multicloud networking functions. F5 does not supply DeepInspect's identity-bound LLM decision record on a downstream model route. Scope each product against the traffic it can inspect, then price the two layers with separate workload assumptions. Book a technical deep dive at deepinspect.ai.