Fastly launches AI security and control tools for enterprises

Fastly launched three AI-security and governance tools—AI Runtime Control, AI Firewall, and enhanced API Security—to manage model access, AI-agent API usage, and prompt-injection risks on its edge cloud platform. The launch addresses rapidly rising AI demand: machine-generated traffic exceeded 50% of Fastly network traffic in July and August 2026, while AI traffic grew 6.5x faster than human traffic from January through May. The capabilities are immediately available and extend Fastly's existing bot management, DDoS protection, and API-security offerings.

Analysis

The product set is strategically relevant because it shifts Fastly’s AI exposure from bandwidth consumption toward a higher-value control plane: security, routing, spend governance, and API enforcement. The near-term revenue contribution is unlikely to move estimates without disclosed pricing, attach rates, or design wins, but successful bundling could improve net retention and mix by monetizing customers’ operational AI risk rather than competing solely on CDN price. The key competitive test is whether Fastly can sell these features into its installed base faster than Cloudflare (NET), Akamai (AKAM), and hyperscaler-native tooling can commoditize them.

Over the next 1-3 months, this is principally a validation/watch catalyst rather than a standalone earnings trade. Investors should look for AI-security bookings, paid-conversion metrics, expansion in security ARR, and gross-margin commentary; a material increase in compute-intensive inspection could otherwise dilute margins if pricing is usage-light. If adoption is real, the 6-18 month implication is a more credible security-platform multiple for FSLY, but only if it demonstrates cross-sell without elevated sales-and-marketing expense or customer concentration.

Consensus may overvalue the headline traffic statistic: machine traffic includes bots and automated workloads that do not necessarily translate into premium AI-security revenue. Conversely, the underappreciated upside is that runtime budget controls can become a procurement wedge for CIOs facing uncontrolled model spend, creating a natural attachment point to API security. The thesis is falsified if the next two earnings reports show no improvement in security growth, dollar-based net retention, or forward gross-margin trajectory.

Key Decisions for Investors

• No immediate directional FSLY position solely on the launch; set an alert for the next earnings call for disclosed AI-security ARR, paid customers, pricing model, and security attach-rate evidence.
• If FSLY guides to accelerating security revenue or net retention while maintaining gross-margin guidance, initiate a 3-6 month long FSLY position sized small: target a rerating toward security/edge peers, with exit on a material gross-margin guide-down or absent AI monetization evidence in two reporting cycles.
• For a cleaner competitive expression, consider long NET / short FSLY only if FSLY’s security-growth commentary remains weak while NET demonstrates enterprise AI-security bookings; reassess after each company’s next earnings release because product differentiation and valuation dispersion can reverse quickly.
• Monitor AKAM and NET pricing and product announcements around AI gateway, API protection, and prompt-security functions. Aggressive bundled pricing by either would reduce Fastly’s ability to monetize the new capabilities and weaken the long case.