Akamai NodeBalancers

Name: Akamai NodeBalancers
Brand: Akamai Technologies

Leader

At Akamai, we make life better for billions of people, billions of times a day

Est 1998|Valuation $16.6B|Raised $361.8M

LinkedIn 592K|Website|Web traffic 2.2M|FTEs 11,000|HQ Cambridge, Massachusetts, US

MarketsWeb Application & API Protection (WAAP)

Platform CoversInfrastructure Monitoring Infrastructure as Code (IaC)

Published Sep 26, 2026

01Common complaints

Organizations that require modern L7 protocol support (HTTP/2/gRPC) at the load balancer immediately

NodeBalancer documentation states L7 uses HTTP/1.1 and HTTP/2 is not currently available. Alternative options include AWS ALB, Google Cloud HTTPS Load Balancer, Azure Application Gateway, or specialized proxy solutions depending on requirements.

Organizations that require transparent, self-serve pricing for high-scale tiers

Premium NodeBalancer pricing requires sales engagement, which can create procurement friction for teams that need predictable, self-service pricing for high-capacity requirements.

Organizations that require mature, first-party observability for the LB at day one

Cloud Pulse metrics for NodeBalancers are in limited availability and alerts/logs are listed as planned; teams needing integrated monitoring should plan for external tooling.

PCI-constrained payment architectures that require the LB to be in-scope

Akamai’s PCI DSS responsibility matrix indicates NodeBalancers may be out of scope for certain PCI-compliant workloads; procurement teams should confirm scope during vendor assessment.

Teams that require a cloud-agnostic, vendor-neutral load balancing solution

NodeBalancers are designed for Akamai Cloud backends; multi-cloud balancing typically requires DNS/GSLB solutions or vendor-neutral products.

1) Organizations that require modern L7 protocol support (HTTP/2/gRPC) at the load balancer immediately - NodeBalancer documentation states L7 uses HTTP/1.1 and HTTP/2 is not currently available. Alternative options include AWS ALB, Google Cloud HTTPS Load Balancer, Azure Application Gateway, or specialized proxy solutions depending on requirements. 2) Organizations that require transparent, self-serve pricing for high-scale tiers - Premium NodeBalancer pricing requires sales engagement, which can create procurement friction for teams that need predictable, self-service pricing for high-capacity requirements. 3) Organizations that require mature, first-party observability for the LB at day one - Cloud Pulse metrics for NodeBalancers are in limited availability and alerts/logs are listed as planned; teams needing integrated monitoring should plan for external tooling. 4) PCI-constrained payment architectures that require the LB to be in-scope - Akamai’s PCI DSS responsibility matrix indicates NodeBalancers may be out of scope for certain PCI-compliant workloads; procurement teams should confirm scope during vendor assessment. 5) Teams that require a cloud-agnostic, vendor-neutral load balancing solution - NodeBalancers are designed for Akamai Cloud backends; multi-cloud balancing typically requires DNS/GSLB solutions or vendor-neutral products.

Deal disqualifiers (poor fit)

Requirement for LB-level HTTP/2 or HTTP/3 termination today
Need for sophisticated L7 routing and policy enforcement at the LB layer (advanced header routing, mutual TLS, integrated WAF)
Requirement for fully integrated first-party LB observability (metrics, alerts, logs) at deployment time given Cloud Pulse limitations

Sources:

Official vendor documentation — NodeBalancers product documentation
Official vendor documentation — NodeBalancers monitoring and observability documentation

- Requirement for LB-level HTTP/2 or HTTP/3 termination today - Need for sophisticated L7 routing and policy enforcement at the LB layer (advanced header routing, mutual TLS, integrated WAF) - Requirement for fully integrated first-party LB observability (metrics, alerts, logs) at deployment time given Cloud Pulse limitations Sources: - Official vendor documentation — NodeBalancers product documentation - Official vendor documentation — NodeBalancers monitoring and observability documentation

Vendor-documented limitations

L7 load balancing supports HTTP/1.1 only; HTTP/2 is not available for NodeBalancers.
UDP support is limited to the premium tier and must be configured via the API.
The Cloud Manager UI does not support UDP; UI changes can overwrite UDP configuration made via API.
Cloud Pulse metrics for NodeBalancers are in limited availability; alerts and logs are planned but not fully available in the documentation reviewed.

Sources:

- L7 load balancing supports HTTP/1.1 only; HTTP/2 is not available for NodeBalancers. - UDP support is limited to the premium tier and must be configured via the API. - The Cloud Manager UI does not support UDP; UI changes can overwrite UDP configuration made via API. - Cloud Pulse metrics for NodeBalancers are in limited availability; alerts and logs are planned but not fully available in the documentation reviewed. Sources: - https://techdocs.akamai.com/cloud-computing/docs/nodebalancer - https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-nodebalancers - https://techdocs.akamai.com/cloud-computing/docs/monitor-nodebalancers

Roadmap signals

Akamai’s Cloud Pulse documentation indicates alerts and logs for NodeBalancers are planned; no firm release dates were found in the reviewed materials.

Source:

https://techdocs.akamai.com/cloud-computing/docs/monitor-nodebalancers

Scale limitations (public specs)

Documented public limits:

Non-premium: up to 1,000 backends per configuration; up to 10,000 concurrent connections (TCP/HTTP/HTTPS).
Premium: up to 2,000 backends per configuration; up to 100,000 concurrent connections (TCP/HTTP/HTTPS); up to 80,000 concurrent connections for UDP.

Source:

https://techdocs.akamai.com/cloud-computing/docs/nodebalancer

Documented public limits: - Non-premium: up to 1,000 backends per configuration; up to 10,000 concurrent connections (TCP/HTTP/HTTPS). - Premium: up to 2,000 backends per configuration; up to 100,000 concurrent connections (TCP/HTTP/HTTPS); up to 80,000 concurrent connections for UDP. Source: - https://techdocs.akamai.com/cloud-computing/docs/nodebalancer

Why some customers leave / churn reasons (inferred)

Common churn drivers evident in reviews and community threads include account verification and fraud-flag lockouts, support delays, changes in perceived value after pricing changes, and sensitivity to outages in relied-on regions.

Sources:

Trustpilot consumer review pages
Reddit community threads and posts
Hacker News discussion threads

02Why they buy

Key differentiators supported by documentation and repeated user feedback:

Baseline monthly price for the standard NodeBalancer tier documented at $10/month.
Integration with Akamai Cloud primitives (Cloud Manager, API, CLI, and IaC tooling such as Terraform/Pulumi).
Premium tier that documents higher concurrency and UDP support, subject to procurement terms and API/UI constraints.

Where competitors typically differ:

Hyperscalers provide deeper managed L7 features, richer protocol support, and broader integrated security and observability services.
Edge/DNS providers may offer more comprehensive global traffic steering options.

Sources:

Pricing: https://www.akamai.com/cloud/pricing
Specs and IaC references: https://techdocs.akamai.com/cloud-computing/docs/nodebalancer

Key differentiators supported by documentation and repeated user feedback: - Baseline monthly price for the standard NodeBalancer tier documented at $10/month. - Integration with Akamai Cloud primitives (Cloud Manager, API, CLI, and IaC tooling such as Terraform/Pulumi). - Premium tier that documents higher concurrency and UDP support, subject to procurement terms and API/UI constraints. Where competitors typically differ: - Hyperscalers provide deeper managed L7 features, richer protocol support, and broader integrated security and observability services. - Edge/DNS providers may offer more comprehensive global traffic steering options. Sources: - Pricing: https://www.akamai.com/cloud/pricing - Specs and IaC references: https://techdocs.akamai.com/cloud-computing/docs/nodebalancer

Why customers chose it (inferred from review patterns)

Reported reasons include predictable baseline pricing, ease of provisioning infrastructure, acceptable support for some customers, and developer-oriented APIs and tooling.

Sources:

TrustRadius product review pages
G2 product and seller pages

03Field reports

Important limitation: review platforms generally list Akamai Cloud Computing (Linode) as a whole rather than NodeBalancers specifically. Customer feedback for the cloud platform often reflects experiences that affect NodeBalancers in production (support quality, outages, billing friction, usability).

Review Platforms: TrustRadius (examples)

Examples from reviews reference uptime, support, and cost effectiveness as positive factors in some submissions (e.g., a recent vetted review). Other reviews requested expanded regional coverage and changes to network limits.

Source:

TrustRadius product review pages

Review Platforms: G2 (examples)

G2 lists Akamai Cloud Computing with a distribution favoring higher ratings; negative themes include limited features and complex setup for some users. These comments are platform-level and may influence expectations for NodeBalancers.

Source:

G2 product and seller pages

Review Platforms: Trustpilot (complaints and mixed experiences)

Trustpilot entries often describe issues with signup and account verification, including fraud flags. Some long-time users report positive experiences, while others report frustration. Account creation and verification problems can materially affect procurement and pilots.

Source:

Trustpilot consumer review pages

Community/Social: Reddit (selected themes)

Community threads include reports about support responsiveness, account-related issues, pricing concerns, and outage experiences. These community signals should be considered for availability risk planning, while recognizing they are anecdotal.

Sources (examples):

Reddit community threads and posts

Community/Social: Hacker News

Discussions on Hacker News have documented regional outage events and the associated user discussions.

Source:

Hacker News discussion threads

Vendor-published customer stories mentioning NodeBalancers

Examples:

MultiVRse customer story (mentions NodeBalancers in stack): Vendor-published customer story PDF on the vendor site
APIcontext story (mentions NodeBalancers + Terraform): Vendor-published customer story PDF on the vendor site

Critical evaluation:

Vendor-published stories rarely provide validation of causality (for example, specific percentage reductions in downtime with methodology). Metrics are often self-reported and lack disclosed methodology.

Akamai customer stories reference NodeBalancers as part of some customer infrastructure stacks. These vendor-published customer stories describe provisioning and operational aspects but typically do not include independently audited methodologies or detailed quantitative comparisons against alternatives. Examples: - MultiVRse customer story (mentions NodeBalancers in stack): Vendor-published customer story PDF on the vendor site - APIcontext story (mentions NodeBalancers + Terraform): Vendor-published customer story PDF on the vendor site Critical evaluation: - Vendor-published stories rarely provide validation of causality (for example, specific percentage reductions in downtime with methodology). Metrics are often self-reported and lack disclosed methodology.

Third-party writeups (not controlled studies)

Third-party reviews commonly describe NodeBalancers as affordable at the documented baseline pricing published by the vendor, but these sources are not rigorous benchmarks and typically do not include standardized performance testing.

Example:

Third-party community review (Better Stack) — community guide comparing Linode and Akamai

04Best fit

Company sizes (practical ranges)

1–200 employees (startups/SMBs) running 2–20 instances and requiring basic high availability for web applications.
200–2,000 employees with platform teams that seek alternatives to hyperscalers for selected workloads or for edge-adjacent architectures.

This is inferred from Akamai Cloud customer segments and the product’s capabilities.

Industries / verticals

SaaS, web applications, e-commerce, developer tooling.
Media and content services that align with Akamai’s broader ecosystem.

Roles and personas

DevOps / SRE
Platform engineering
Backend engineering
Technology leadership at smaller organizations evaluating managed primitives over self-operated proxies

Pain points addressed

Reducing single-server single points of failure for front-end services
Supporting rolling maintenance without full downtime
Enabling straightforward scale-out patterns

Qualification criteria (good fit)

Primary hosting on Akamai Cloud
Acceptance of HTTP/1.1 constraints for L7 or reliance on TCP-level balancing
Preference for a predictable baseline price for the standard tier and willingness to engage sales for premium capabilities

05The pitch

What the product does (core value proposition)

Key documented capabilities include:

TCP, HTTP, and HTTPS load balancing (HTTP/1.1 for L7).
SSL/TLS termination and session persistence ("sticky sessions").
Passive per-request health checks plus configurable active health checks.
Dedicated IPv4 + IPv6 addresses per NodeBalancer.
Client connection throttling.
Multi-port balancing (one NodeBalancer can front multiple services/ports).

Sources: Official vendor product pages and technical documentation.

Akamai NodeBalancers are a managed Load Balancer-as-a-Service (LBaaS) offering within Akamai Cloud (formerly Linode). They distribute inbound traffic across multiple backend compute instances ("Linodes") to improve availability and support horizontal scaling, using TCP (L4) and HTTP/HTTPS (L7) load balancing. Premium NodeBalancers provide higher capacity and UDP load balancing (API-only configuration). Key documented capabilities include: - TCP, HTTP, and HTTPS load balancing (HTTP/1.1 for L7). - SSL/TLS termination and session persistence ("sticky sessions"). - Passive per-request health checks plus configurable active health checks. - Dedicated IPv4 + IPv6 addresses per NodeBalancer. - Client connection throttling. - Multi-port balancing (one NodeBalancer can front multiple services/ports). Sources: Official vendor product pages and technical documentation.

Target market and market positioning

Positioning is primarily:

SMB to mid-market teams building or hosting on Akamai Cloud that require a managed load balancing service without operating HAProxy/Nginx clusters directly.
Developer-led teams that prefer straightforward cloud primitives and Infrastructure-as-Code/API access.
Kubernetes users on Akamai’s Kubernetes Engine (LKE / LKE Enterprise), where load balancers are commonly used for ingress patterns.

The feature set indicates NodeBalancers target basic to moderate L4/L7 requirements rather than advanced enterprise application delivery controller (ADC) capabilities (for example, WAF at the LB layer, HTTP/2/3 termination, advanced L7 routing, global traffic steering, or mutual TLS termination).

Sources: Official vendor technical documentation and product overview pages.

Positioning is primarily: - SMB to mid-market teams building or hosting on Akamai Cloud that require a managed load balancing service without operating HAProxy/Nginx clusters directly. - Developer-led teams that prefer straightforward cloud primitives and Infrastructure-as-Code/API access. - Kubernetes users on Akamai’s Kubernetes Engine (LKE / LKE Enterprise), where load balancers are commonly used for ingress patterns. The feature set indicates NodeBalancers target basic to moderate L4/L7 requirements rather than advanced enterprise application delivery controller (ADC) capabilities (for example, WAF at the LB layer, HTTP/2/3 termination, advanced L7 routing, global traffic steering, or mutual TLS termination). Sources: Official vendor technical documentation and product overview pages.

Get a comprehensive analysis of Akamai NodeBalancers including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →