Akamai: Cloud, CDN, Edge Computing & Security

Akamai’s cloud computing, CDN, media delivery, EdgeWorkers and security products explained, including how cloud hosting differs from edge delivery.

Updated 8 September 2026

Akamai’s role in website delivery

Akamai provides an edge network that can deliver content on behalf of an origin. Its delivery configuration describes how a website’s hostnames map to that network and how edge servers handle requests. Property Manager is the tool used to define that behaviour; the available capabilities depend on the purchased product and modules.

For a site with several kinds of traffic, the useful question is what each route requires. A software download, a public landing page and an account endpoint have different freshness and forwarding requirements, even when they share a domain.

Properties, edge hostnames and rules

An Akamai property combines an edge hostname with traffic options and business rules. The rules control how content is retrieved from an origin and distributed to visitors. This makes the property a significant part of the site’s production configuration, alongside the application itself.

For example, a team might want long-lived delivery for versioned assets but rapid updates for editorial pages. That distinction should be expressed and tested in the delivery configuration rather than left to assumptions about a file extension.

Akamai Cloud: compute, storage and networking

Akamai also operates a cloud computing platform, built on the Linode product family. It offers virtual machines, managed Kubernetes, object and block storage, managed databases and networking services. These run application workloads and persistent data, expanding Akamai’s role beyond delivering content from somebody else’s origin.

A team can use cloud instances for an API, Kubernetes for container orchestration and object storage for assets. Those resources have their own provisioning and operating model; configuring a CDN property does not automatically provision a cloud application.

EdgeWorkers, EdgeKV and serverless development

EdgeWorkers runs JavaScript within Akamai’s edge delivery request lifecycle. It supports logic such as request routing and response personalization. EdgeKV provides data access for those functions. Akamai Functions is a separate serverless offering with a different execution model; it should not be treated as another name for EdgeWorkers.

Application, API and enterprise security

Akamai’s security portfolio includes App & API Protector, API Security and Prolexic DDoS protection. Guardicore Segmentation focuses on limiting communication and lateral movement within enterprise environments. These serve different security layers, from a public application endpoint to internal workloads.

Media delivery and programmable CDN operations

Adaptive Media Delivery addresses streaming workloads, while other delivery services handle websites, APIs and downloads. Property Manager and cache purging are operational tools within that delivery platform. A streaming service may therefore use Akamai for media distribution while its user accounts run on a different backend.

Preparing an Akamai rollout

Treat origin settings, certificates and rule activation as separate deployment steps. A DNS change can be correct while an origin hostname or certificate setting is wrong. Test the actual public hostnames, redirects and authenticated routes before switching traffic.

When comparing delivery options, map the required behaviours to the specific Akamai product being considered. A feature described in the documentation may require a module that is not enabled for that account.

How DNSTrace.dev detects Akamai

Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.

akamai-grn — A global request number identifying the edge transaction.
x-akamai-request-id — Per-request identifier on many configurations.
x-akamai-transformed — Set when Akamai has modified the payload, for example by compressing images.
server: AkamaiGHost — The Akamai Global Host process.
server-timing containing ak_p — Akamai edge timing metrics.
CNAME chains ending in edgekey.net or akamaiedge.net — The standard Akamai delivery mapping.

What a detection proves

The hostname is delivered through Akamai, and the response was served by an Akamai edge server.

What it does not prove

Which origin Akamai forwards to, or whether the customer also uses another CDN for other paths. Akamai configurations frequently omit identifying headers entirely, so absence is not evidence of absence.

Common questions about Akamai

What is an Akamai property?

A property is the delivery configuration that associates hostnames with traffic and content-handling rules. It tells Akamai’s edge how to retrieve and serve the site’s content.

Why does an Akamai site sometimes return no Akamai headers?

Akamai lets customers suppress its identifying headers. When they are absent, the CNAME chain and the announcing network remain the usable evidence.

What is an edgekey.net hostname?

It is the Akamai edge hostname a customer's own name is aliased to. Resolving it returns the edge server chosen for the querying resolver's location.

Edge cloud and CDN