Akamai Functions
LeaderAt Akamai, we make life better for billions of people, billions of times a day
Est 1998|Valuation $16.6B|Raised $361.8M
At Akamai, we make life better for billions of people, billions of times a day
Published Oct 22, 2026
No public, Functions-specific roadmap with dates was identified in the sources reviewed. Buyers should request roadmap and product maturity details during procurement.
Akamai Functions is relatively new and does not appear to have many product-specific reviews on major review platforms under that exact product name. Most third-party reviews found are for Akamai broadly (CDN/security), Akamai Cloud Computing (Linode/Akamai Connected Cloud), or Akamai EdgeWorkers (an adjacent edge compute product). This makes independent, product-specific customer signal for Functions limited.
Gartner’s vendor review portal contains reviews across Akamai’s product set, but there was not an identifiable Functions-specific corpus available in the public sources reviewed for this report.
Because Functions-specific reviews are sparse, the available community signals pertain to broader Akamai product experience and EdgeWorkers. Common themes in community discussions include concerns about pricing opacity and the perception that Akamai products can be more complex and enterprise-focused compared with some developer-first platforms.
From reviews of adjacent Akamai products and ecosystem commentary:
Note: These points are not specific to Akamai Functions unless confirmed directly.
Common themes from community and review commentary (not Functions-specific):
Industries where Akamai has considerable presence and where Functions may be relevant include:
Get a comprehensive analysis of Akamai Functions including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →Small teams or startups that require self-serve onboarding and transparent, unit-based pricing are likely to prefer cloud platforms that publish unit costs and provide free trial tiers.
Workloads that require integrated, platform-managed stateful compute primitives for transactional consistency may be better served by platforms that advertise those primitives.
Teams that cannot adopt Wasm toolchains or do not want to introduce cross-compilation steps (for example, teams that rely exclusively on Node.js without cross-compilation) may prefer platforms with native JavaScript runtimes.
Organizations that need the simplest possible procurement and minimal platform complexity for small-scale deployments may find single-vendor, developer-oriented platforms easier to adopt.
G2 reviews for Akamai EdgeWorkers indicate limited review volumes, and some reviewer feedback points to platform constraints such as limits on the number of EdgeWorker scripts executed per request and rate limits for certain operations.
G2 reviews for Akamai Cloud Computing include reviewer comments that reference reliability, global performance, documentation, and support responsiveness, but these comments relate to IaaS/VPS/managed services rather than Functions and should not be treated as Functions-specific evidence.
Caution on review platforms: community discussions note that some review platforms may include incentivized reviews or other noise; reviews should be weighed alongside direct references, community forums, and vendor-provided evidence.
Akamai and partner materials describe a Fermyon case that demonstrates using Wasm tooling (Spin) to deploy functions on Akamai’s platform. These partner-published materials illustrate an intended integration pattern and tooling compatibility.
Critical evaluation:
Akamai describes use cases such as mass redirects, token management, bot management, and personalization with KV-backed lookups. The vendor asserts low-latency behavior for these patterns; however, independent benchmarks — including detailed high-percentile latency measurements and cold-start behavior under defined conditions — were not located in the public materials reviewed.
Critical interpretation: redirect, token, and bot logic implemented at the edge are consistent with edge compute strengths, but buyers should request measured latency distributions, concurrency behavior, and pricing/cost examples under expected traffic patterns.
Akamai Functions is Akamai’s serverless compute offering designed to run WebAssembly (Wasm) functions across Akamai’s distributed edge/cloud footprint. The core proposition is to execute application logic closer to end users (often in the request/response path), with very short startup times and reduced need to manage regions, servers, containers, or global scaling operations. Akamai markets the product for modern applications and AI-related tasks, and emphasizes reduced latency, global distribution, and portability through WebAssembly/WASI standards.
Akamai differentiates Functions from its older edge compute product EdgeWorkers: EdgeWorkers provides JavaScript-based CDN logic, while Akamai Functions provides a WebAssembly runtime intended for broader application logic, APIs, and some AI workflow components.
Key vendor-stated attributes (note: vendor claims, not independently benchmarked in this research):
Positioning: Marketed toward enterprise customers as an edge/serverless compute option for teams already using (or considering) Akamai for CDN, security, and traffic management—particularly those seeking:
Likely buyers include platform engineering, SRE/platform teams, security engineering teams (token/bot/auth logic), and performance teams at mid-market to large enterprises.
Common edge-compute alternatives used by developers (based on market observations): Cloudflare Workers, Fastly Compute (Compute@Edge), Vercel Edge Functions, AWS Lambda@Edge / CloudFront Functions.