Fastly Company Overview

As of August 13, 2026, Fastly, Inc. is an independent Delaware public company listed on Nasdaq as FSLY and headquartered in San Francisco. It began in 2011 as SkyCache and now operates a global edge-cloud platform spanning content delivery, application and API security, programmable compute, and observability. Fastly frames its purpose around improving human lives through its work, supported by published values emphasizing customers, curiosity, trust, integrity, competitiveness, transparency, passion, and good conduct. Shareholders own the company; an independent chair oversees a management team in which founder Artur Bergman remains CTO and a director. Fastly monetizes primarily usage and contracted services, reaching digital enterprises and developers through direct sales, self-service, partners, resellers, and cloud marketplaces. It competes with Akamai, Cloudflare, hyperscale clouds, security specialists, and customer-built alternatives. CEO Kip Compton is pursuing expansion through existing accounts, security and compute, AI-related workloads, partners, and international reach. Its core capability is a programmable, observable edge; material constraints include usage volatility, customer concentration, infrastructure capacity, and third-party networks. Evidence was checked through August 13, 2026 using Fastly’s 2025 Form 10-K, 2026 proxy, and leadership page.

Fastly’s history is a sequence of scope expansions: Artur Bergman founded the business in 2011, the company moved from the SkyCache name to Fastly in 2012, listed publicly in 2019, then used product development and acquisitions to extend beyond content delivery into security, edge compute, developer tooling, and a broader platform strategy.

The legal origin is unusually clear. Fastly’s filing history says the company was incorporated in Delaware in March 2011 as SkyCache, Inc. and changed its name to Fastly, Inc. in May 2012. Its investor FAQ records the May 17, 2019 initial public offering, when Class A shares began trading on Nasdaq under FSLY. Those dates distinguish founding, naming, and public-company status rather than collapsing them into one “launch” event.

History is supported by the investor FAQ, the 2020 Form 10-K for Signal Sciences, the 2022 full-year release for Glitch, and the 2026 proxy for the CEO transition.

Fastly’s official materials emphasize an aspiration rather than relying on a separately labeled mission-and-vision pair: the company says technology can improve human lives and that it aspires to do so through its work. Its published values then convert that broad purpose into behavioral expectations around customers, curiosity, trust, integrity, passion, competition, transparency, and being good people.

That purpose is consistent with how Fastly describes product design. The company repeatedly emphasizes giving developers and operators more control, enabling experimentation, exposing real-time information, and making applications resilient and secure. Its evidenced long-term direction is to make the integrated edge platform accessible to a broader customer base and expand the workloads customers can run on it. The strategy also complicates the idealistic language in a useful way: Fastly is a commercial infrastructure provider, so its purpose has to coexist with reliability commitments, disciplined economics, enterprise procurement, and security obligations.

What aspiration anchors the company?

Fastly states that technology can improve human lives and that it aspires to improve them through its work, connecting the corporate purpose to the quality, safety, and usefulness of digital experiences.

How do the values constrain execution?

Customer focus, integrity, trust, transparency, curiosity, passion, competitiveness, and good conduct establish a behavioral test for decisions that otherwise could be judged only by speed, growth, or technical performance.

Fastly’s aspiration appears in its 2025 Form 10-K; its named values are published on the careers and values page.

The platform thesis is that delivery, protection, programmable logic, and telemetry become more useful when they operate close to users and share one edge architecture. Fastly can therefore address several steps in the same application request path, while customers can reduce handoffs among point products and keep developers closer to performance and security decisions.

Network Services includes CDN and adjacent delivery capabilities such as dynamic site acceleration, origin shielding, instant purge, and reliability features. Security covers web and API protection, DDoS defense, bot management, TLS, and client-side protections. Compute runs customer logic in isolated WebAssembly-based environments, while observability exposes logs and metrics across delivery, compute, and security. The integration is commercially important because it lets Fastly expand from an initial workload into additional use cases without requiring an entirely separate platform relationship.

What makes the integrated edge model consequential?

The architecture places multiple controls on the same request path, so performance optimization, application logic, threat response, and telemetry can be coordinated at the edge instead of being assembled only after traffic reaches origin infrastructure.

• Network Services accelerates and routes content close to users.
• Security inspects and mitigates threats before origin exposure increases.
• Compute executes programmable application logic in isolated edge environments.
• Observability feeds operators real-time service, traffic, and security signals.

Product scope and architecture are documented in Fastly’s product portfolio, Compute page, and observability metrics page.

Fastly is owned by its public shareholders, not by its founder, CEO, board, or Nasdaq. Its 2026 proxy shows one vote per outstanding common share and no Class B shares entitled to vote at the April record date. Large institutions hold meaningful blocks, but the disclosed ownership picture does not identify a single controlling shareholder.

Beneficial-ownership tables require date discipline. Fastly’s proxy was prepared in 2026, yet some institutional positions were taken from earlier Schedule 13G filings. The table below therefore reports exactly what the proxy presented and preserves each underlying position date instead of treating those percentages as a real-time cap table. Founder Artur Bergman’s proxy-reported stake is materially smaller than the largest institutional block and does not confer majority control.

Governance is deliberately separated from day-to-day management. The proxy says seven of nine directors were independent under Nasdaq rules and identifies David Hornik as independent chair, while Compton and Bergman are not independent because of their executive roles. The board oversees strategy and major risk categories; executives are responsible for operating the business. That distinction matters because institutional share ownership, board oversight, and executive authority are three different forms of influence.

Fastly monetizes a technical value flow rather than a consumer audience: customers route traffic, security inspection, or application logic through its platform; usage and contracted services are measured; Fastly bills according to consumption, commitments, subscriptions, and selected fixed-rate services. The model creates expansion upside when customer traffic or product adoption rises, but also makes demand variability economically important.

Network Services fees are tied primarily to committed or actual data transfer and requests. Security revenue is more subscription-oriented, often under annual contracts billed in advance, while larger customers frequently have minimum billing commitments plus variable usage above those levels. Fastly also earns fixed recurring revenue from security and other services. In 2025, the company said substantially all revenue was platform-related and that the great majority remained usage-driven, which means gross profit depends on both revenue growth and the cost of carrying a high-capacity global edge.

The value flow and contract mechanics are described in Fastly’s 2025 Form 10-K.

The cost side is infrastructure-heavy. Fastly identifies bandwidth from network providers, colocation, network operations, support, storage, managed services, depreciation, and internal-use software amortization among the main costs of revenue. Because bandwidth and colocation capacity cannot always be reduced at the same speed as customer usage, traffic changes can affect margins differently from a conventional seat-based software model.

Fastly is aimed at organizations for which web and application performance, resilience, security, or programmable edge logic are operationally important. Developers and engineering leaders can champion the technology, security and platform leaders shape product choice, and commercial buyers authorize contracts. Fastly reaches them through direct enterprise selling, developer-led self-service, partners, resellers, managed-service providers, and cloud marketplaces.

In role terms, developers, site-reliability engineers, and security practitioners are typical users and evaluators; engineering, platform, and security leaders can act as choosers; procurement and finance functions help authorize and pay for enterprise contracts; and the customer’s own end users benefit from faster, safer, more resilient digital services. In smaller self-service accounts, the technical user can also be the buyer.

The direct-sales motion is geographically organized and explicitly described as “land and expand”: an initial deployment proves value, then account teams seek more traffic, products, workloads, or business units. Fastly also uses free accounts and developer experiences to lower the technical trial barrier. Partner routes include referrals, resellers, MSPs and MSSPs, while AWS and Google Cloud marketplaces add procurement paths and co-selling opportunities. Customer support runs globally across North America, EMEA, and APAC, which matters because support quality can influence renewal and expansion in mission-critical infrastructure.

Retention is economic as well as relational. Customers can start with smaller deployments and increase usage if performance, security, and developer experience justify wider adoption. Yet Fastly also warns that many contracts are relatively easy to shift or terminate and that usage can be reallocated to other providers. The result is a model where technical credibility, support responsiveness, and continuous product improvement are part of retention, not merely post-sale service.

Fastly competes across several overlapping buyer decisions rather than one perfectly bounded market. Akamai and Cloudflare can overlap broadly in delivery, security, and edge compute; hyperscale clouds can bundle CDN and web-security capabilities with broader cloud estates; specialist security vendors overlap on protection; and customers can substitute internal infrastructure or multi-vendor stacks for an integrated edge platform.

The comparison boundary therefore has to be use-case specific. A media company choosing global delivery may evaluate a different set of vendors from a security team buying a WAF, while an application platform team may compare serverless edge-compute options. Fastly itself names competitors across these categories, and Gartner’s current CDN alternatives page independently places Akamai, Cloudflare, Amazon CloudFront, Google Cloud CDN, and Azure Front Door among alternatives to Fastly CDN.

Fastly’s claimed differentiators center on programmability, real-time visibility, performance, developer experience, integrated security, and support. Those are company claims, not universal rankings. The 10-K also supplies the counterweight: some competitors have greater financial resources, larger sales and distribution systems, broader installed bases, or deeper product portfolios. Competitive advantage therefore depends on the customer’s workload and procurement context rather than a single market-wide superiority claim.

Fastly’s current growth model combines deeper adoption by existing customers with product expansion in security and compute, new workloads tied to AI and modern applications, partner-led distribution, vertical selling, and international reach. Recent results show the company entering 2026 with stronger revenue momentum, while management’s full-year outlook remains guidance rather than an achieved result.

The multi-quarter pattern is useful because usage-based infrastructure can be noisy. Quarterly revenue rose across the displayed period, with a particularly visible step-up in late 2025 and another high point in the second quarter of 2026. That progress does not isolate one cause: Fastly attributes growth to customer usage, new product adoption, larger deals, and platform demand, while the reported series itself cannot assign causal weight to any one factor.

Implemented actions in the second quarter included a C++ SDK for Compute, an anti-piracy collaboration with LALIGA, and a Skyfire partnership aimed at trusted AI-agent commerce. Fastly’s Q2 2026 supplement also describes customers expanding or adopting Bot Management, Next-Gen WAF, and resiliency services. These examples show execution against the strategy; they do not by themselves prove what caused the quarter’s revenue growth.

Growth priorities and channel expansion mechanisms are set out in the 2025 Form 10-K.

For full-year 2026, management guided to total revenue of $732 million to $746 million in the August investor supplement. That range is a company forecast, not an actual outcome. Its usefulness is directional: management expects the newer growth trajectory to continue, but fulfillment depends on usage, renewals, product adoption, pricing, customer concentration, infrastructure efficiency, and execution against enterprise sales cycles.

Fastly’s main constraints cluster around three connected systems: customer demand can move faster than committed revenue, the edge platform depends on physical network capacity and third parties, and enterprise growth depends on long technical sales cycles plus reliable support. These dependencies can amplify upside when usage expands, but they can also delay or dilute operating leverage.

The customer side is structurally important. In the 2025 filing, Fastly said its ten largest customers represented roughly one-third of trailing revenue, while many arrangements still allowed usage to shift between providers. That means customer health, workload share, pricing, and traffic patterns matter alongside logo count. A usage-led model can expand efficiently with customers, but it does not provide the same predictability as a fully prepaid seat subscription.

Customer concentration, usage flexibility, bandwidth and colocation exposure, cloud-provider reliance, sales-cycle length, and support dependence are disclosed in Fastly’s 2025 Form 10-K.

Capacity planning adds a second-order constraint. Fastly has to buy or lease infrastructure before demand is perfectly known, and it warns that hardware shortages, delivery delays, outages, or misjudged capacity can affect service quality and economics. The company also competes with some of the cloud providers it relies on. That combination is characteristic of edge infrastructure: the product feels like software to the customer, but delivery still rests on capital, network, facility, supplier, and operational execution.

Fastly’s current operating authority is divided across CEO Kip Compton, founder and CTO Artur Bergman, CFO Richard Wong, and President of Go to Market Scott Lovett. The arrangement separates enterprise-wide accountability, technical architecture, financial stewardship, and commercial execution, while the independent board chair and committees retain oversight rather than running daily operations.

Compton became CEO effective June 16, 2025 after joining Fastly as chief product officer in January 2024; his prior Cisco experience included strategy and business development. Bergman, the founder and former CEO, returned to the CTO role in 2024, preserving technical continuity without combining founder, CEO, and board-chair authority. Wong became CFO in August 2025 after finance leadership roles at Benchling, Houzz, LinkedIn, Yahoo, and investment banking. Lovett became President of Go to Market in August 2025 after serving as CRO, with earlier senior commercial roles at Imperva and Akamai.

Board design supplies the governance counterweight. Independent chair David Hornik can call and preside over board and independent-director meetings and shape agendas. The board oversees strategic, operational, technology, information-security, AI, cybersecurity, and other major risks, while management owns implementation. In practical terms, Compton leads the company, Bergman supplies founder and technical authority, institutional investors exercise shareholder rights, and the independent board oversees rather than substitutes for management.

Fastly today is best understood as a programmable edge infrastructure company in the middle of a commercial broadening: its CDN heritage still anchors the economics, but security, compute, observability, partners, and AI-era workloads extend the platform story. The central management task is to turn that broader technical relevance into durable customer expansion while improving predictability and operating efficiency.

What is Fastly’s core identity?

A developer-oriented edge platform that combines delivery, security, programmable compute, and telemetry close to end users, with public-company governance and a founder who remains technically influential rather than economically controlling.

Where can the model compound?

Existing customers can add traffic and products, while partner channels, international selling, security, compute, and emerging AI workloads give Fastly multiple routes to expand beyond an initial delivery deployment.

What must management balance?

Fastly must pair developer speed and platform breadth with customer retention, infrastructure discipline, resilient third-party dependencies, enterprise sales execution, and governance that converts stronger demand into repeatable rather than merely episodic growth.

This synthesis connects previously cited evidence from the 2025 Form 10-K, Q2 2026 supplement, and 2026 proxy.