Runs a global network that delivers websites and content faster by storing copies closer to users and updating those copies in seconds.
Fastly runs a global network of edge servers that intercept web traffic before it reaches a customer's own servers, serving cached content from whichever node is closest to the end user. The caching and routing rules that govern every one of those nodes are written in Varnish Configuration Language, which is wired directly into the cache process itself, so a single rule change — rerouting traffic, purging a stale video segment, rewriting a cache key — reaches every node worldwide in seconds without restarting any server. Because customers embed Fastly's purge API into their own deployment pipelines and encode their routing logic in VCL that no competing CDN can read, switching away means rewriting all of that logic from scratch, which makes the network sticky even without long-term contracts. The same propagation speed that creates that stickiness is also the clearest way the business could break: a misconfigured VCL rule replicates to every node before any circuit-breaker fires, exactly as happened in 2021 when a single bad rule took down major customer websites within minutes.
How does this company make money?
Customers pay based on how much bandwidth they consume and how many HTTP requests Fastly processes on their behalf. On top of that base usage billing, Fastly charges extra for premium features including image optimization, DDoS protection, and access to broader geographic coverage.
What makes this company hard to replace?
Switching away from Fastly means rewriting all of the VCL caching logic and custom traffic routing rules in whatever language or format a different CDN uses — none of it transfers. Fastly's cache-purge API is also embedded directly into customers' own deployment pipelines, so unplugging it means reworking internal engineering tools. On top of that, Fastly's anycast IP addresses are hardcoded into customers' DNS records, and changing DNS records takes time to propagate across the internet, creating a gap window with no clean fallback.
What limits this company?
The main bottleneck is the cache hit ratio — how often a node can answer a request from its local copy rather than fetching fresh content from the origin server. When the cache misses, the latency and bandwidth cost the customer is paying to avoid comes straight back. Hit ratio depends on how quickly stale content gets purged: a slow or missed purge forces the next request for that content to go all the way to origin anyway.
What does this company depend on?
Fastly cannot operate without Varnish Cache, the open-source software that powers its HTTP acceleration. It also relies on data center colocation agreements in major cities around the world to physically house its edge nodes, BGP anycast routing infrastructure to direct user traffic to the nearest node, TLS certificate authorities to handle secure HTTPS connections, and transit and peering agreements with major ISPs to move traffic across the internet.
Who depends on this company?
E-commerce platforms rely on Fastly during traffic spikes — without it, slow page loads would cause shoppers to abandon their carts. Media streaming services would see buffering and worse video quality during peak viewing times. Mobile apps that call APIs for critical actions like payments or logins would time out. Financial trading platforms would lose the microsecond speed advantages they depend on for order execution.
How does this company scale?
Once content is cached at one edge node, copies can be spread to additional nodes cheaply — that part scales well. What does not scale easily is expanding raw network capacity at internet exchange points. Adding physical fiber connections and negotiating peering relationships with ISPs has to be done one deal at a time and cannot be automated, so capacity growth in any given location is slow and manual.
What external forces can significantly affect this company?
Data sovereignty laws in some countries require certain content to stay within their borders, which limits where Fastly can optimally place its caches. Submarine cable cuts from earthquakes or storms can force traffic onto slower, longer routes. Central bank digital currency systems being developed by some governments may require real-time transaction checks that are fundamentally incompatible with the way caching works, which could exclude Fastly from serving parts of that infrastructure.
Where is this company structurally vulnerable?
Because VCL changes replicate instantly to every node with no circuit-breaker in the way, a single bad rule goes everywhere before anyone can stop it. This already happened in 2021, when one misconfigured VCL rule took down major customer websites simultaneously within minutes. If a future incident like that hit financially regulated or safety-critical customers, the resulting liability claims or regulatory pressure could force Fastly to slow down its propagation model — which would destroy the sub-second update speed that the whole product is built around.
Sign in to view price data.
Sign inStructural observations derived from financial data, industry benchmarks, and supply chain position.
Companies that share the same coordination system — how they create, deliver, or capture value.
Companies that share active interpretations — structural patterns currently present in both stocks.
CompanyGraph