Fastly: The Edge Cloud and CDN Company

August 14, 2026•13 min read•

CDN Edge Computing Cloud Infrastructure Varnish Web Performance Companies

Fastly operates an edge cloud platform, a global network of servers designed to speed up access to websites and applications while protecting them from online threats. At its core, the company provides a content delivery network (CDN) that caches content like images, videos, and API responses in locations physically closer to end-users, reducing latency and improving load times. This solves a fundamental problem of the internet: distance creates delay. By distributing content, Fastly helps businesses deliver a faster and more reliable user experience.

What distinguishes Fastly is its emphasis on programmability and real-time control. From its inception, the platform was built to give developers granular control over how content is cached and delivered. This developer-centric approach allows for custom logic to be executed at the network edge, close to the user, rather than on a distant origin server. This enables advanced use cases beyond simple content caching, such as dynamic content assembly, A/B testing, and sophisticated request routing, making the network an extension of a company's application logic.

History

Fastly was founded in 2011 by Artur Bergman and Simon Wistow. Bergman, who previously served as the VP of Engineering at Wikia (now Fandom), was frustrated with the limitations of existing CDNs. He found them to be slow, opaque "black boxes" that were difficult to configure and offered little visibility into traffic. The founding vision for Fastly was to create a transparent, real-time CDN that developers could control through an API.

The company's technical foundation was built upon Varnish Cache^[1], an open-source web accelerator and reverse proxy. Fastly heavily modified and optimized Varnish to operate at a global scale, using its powerful Varnish Configuration Language (VCL) to give customers direct control over caching rules and HTTP request and response manipulation.

Key milestones in the company's history include:

Initial Funding and Growth: After its founding in 2011, the company raised several rounds of venture capital funding to build out its global network of Points of Presence (PoPs). It attracted high-traffic media publishers and technology companies who valued its performance and configurability.
Initial Public Offering (IPO): Fastly's Initial Public Offering (IPO) was on May 17, 2019, on the New York Stock Exchange (NYSE). The IPO raised significant capital, enabling further network expansion and product development.
Acquisition of Signal Sciences: In a major strategic move to bolster its security offerings, Fastly announced its acquisition of web application security company Signal Sciences in August 2020 for approximately $775 million. This brought a highly regarded Next-Generation Web Application Firewall (WAF) into Fastly's product portfolio.
Global Outage: On June 8, 2021^[2], Fastly experienced a major service outage that took down many of the world's most popular websites, including The New York Times, The Guardian, Reddit, and the UK government's official site. The company resolved the issue within an hour and later published a detailed post-mortem, attributing the cause to a software bug triggered by a specific, valid customer configuration change.
Acquisition of Glitch: Fastly announced its acquisition of Glitch, a web development platform with a community of over 1.8 million developers, on May 19, 2022, for a reported $34.9 million. The acquisition aimed to bring Glitch's developer-friendly tools and community into the Fastly ecosystem, making it easier for developers to build and deploy applications on Fastly's edge compute platform.

For the fiscal year ending December 31, 2023, Fastly reported total revenue of $506.0 million^[3] and a network capacity of 622 Tbps as of 2026.

Core Products and Technology

Fastly's platform is built around a global network of strategically placed servers. The company's network map^[4] shows these PoPs are located in major internet exchange points around the world. The core product offerings run on top of this network.

Content Delivery and Edge Compute

Content Delivery Network (CDN): Fastly's primary service is its CDN. When a user requests content from a customer's website, the request is routed to the nearest Fastly PoP. If the PoP has a cached copy of the content (a "cache hit"), it delivers it immediately. If not (a "cache miss"), the PoP fetches the content from the customer's origin server, caches it for future requests, and then delivers it to the user. Fastly uses both RAM and SSDs for its caching, which provides faster read times than traditional hard drives. A key feature is "Instant Purge," which allows customers to invalidate cached content across the entire global network in milliseconds, ensuring content updates are reflected quickly.

VCL (Varnish Configuration Language): VCL is a domain-specific language that provides the core programmability of Fastly's CDN. It allows developers to write custom logic that executes at different stages of the request-handling process. For example, a developer can use VCL code^[5] to modify HTTP headers, rewrite URLs, perform custom authentication, or direct traffic between different origin servers based on the user's location or device type. This deep control is a significant differentiator from CDNs that only offer configuration through a graphical user interface (GUI).

Compute@Edge: Introduced as the successor to VCL for more complex tasks, Compute@Edge^[6] is Fastly's serverless compute environment. It allows developers to build and deploy more advanced applications directly on Fastly's edge network. Unlike traditional serverless platforms that can suffer from cold start latency, Compute@Edge is built on WebAssembly (Wasm) and an ahead-of-time compilation model. This design provides a secure, high-performance sandbox with near-instant startup times. Developers can write code in languages like Rust, Go, and JavaScript/TypeScript^[7], compiling it to a Wasm binary that runs on the edge. This enables use cases like real-time data processing, personalized content generation, and full-stack applications that run without a traditional origin server.

Security Services

Next-Gen WAF (Web Application Firewall): Acquired from Signal Sciences, Fastly's Next-Gen WAF is designed to protect applications and APIs from attacks like SQL injection, cross-site scripting (XSS), and account takeovers. It differs from traditional WAFs, which often rely on rigid, pattern-matching rules that can generate many false positives and are difficult to maintain. The Next-Gen WAF uses a proprietary technology called SmartParse to analyze the intent of a request rather than just matching signatures. It learns an application's normal traffic patterns to more accurately identify and block malicious activity with a lower rate of false positives. It can be deployed at the edge, on-premise, or in any cloud environment.

DDoS Mitigation: Like other major CDNs, Fastly's large, distributed network provides a first line of defense against Distributed Denial-of-Service (DDoS) attacks. The platform is designed to absorb and scrub large volumes of malicious traffic at the network edge, preventing it from ever reaching the customer's origin server. This service is always-on and protects against volumetric attacks at layers 3, 4, and 7 of the OSI model.

Observability

A core tenet of Fastly's platform is real-time visibility. The company offers real-time log streaming, allowing customers to send detailed logs of every request to a wide variety of third-party endpoints, such as Amazon S3, Google BigQuery, or Datadog. This provides immediate insight into traffic patterns, performance, and potential security threats. The platform also provides real-time analytics and metrics through its API and control panel, giving operators a live view of cache performance, error rates, and other key indicators.

Business Model

Fastly's business model is primarily consumption-based^[8], often referred to as pay-as-you-go. Customers are billed based on their usage, with the two main metrics being bandwidth (data transferred from the edge to the user) and the number of requests. The price per gigabyte and per 10,000 requests decreases as volume increases.

This model offers flexibility, as costs scale directly with traffic. However, it can also lead to unpredictable billing for businesses with highly variable or spiky traffic patterns. Specific products, like the Next-Gen WAF, may be priced differently, often based on a combination of request volume and the number of applications being protected. The company also offers enterprise plans with committed usage rates, dedicated support, and other premium features for its largest customers.

Market Position and Competitors

Fastly is a significant player in the global CDN and edge computing market, but it faces intense competition from both established incumbents and other fast-growing innovators.

Akamai: Founded in 1998, Akamai is the long-standing market leader in the CDN space. It operates one of the world's largest and most distributed networks and has a deep portfolio of enterprise-focused security and delivery products. Akamai is often the choice for large, risk-averse enterprises that require a massive global footprint and a broad suite of managed services.
Cloudflare: A primary competitor, Cloudflare^[9] has built a massive network with a strong focus on integrated security and ease of use. Cloudflare is known for its generous free tier, which has made it extremely popular with individuals and small businesses. Its strategy centers on bundling a wide array of services, including CDN, DDoS protection, WAF, and DNS, into simple, predictable subscription plans. This contrasts with Fastly's more à la carte, usage-based model.
Cloud Providers (AWS, Google Cloud, Azure): Major public cloud providers offer their own CDN and edge services. Amazon Web Services has Amazon CloudFront, Google Cloud has Cloud CDN, and Microsoft has Azure CDN. These services benefit from deep integration with their respective cloud ecosystems, making them a convenient choice for customers already heavily invested in one of these platforms. They are also aggressively expanding their edge computing capabilities, competing directly with Fastly's Compute@Edge.

Fastly's market position is defined by its appeal to a specific segment: technically sophisticated organizations that prioritize performance, programmability, and real-time control. It is often favored by large media companies, high-growth technology firms, and e-commerce platforms where speed and customizability provide a direct competitive advantage.

Strengths and Limitations

Like any technology platform, Fastly has a distinct set of strengths and weaknesses that make it suitable for some use cases and less so for others.

Genuine Strengths

Performance and Speed: Fastly's architecture, built on modern hardware like SSDs and a highly configurable Varnish core, is engineered for low latency and high cache-hit ratios. Features like Instant Purge and real-time configuration changes allow for agile content management that is difficult to achieve on older platforms.
Deep Programmability: The ability to execute custom logic at the edge via VCL and Compute@Edge is Fastly's most powerful feature. It transforms the CDN from a simple caching layer into a distributed application platform, giving developers fine-grained control over traffic and content delivery.
Real-Time Observability: The platform's emphasis on streaming logs and metrics in real time provides unparalleled visibility. This allows DevOps and security teams to monitor performance, debug issues, and respond to threats instantly, rather than waiting for batch-processed reports.
API-First Philosophy: The entire platform is designed to be controlled via a comprehensive API. This makes it easy to integrate Fastly into automated CI/CD pipelines and infrastructure-as-code workflows, a critical requirement for modern engineering teams.

Real Limitations and Criticisms

Complexity and Learning Curve: The same programmability that is a strength can also be a limitation. Mastering VCL requires specialized knowledge, and building applications for Compute@Edge is more involved than using a simple GUI. This can present a steep learning curve for teams without dedicated engineering resources.
Pricing Model Predictability: While the pay-as-you-go model is flexible, it can be a source of financial uncertainty. A sudden traffic spike, whether legitimate or from an attack, can lead to a surprisingly large bill. This contrasts with the fixed-price subscription plans offered by competitors like Cloudflare, which can be more appealing for budget-conscious organizations.
Network Scale: While Fastly's network is powerful and strategically placed, its total number of PoPs has historically been smaller than that of competitors like Akamai and Cloudflare. For instance, while Fastly's total number of PoPs is not consistently reported, Cloudflare's network page stated a presence in 335 cities as of 2026. For applications requiring hyper-local delivery in more remote regions, a network with greater density might offer better performance.
Impact of Outages: The June 2021 outage demonstrated the systemic risk associated with a centralized, software-defined control plane. While Fastly's response was swift and transparent, the event highlighted how a single bug on a major edge platform can have a cascading impact across a significant portion of the internet. This is a risk inherent to all large-scale infrastructure providers, but the incident drew particular attention to Fastly's role in the internet's ecosystem.

Decision Lens for Technical Leaders

When evaluating Fastly, technical leaders should weigh the tradeoffs between control, performance, complexity, and cost.

Who is it a good fit for?

Fastly is an excellent choice for organizations where web and application performance is a primary business driver. This includes:

High-traffic media and publishing companies that need to deliver dynamic content and video streams with low latency and manage complex caching rules.
E-commerce and retail platforms where every millisecond of delay can impact conversion rates and revenue.
SaaS and technology companies that want to use the edge as a programmable layer for their applications, offloading logic from their origin servers to improve user experience and reduce infrastructure costs.
Organizations with strong DevOps and engineering teams that have the skills and desire to use a powerful, API-driven platform to its full potential.

Who might it not be a good fit for?

Conversely, Fastly may not be the ideal solution for:

Small businesses, bloggers, or individuals who need a simple, low-cost, or free CDN. The complexity and cost model are not optimized for this segment, which is better served by competitors with free tiers and simple setup wizards.
Teams without the engineering capacity to manage VCL or develop applications for Compute@Edge. The platform's value is maximized when its programmability is used, and organizations unable to do so may be paying for features they cannot use.
Organizations that prioritize predictable, fixed costs over a usage-based model. Companies that need to lock in their infrastructure spending may prefer the bundled subscription plans offered by other providers.

Tradeoffs to Weigh

A technical leader's decision to choose Fastly ultimately comes down to a few key tradeoffs:

Performance and Control vs. Simplicity: Fastly offers superior control and performance for those willing to manage its complexity. The alternative is a simpler, more abstracted platform that may be easier to manage but offers less flexibility.
Usage-Based Cost vs. Fixed Subscription: The pay-as-you-go model can be more efficient if traffic is well understood and optimized, but a fixed subscription provides budget certainty. The choice depends on the organization's traffic patterns and tolerance for financial risk.
Best-of-Breed Component vs. Integrated Suite: Choosing Fastly often means adopting a best-of-breed component for delivery and edge compute, which is then integrated with other services. This contrasts with an all-in-one provider that offers a more tightly integrated but potentially less powerful suite of tools.

Sources (9)