Fastly

Fastly

Definition: A San Francisco-based CDN and edge computing company founded in 2011 by Artur Bergman, known for near-instant cache invalidation and a developer-first approach to configuration and tooling. Built on top of Varnish Cache, an open-source HTTP accelerator, Fastly popularized real-time CDN configuration changes at a time when competitors’ purges commonly took minutes rather than seconds. Went public on the NYSE in 2019, and has since pushed further into WebAssembly-based edge compute (Compute@Edge) as a more portable alternative to single-runtime, JavaScript-isolate models like Cloudflare Workers.

Core Services & Concepts

  • CDN — Content Delivery Network (CDN) and Edge Computing, known industry-wide for near-instant cache purges, commonly cited at around 150 milliseconds compared to competitors’ multi-minute purge times
  • Compute@Edge — Serverless Computing and Cold Starts, WebAssembly-based edge compute supporting multiple source languages (Rust, JS, Go) compiled to Wasm rather than a single JS runtime
  • VCL (Varnish Configuration Language) — a developer-facing configuration language, derived from open-source Varnish Cache, giving fine-grained control over caching and request logic
  • Real-time log streaming & analytics — Observability and Monitoring, request-level visibility with minimal delay, popular for debugging traffic issues as they happen
  • Image Optimizer — on-the-fly image resizing and format conversion served from the edge, reducing origin load for image-heavy sites
  • Next-Gen WAF — a web application firewall built on Signal Sciences, a company Fastly acquired in 2020 to strengthen its security product line
  • Fanout — a real-time messaging and streaming API product for pushing WebSocket, SSE, and long-polling updates from the edge, built on the open-source Pushpin project Fastly maintains

How Pricing Works

  • Usage-based pricing built around bandwidth and request volume, with a notably smaller free tier than Cloudflare’s
  • Historically required a minimum monthly spend commitment for self-serve accounts, a meaningful difference from Cloudflare’s free-forever tier
  • Compute@Edge is billed separately based on compute resource usage, distinct from core CDN bandwidth charges
  • Security add-ons (Next-Gen WAF) and premium support are priced on top of the base CDN plan
  • Enterprise customers negotiate custom contracts, similar to competitors, once traffic and feature needs exceed self-serve tiers
  • Billing is generally transparent and usage-itemized, appealing to engineering teams that want to reason precisely about cost drivers

Pros

  • Fastest cache invalidation in the industry, purges commonly propagate in roughly 150 milliseconds instead of the minutes typical elsewhere
  • Developer-friendly VCL configuration language giving precise, code-like control over caching behavior
  • Strong real-time analytics and log streaming, useful for debugging traffic issues as they happen rather than after the fact
  • Compute@Edge’s WebAssembly model offers multi-language support and strong isolation/performance characteristics
  • Well regarded among engineering-heavy teams for API and infrastructure quality over flashy marketing
  • Transparent, itemized usage billing makes cost attribution easier than vaguer bundled pricing from some competitors

Cons

  • Smaller free tier than Cloudflare, less attractive for hobbyists or very early-stage projects
  • Smaller global network footprint than Akamai or Cloudflare, meaning potentially higher latency in some underserved regions
  • More expensive at small scale, historically requiring a minimum spend that Cloudflare’s free tier doesn’t
  • VCL, while powerful, has a steeper learning curve than simpler dashboard-driven caching rules
  • A high-profile 2021 global outage, traced to a single customer’s configuration change, highlighted the risk of concentrating so much traffic on one provider
  • Smaller company overall than Cloudflare or Akamai, meaning a narrower breadth of adjacent products (no equivalent to Cloudflare’s Zero Trust suite, for instance)

Comparison: Fastly vs Cloudflare vs Akamai

FastlyCloudflareAkamai
Primary strengthFastest cache purge/invalidation and real-time configurabilityLargest all-in-one edge network spanning CDN, security, and serverless computeDeepest enterprise relationships and longest-running large-scale CDN footprint
Typical pricing modelUsage-based, smaller free tier, pay-as-you-go plus enterprise contractsGenerous free tier, self-serve usage-based paid plans, custom enterprise pricingEnterprise contract-based, sales-negotiated, rarely self-serve
Best fitMedia/news and API-heavy teams needing instant purges and fine-grained real-time controlStartups to large enterprises wanting a broad, self-serve edge/security platformLarge enterprises, broadcasters, and e-commerce needing contract-based SLAs at massive scale
API/product styleREST API + VCL/Compute@Edge (Wasm), developer-first toolingREST API + Workers (JS/Wasm serverless) + broad self-serve dashboardREST/Akamai API + EdgeWorkers, more enterprise-console-driven

Best For

  • News and media publishers needing instant cache purges the moment a breaking story updates
  • API-heavy platforms wanting fine-grained, code-like control over edge caching and routing logic

Real Examples

  • Used by The New York Times, GitHub, and Reddit for content delivery
  • Publicly cited by Fastly as a customer alongside Pinterest and Vimeo, spanning news, API, and image/video-heavy use cases
  • Popular among API-first and infrastructure-focused companies that value real-time purge and analytics over sheer product breadth

Use Cases

  • News publishing platforms needing instant cache purges on breaking updates
  • API gateways and API-heavy backends needing edge caching with fine-grained control
  • Real-time content delivery for e-commerce and ticketing sites during high-traffic events
  • Image- and video-heavy sites using Image Optimizer to reduce origin load
  • Security-conscious teams wanting WAF (Signal Sciences-based) alongside CDN from one vendor
  • Real-time messaging and live-update features (chat, notifications, live scoreboards) built on Fanout instead of maintaining separate WebSocket infrastructure

Integration Notes & Common Pitfalls

  • VCL customization has a real learning curve, teams coming from simple dashboard-based CDNs should budget time to learn its request/response hook model
  • Self-serve accounts have historically required a minimum monthly spend, worth checking current terms before assuming a free-tier-only setup is viable
  • Compute@Edge requires compiling to WebAssembly, language and tooling support (Rust, JS, Go) is solid but narrower than a general-purpose serverless runtime
  • The June 2021 global outage, triggered by a single customer’s valid-but-unexpected configuration change, is a widely cited example of blast-radius risk when relying on one CDN provider for critical infrastructure
  • Minimum spend commitments and smaller network footprint mean it’s worth benchmarking latency in a project’s specific target regions before committing, rather than assuming parity with Cloudflare or Akamai everywhere

Code Example

# Fastly VCL — cache static assets aggressively, bypass cache for API routes
sub vcl_recv {
  if (req.url ~ "^/api/") {
    return(pass);
  }
}

sub vcl_fetch {
  if (req.url ~ "\.(css|js|png|jpg)$") {
    set beresp.ttl = 1d;
    set beresp.http.Cache-Control = "public, max-age=86400";
  }
}

FAQ

What makes Fastly’s cache purging so much faster than competitors? Its architecture propagates purge instructions across its network in roughly 150 milliseconds, built specifically for real-time invalidation, whereas many competing CDNs historically took minutes for full propagation.

Is Compute@Edge the same as Cloudflare Workers? Conceptually similar in that both run compute close to the user, but Compute@Edge is built on WebAssembly rather than a JavaScript-isolate model, supporting multiple source languages compiled to Wasm instead of a single runtime.

Why did a single Fastly outage in 2021 affect so many major websites? A valid configuration change from one customer triggered a previously undetected software bug across Fastly’s network, taking down sites like Reddit, The New York Times, and gov.uk simultaneously, illustrating how concentrated a large share of the internet’s traffic is on a handful of CDN providers.

Does Fastly have a free tier like Cloudflare? It offers a limited free trial/developer tier rather than Cloudflare’s free-forever plan, and self-serve accounts have historically carried a minimum monthly spend once past the trial.

History

  • Founded in 2011 by Artur Bergman, built on top of Varnish Cache, an open-source HTTP accelerator
  • Went public on the NYSE in May 2019
  • Acquired Signal Sciences in 2020 to add a modern WAF product to its security lineup
  • Suffered a major global outage in June 2021 that took down large parts of the internet for roughly an hour, becoming one of the most widely cited examples of internet infrastructure concentration risk

Referenced by

Dig deeper