Akamai EdgeWorkers

HostedEdge runtime

Execute code on any edge server on demand, with an extremely fast cold-start time with V8 isolates

Homepage Docs Pricing Repository

Scanned 14 Oct 2026 · Schema v5 · features v21

From: Free
Enterprise contract / usage-based. EdgeWorkers pricing is NOT publicly disclosed — contact Akamai account representative for billing rates. Three resource tiers (Basic, Dynamic, Enterprise) with different billing rates. A free Evaluation Tier exists for testing.
Free tier: Yes
Evaluation Tier available (free, confirmed via techdocs: 'confirm the price (free), and review and accept the Terms and Conditions to proceed'). Limited to contract evaluation; not a production free tier.
Isolation: V8 isolate
shares the host process
Regions: 1
Global; exact EdgeWorkers PoP/country count not freshly disclosed
Capabilities: 10 / 61
6 partial · 41 fail · 0 not assessed
Agent readiness: 8/11 · 7/11
read · drive, pre-login surface

Advertised for

EdgeWorkers functions (V8 isolate JS/TS serverless at CDN edge) · EdgeKV data reads/writes (companion edge KV store) · HTTP sub requests (upstream fetch from edge function) · ResponseProvider (full response generation, streaming) · SubWorkers (nested function composition — up to 2 level tree)

Built for

Technical, then developers

· Onboarding requires enterprise contract + Akamai CLI or REST API — no self-serve wizard
· Pricing not publicly disclosed — enterprise sales motion
· Hero content on product page emphasizes edge execution, V8 isolates, cold start time

01 Pricing Enterprise contract / usage-based. EdgeWorkers pricing is NOT publicly disclosed — contact Akamai account representative for billing rates. Three resource tiers (Basic, Dynamic, Enterprise) with different billing rates. A free Evaluation Tier exists for testing.

Tier	EntryEvaluation Tier	Basic Compute	Dynamic Compute	TopEnterprise Compute
Price	Free	Enterprise contract — contact sales	Enterprise contract — contact sales	Enterprise contract — contact sales
Includes	For testing only; limited to staging/evaluation contract. Not for production traffic.	10ms CPU/handler, 1.5MB memory, 2 HTTP sub-requests, 4s wall time	20ms CPU/handler, 2.5MB memory, 4 HTTP sub-requests, 5.5s wall time. Default tier.	70ms CPU/handler, 4MB memory, 10 HTTP sub-requests, 10s wall time, 300ms init CPU

Free tier: Evaluation Tier available (free, confirmed via techdocs: 'confirm the price (free), and review and accept the Terms and Conditions to proceed'). Limited to contract evaluation; not a production free tier.

Million events invoked; count each event executed for traffic during the month. Rates differ by resource tier and are available from the account representative.·Card required: unconfirmed·Not publicly disclosed. Enterprise contract terms govern overages.·techdocs.akamai.com

02 Website design Desktop public website · assessed 14 Oct 2026

Complete assessment.

Dark marketing hero with blue digital imagery and orange call-to-action contrasts with white, dense sidebar-led technical documentation.

Corporate
Technical illustration

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

V8 isolateshares the host process

Persistence

Stateless — EdgeWorkers functions are ephemeral; no persistent local disk between requests. Durable state lives in EdgeKV (edge-resident key-value store, a companion product) or in origin. No persistent filesystem.

Snapshots / forks

No snapshot or fork primitive for running EdgeWorkers instances. EdgeWorkers are stateless; no copy-on-write or memory-checkpoint capability is documented.

Resources & limits

Storage

EdgeKV — first-party edge-resident key-value store tightly integrated with EdgeWorkers (companion product; requires separate add-on to contract). No block storage or persistent disk. No object storage directly accessible from EdgeWorkers functions (would require HTTP sub-request to Akamai Cloud / external).

Limits & quotas

Three resource tiers — Basic, Dynamic (default), Enterprise. CPU: 10ms/20ms/70ms per standard handler; 60ms–300ms init. Memory: 1.5MB/2.5MB/4MB per handler. Wall time: 4s/5.5s/10s. HTTP sub-requests: 2/4/10 concurrent. Code bundle: 512KB compressed, 1MB uncompressed. Max 200 EdgeWorker IDs/account, 1000 versions/ID, 20 activations/min, 500/day. Cold start < 5ms. responseProvider differs: Basic/Dynamic/Enterprise CPU 100/200/300ms, memory 2/4/6MB, wall 4/8/10s, 50 total subrequests and 5/5/10 parallel. respondWith body limit is now 16,384 characters.

GPU

No GPU available in EdgeWorkers. EdgeWorkers is a JavaScript-only serverless FaaS; no GPU-backed instances are offered on this SKU. GPU/ML workloads would require Akamai Cloud Computing (Linode) separately.

Access

Deploy interface

Three interfaces: (1) Akamai CLI (`akamai install edgeworkers` + `akamai edgeworkers` commands — register, upload, activate, test); (2) EdgeWorkers Management Application (GUI in Akamai Control Center); (3) EdgeWorkers REST API v1 (OpenAPI spec at github.com/akamai/akamai-apis/apis/edgeworkers/v1/openapi.json, 619KB). Terraform provider also available (akamai_edgeworkers_resource_tier resource documented in techdocs).

SDK languages

JavaScriptTypeScript

Network & secrets

Egress controls

HTTP sub-requests from EdgeWorkers functions are allowed but limited by tier (2–10 concurrent, 4–10s wall time). No documented per-function outbound allowlist/firewall for blocking arbitrary egress. Sub-request response size capped (5MB Basic/Dynamic, 8MB Enterprise). Platform-level Akamai WAF/security applies but is not a per-function egress control.

Secrets

No first-party secrets management documented for EdgeWorkers specifically. Environment variables and Property Manager variables are available (max 1024 chars, up to 4000 with approval). EdgeKV can be used for token/secret storage. No dedicated vault or secrets injection product analogous to Cloudflare Secrets Store.

Bring your own cloud

No. EdgeWorkers runs exclusively on Akamai's own global edge network. No bring-your-own-cloud option exists for EdgeWorkers.

Placement & use

Jurisdiction

Global anycast across Akamai's 4,300+ PoP network in 130+ countries. No documented per-request jurisdiction pinning for EdgeWorkers (unlike Cloudflare's Data Localization Suite). Enterprise customers may negotiate contractual data residency. EdgeWorkers is NOT supported on China CDN.

Advertised workloads

EdgeWorkers functions (V8 isolate JS/TS serverless at CDN edge)EdgeKV data reads/writes (companion edge KV store)HTTP sub requests (upstream fetch from edge function)ResponseProvider (full response generation, streaming)SubWorkers (nested function composition — up to 2 level tree)

04 Capabilities 10 pass · 6 partial · 41 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 2/10

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Not supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not applicable

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 3/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Not supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Partially supported

Developer access 4/9

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Not supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not applicable

AI & agents 0/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Not supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Not supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 0/2

First-party databasePlatform-provided managed database.

Partially supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not applicable

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not applicable

Platform & operations 0/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Partially supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 1/9

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Not supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Not supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

8/11

7 full · 2 partial · 73% of applicable checks

llms.txt
Supported
“https://techdocs.akamai.com/edgeworkers/llms.txt provides guide, API and changelog indexes; guide links resource-tier billing.”
llms-full.txt
Not supported
“Apex llms-full.txt returns rendered HTTP 404; docs llms.txt is an index, not full text.”
robots.txt AI policy
Supported
“https://www.akamai.com/robots.txt explicitly allows GPTBot, ClaudeBot, ChatGPT-User, Google-Extended, PerplexityBot and other AI UAs with Allow: /.”
JSON-LD
Partially supported
“Rendered product HTML contains four application/ld+json scripts; no priced offers verified.”
Sitemap
Supported
“robots.txt points to https://www.akamai.com/sitemap-index.xml; sitemap.xml and index fetched successfully.”
Meta tags
Supported
“Rendered HTML includes product-specific title, description and Open Graph metadata.”
Markdown negotiation
Supported
“techdocs.akamai.com serves .md URLs natively (e.g. /edgeworkers/docs/resource-tier-limitations.md returns clean markdown). Docs subdomain earns credit.”
Content efficiency
Supported
“Rendered HTML 461686 bytes; non-script/style text fraction 0.1539 (>5%).”
Docs discoverable
Supported
“ora: 'Documentation site found at https://developers.akamai.com' (scored public_api 3/3). techdocs.akamai.com is first-class. developers.akamai.com links prominently from public surface.”
Machine-readable pricing
Not supported
“Resource tiers are documented but all monetary rates require contact with account representative.”
No anti-bot wall
Partially supported
“Direct curl receives 403 on marketing pages/well-known probes; anonymous rendered landing succeeds. Blocking is intermittent/path-dependent, not a robots prohibition.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

7/11

6 full · 2 partial · 64% of applicable checks

Public API
Supported
“EdgeWorkers REST API v1 fully documented at techdocs.akamai.com/edgeworkers/reference. Multiple REST endpoints (contracts, groups, IDs, versions, activations, resource-tiers, limits, secure-tokens, validations).”
OpenAPI spec
Supported
“Fetchable OpenAPI spec at github.com/akamai/akamai-apis/blob/main/apis/edgeworkers/v1/openapi.json (~619KB). Apache-2.0 licensed. Comprehensive spec covering all EdgeWorkers management endpoints.”
MCP server
Not supported
“No current supported EdgeWorkers-specific MCP evidence in guide/API indexes; vendor-wide endpoint blocked, OAuth metadata 404.”
SDK packages
Partially supported
“JavaScript runtime modules and TypeScript declarations documented; two language syntax surfaces are not multiple official SDKs.”
Auth documented
Supported
“https://techdocs.akamai.com/developer/docs/edgegrid.md documents HMAC-SHA-256 authentication, basic/managed/advanced scoped clients and request signatures.”
Self-serve credentials
Partially supported
“Existing account user creates API client in Control Center and downloads .edgerc; no programmatic initial key issuance documented.”
Webhooks
Not supported
“ora: 'No webhook system found.' No webhooks documented for EdgeWorkers event subscriptions.”
CLI tool
Supported
“Official cli-edgeworkers release 1.19.0 fetched via GitHub releases API.”
Error model
Supported
“https://techdocs.akamai.com/edgeworkers/reference/api-errors.md documents error JSON and HTTP statuses.”
Rate limits documented
Supported
“https://techdocs.akamai.com/edgeworkers/reference/resource-limiting.md documents 429 and *-Limit, *-Remaining, *-Reset headers, with default values.”
Agent config files
Not supported
“No agents.md, /.well-known/agent, or agent skills listings found. ora: 'Could not locate a public repo containing agent configs or rules.' Enterprise CDN company — agent-config surface is thin.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 0

The public surface names no coding harness as supported or documented-to-run-here.

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 0

No attestations found on the public surface. Empty means nothing is advertised, after checking, not that nothing was checked.

Regions 1

Global; exact EdgeWorkers PoP/country count not freshly disclosedAkamai global edge network

Product limits exclude regional/governmental CDNs. Cloud Computing datacenter regions are a separate SKU.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: Cambridge, Massachusetts, USA
Founded: 1998 (IPO 1999, NASDAQ: AKAM)
Team size: Large public company; exact current headcount not verified.
Hiring: Hiring (public careers board at akamai.com/careers).

Activity

Last release: cli-edgeworkers 1.19.0 github.com
Last blog post: 2026-10-13 (company blog listing; not an EdgeWorkers-specific release) akamai.com

Presence 9

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from akamai.com's unauthenticated pages, docs, pricing and repository on 14 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Edge runtime products →