(AKAM) Akamai Technologies, Inc. Company Overview

Akamai Technologies, Inc. is a Nasdaq-listed cybersecurity, cloud computing, and content-delivery infrastructure company. It sits between enterprises and the public internet: applications load faster, websites and APIs get protected, and workloads can run closer to users. The company says its platform supports global enterprises across more than 700 cities on Akamai's company overview.

The key point is that Akamai is no longer only a legacy CDN. Security is the largest disclosed revenue category, CIS is the fastest-growing category, and delivery remains important but price-sensitive. The research question is whether Akamai can turn edge scale into durable security and distributed-cloud growth.

What business problem does Akamai solve?

Akamai addresses a structural internet problem: users, applications, APIs, files, and attacks are global, while enterprise infrastructure is often concentrated. Its network shortens distance, absorbs spikes, filters attacks, and routes workloads closer to users. That original performance problem has expanded into security, edge logic, and AI inference.

Which customers and use cases rely on it?

Akamai sells to media, retail, gaming, financial services, healthcare, software, telecom, and public-sector customers. Its company profile says all top 10 video streaming services, all top 10 video game companies, all top 10 banking companies, and all six U.S. military branches use Akamai. That breadth strengthens security intelligence and supports mission-critical contracts.

Akamai primarily sells services under customer contracts that usually run one year or longer. The economic model combines recurring committed revenue, renewals, product cross-sell, and usage-based upside when customers exceed traffic or cloud commitments. In its 2025 annual report, the company says most services are stand-ready obligations recognized over time, generally ratably over the contract term, while usage over a given commitment is recognized when served in the 2025 Form 10-K. That accounting description is useful: Akamai is not a pure consumption-only cloud vendor, and it is not a hardware seller. It is a contracted digital infrastructure service provider.

Which revenue categories are disclosed?

For FY2025, Akamai reported $2.24 billion of security revenue, $1.26 billion of delivery revenue, and $708.1 million of cloud computing revenue. Security grew 10% year over year, cloud computing grew 12%, and delivery declined 5%. Beginning in Q1 2026, Akamai began reporting Cloud Infrastructure Services separately, stating that CIS had become a primary growth area and a significant investment focus within cloud computing. In Q1 2026, CIS generated $94.6 million, or 8.8% of total revenue, but grew 40% year over year.

How does the contract model work?

The strategic tension is visible in that flow: contracted revenue creates predictability, but pricing and renewal pressure can still reduce delivery revenue. Akamai's task is to push customers from mature traffic-delivery use cases into higher-growth security and cloud infrastructure workloads.

The latest official reporting package available as of July 7, 2026 is Q1 2026, covering the quarter ended March 31, 2026. Akamai reported revenue of $1.074 billion, up 6% year over year, and GAAP diluted EPS of $0.71 in the Q1 2026 earnings release.

What changed in Q1 2026?

The growth mix improved while margin pressure became clearer. Security revenue was $589.8 million, up 11%; Delivery and other cloud applications was $389.2 million, down 7%; and CIS was $94.6 million, up 40%. GAAP operating margin was 11%, non-GAAP operating margin was 26%, and adjusted EBITDA margin was 40%.

What does guidance imply?

Akamai guided to Q2 2026 revenue of $1.075 billion to $1.100 billion and FY2026 revenue of $4.445 billion to $4.550 billion. Non-GAAP operating margin guidance was 25% to 26% for Q2 and 26% for FY2026. The implication is that management expects revenue acceleration from the FY2025 baseline, but not a sudden return to older high-margin CDN economics. The transition to cloud infrastructure and AI workloads requires capacity, co-location space, servers, memory, and software investment before the new revenue base fully scales.

Akamai's strategy is a sequence of pivots around one asset: a distributed network built to solve web congestion. The story starts with Tim Berners-Lee's 1995 MIT challenge, Tom Leighton's applied-mathematics work, Danny Lewin's early technical contributions, and Akamai's August 20, 1998 incorporation in the official company history.

1. 1995
   MIT's web-congestion challenge created the technical problem Akamai was built to solve: route and replicate content over distributed servers.
2. 1998
   Akamai was incorporated after the MIT research team explored commercial use of the technology; that became the foundation for CDN scale.
3. 1999
   Akamai went public on October 29, 1999, creating a public capital base for global network expansion.
4. 2013
   Co-founder Tom Leighton became CEO, reinforcing the technical continuity between the original distributed-network algorithms and the later platform strategy.
5. 2023-2024
   Akamai acquired assets and companies including Neosec, Ondat, StackPath customer contracts, Lumen customer contracts, Edgio customer contracts, and Noname Security to deepen API security, compute, and delivery scale.
6. 2025
   The company acquired Fermyon for $56.6 million to strengthen serverless edge functions and reported FY2025 revenue of $4.208 billion.
7. 2026
   Akamai began reporting CIS separately and disclosed a $1.8 billion, seven-year CIS commitment from a leading frontier model provider.

Why did the original CDN invention still matter?

The original CDN insight was distributed control over internet performance. That resource now supports application security, API protection, zero trust, microsegmentation, edge logic, cloud optimization, and AI inference. Akamai's strategic bet is that the bundle is harder to replicate than any one product.

How did security and cloud reshape the mix?

The portfolio changed because delivery became more mature and price-sensitive. Akamai states that delivery revenue has been pressured by downward pricing of renewals, customer cost optimization, and some do-it-yourself behavior by large customers. Security and cloud computing became the growth engines. The result is a company with a profitable installed base, but also a reinvestment challenge: it has to keep the network efficient while funding the capital intensity of AI, cloud, and distributed compute.

Akamai's moat is distributed infrastructure plus trust plus operating intelligence. Its platform is difficult to copy because scale, locations, enterprise integrations, security rules, traffic data, and operational know-how compound over time.

Where does scale show up?

Scale shows up in customer trust, geographic reach, threat data, and cost leverage. Akamai says its platform delivers and secures tens of millions of requests per second to billions of users, which helps explain why large enterprises outsource demanding traffic and security needs.

Where is the moat under pressure?

The moat is not absolute. Customers can multi-source, optimize traffic, or build internal capacity. In delivery, renewal pricing and DIY behavior already pressure revenue. In cloud, Akamai must compete against hyperscalers with much deeper capital resources.

Akamai competes across CDN and edge delivery, application and API security, DDoS mitigation, zero trust, distributed cloud, AI infrastructure, and enterprise services. The main pressure comes from hyperscale cloud platforms, cybersecurity specialists, CDN and edge vendors, telecom providers, start-ups, and large customers that build internal alternatives.

What should students compare?

For strategy work, compare Akamai on platform breadth and capital intensity. Specialists may grow faster in a narrow security niche, while hyperscalers can spend more on infrastructure. The question is whether Akamai's edge-security-delivery bundle creates enough differentiation to offset both pressures.

The most useful Akamai KPIs are not consumer-app metrics such as daily users. They are enterprise infrastructure metrics: solution revenue mix, security growth, CIS growth, delivery renewal pressure, non-GAAP operating margin, adjusted EBITDA margin, capex intensity, operating cash flow, remaining performance obligations, geographic mix, and share repurchases. In Q1 2026, Akamai also disclosed $5.5 billion of remaining performance obligations, with about 50% expected to be recognized over the next 12 months and about 40% over the next two to three years in the Form 10-Q for the quarter ended March 31, 2026.

Which operating metrics matter most?

The geographic mix matters because foreign exchange can affect reported growth, while global demand can diversify customer exposure. Q1 2026 international revenue grew faster than U.S. revenue, but constant-currency growth was lower than reported international growth, so researchers should separate operational demand from currency translation.

Akamai is profitable and cash-generative, but it is not asset-light in the way many software companies are. Its distributed network, cloud infrastructure expansion, co-location commitments, servers, memory, and internal-use software require capital. In FY2025, Akamai generated $1.519 billion of operating cash flow, spent $819.5 million on property, equipment, and capitalized internal-use software, and produced an approximate cash-basis free cash flow of $699.3 million before acquisitions, financing, and marketable-securities activity. That is strong cash conversion, but the margin profile depends on disciplined infrastructure spending.

What is the cash-flow conversion signal?

The cash-flow bridge also explains why capex intensity matters in valuation. A higher-growth cloud infrastructure business can lift revenue, but if capacity must be built well before utilization, free cash flow can lag revenue. Akamai's Q1 2026 cash from operations was $312.5 million, while purchases of property and equipment plus capitalized internal-use software were $191.8 million on the cash-flow statement. That leaves about $120.7 million of cash-basis free cash flow for the quarter before financing choices.

How much balance-sheet flexibility does Akamai have?

At March 31, 2026, Akamai had $1.7 billion of cash, cash equivalents, and marketable securities, $11.646 billion of total assets, $6.737 billion of total liabilities, and $4.108 billion of convertible senior notes on the balance sheet. The company also had no outstanding borrowings under either its $150 million uncommitted 2025 credit agreement or its $1.0 billion 2022 revolving credit agreement as of March 31, 2026. The balance sheet is not distressed, but it is meaningfully levered through convertible notes, so investors should monitor dilution mechanics, note maturities, and buyback timing.

Akamai has a dispersed public-company ownership profile rather than a founder-controlled dual-class profile. The 2026 proxy statement reports that, as of February 20, 2026, there were 145,013,967 common shares outstanding. Vanguard beneficially owned 18,376,759 shares, or 12.7%; BlackRock beneficially owned 10,026,738 shares, or 6.9%; CEO and co-founder Tom Leighton beneficially owned 2,759,456 shares, or 1.9%; and all executive officers and directors as a group owned 3,317,206 shares, or 2.3% in the 2026 proxy statement.

What does the shareholder base signal?

Because Akamai is not controlled by one founder, family, or sponsor, capital allocation is more exposed to public-market discipline. Management can invest in CIS and security, but it must also justify margins, buybacks, dilution, and acquisitions to institutional investors. The proxy also shows that compensation metrics emphasize revenue adjusted for foreign exchange, non-GAAP EPS, and non-GAAP operating income, which signals that leadership is being measured on growth and profitability rather than revenue alone.

How does capital allocation show up?

Akamai does not currently pay a dividend. Instead, it uses operating cash flow for infrastructure investment, acquisitions, debt management, and share repurchases. In May 2024, the board authorized a $2.0 billion repurchase program through June 2027. The company repurchased 10.0 million shares for $800.0 million in FY2025 and another 2.0 million shares for $205.9 million in Q1 2026. At March 31, 2026, $974.6 million remained available under the authorization.

Akamai's opportunity set is unusually clear: security is large, CIS is small but growing rapidly, AI inference could validate distributed cloud economics, and the installed delivery customer base creates cross-sell potential. The risks are equally concrete: delivery pricing may keep declining, cloud capacity may require heavy capital before utilization, hyperscalers may raise input costs or compete directly, and cybersecurity/regulatory failures could damage trust.

Which risks come directly from filings?

These are not generic technology risks. They map directly to Akamai's model: the company sells trust, scale, security, and availability, so a major outage or security failure would affect more than one product line. Conversely, if Akamai proves that distributed AI inference can be sold profitably at scale, the market may view the platform as more than a mature CDN-plus-security business.

Akamai is a useful DCF case because the revenue line and the free-cash-flow line can tell different stories. Revenue growth is supported by security, cloud, international expansion, and contracted RPO. Free cash flow depends on whether Akamai can grow CIS without permanently raising capex and depreciation faster than revenue. In a DCF model, the most important assumptions are not simply next year's revenue growth; they are security durability, CIS scale economics, delivery decline, capex intensity, and terminal margin.

Which drivers belong in a DCF?

A practical model should separate at least three growth lines. Security deserves a moderate growth and margin profile because it is large and strategic. Delivery deserves a cautious decline or low-growth profile because the company has disclosed pricing and traffic pressure. CIS deserves a higher-growth profile, but with heavier reinvestment and execution risk. The $1.8 billion CIS commitment supports visibility, yet a seven-year commitment should not be valued as immediate revenue or immediate free cash flow.

A comparable-company analysis should also avoid treating Akamai as only a CDN or only a cybersecurity company. Its revenue base is blended. The right peer interpretation changes depending on which part of the mix is most important: security revenue supports a cyber-infrastructure multiple, delivery pulls toward a mature network-services multiple, and CIS adds a distributed cloud and AI-infrastructure option.

Akamai is a transition story built on real infrastructure. Its historic CDN network created scale, trust, and routing expertise; the current strategy is to convert that base into security and distributed cloud growth. Q1 2026 supported the direction with 11% security growth and 40% CIS growth, but GAAP operating margin fell to 11% and capex stayed material.

For students, Akamai is a useful case in repositioning a mature core toward adjacent growth. For investors, the question is whether valuable edge assets can generate higher growth without permanently lower free-cash-flow conversion. That tension belongs at the center of any DCF model or strategy framework.