Fastly Launches AI Firewall and AI Runtime Control to Secure and Scale AI

Fastly announced AI Runtime Control, AI Firewall, and expanded API Security capabilities under its Fastly for AI portfolio. The products are designed to provide real-time visibility and control over AI model access, protect AI applications, and manage how AI agents access enterprise APIs. The launch strengthens Fastly's cybersecurity and AI infrastructure offering, though no financial impact or customer adoption metrics were disclosed.

Analysis

The strategic value is less the feature set than whether it converts Fastly from a performance/CDN budget line into a security-control-plane vendor. That would raise switching costs and expand wallet share within existing enterprise accounts, but only if deployment occurs inline with application traffic and customers accept Fastly as an enforcement point rather than using incumbent cloud security stacks. Near-term revenue impact is likely immaterial absent pricing, design-partner, or attach-rate disclosure; the relevant 1-3 month catalyst is evidence of paid adoption in the next earnings call and pipeline commentary.

Competitive pressure is concentrated against Cloudflare (NET), Akamai (AKAM), Zscaler (ZS), Palo Alto Networks (PANW), and hyperscaler-native controls. NET has the cleaner cross-sell narrative because of its broader developer and security distribution, while PANW and ZS retain stronger enterprise security purchasing influence; Fastly’s opportunity is primarily customers seeking lower-latency policy enforcement at the edge. A successful attach can improve gross-margin mix and net retention over 6-18 months, but feature parity alone will not repair valuation without sustained growth acceleration.

Consensus may over-credit AI labeling before budgets materialize: enterprises are still rationalizing overlapping API, WAF, and AI-governance tools. The key falsifier is any indication that these capabilities are bundled free to defend existing traffic revenue, which would increase operating expense without measurable ARPU expansion. Treat this as a watch catalyst, not a standalone long signal, until management quantifies customers, paid SKUs, or security ARR contribution.

Key Decisions for Investors

• No immediate directional FSLY position on the announcement alone; set an alert for the next earnings release for paid-customer count, security product attach rate, net retention, and forward revenue guidance. A long is justified only if management ties the products to measurable ARR/pipeline and guides to reaccelerating growth.
• Use a relative-strength screen over the next 1-3 months: if FSLY materially outperforms NET and AKAM while consensus revenue estimates remain unchanged, fade the move via a tactical FSLY short or long AKAM/FSLY-short pair; the risk is a disclosed large enterprise security win or material guidance raise.
• For structural AI-security exposure, prefer NET over FSLY until Fastly demonstrates monetization: NET has broader distribution and a more established security cross-sell engine. Reassess the relative trade if FSLY reports sequential improvement in dollar-based net retention and security-led billings over two quarters.
• Monitor enterprise AI governance spending signals from PANW, ZS, and cloud-security peers. Broad budget expansion would validate the category and improve FSLY’s upside optionality; a continued preference for consolidated platforms would make standalone edge-security launches a margin-dilutive defensive response.