PRODUCTS / LOAD BALANCING

Intelligent traffic distribution, included.

Health-aware routing, dynamic DNS resolution, and response caching across all your backends — built into the platform, not sold as a separate add-on.

Backend health routing

Traffic → Healthy origins

Traffic is distributed across multiple healthy backend servers while unhealthy origins are bypassed automatically.

Origin A

healthy

Origin B

healthy

Origin C

bypassed

Delivery and security, from one engine.

CrownWall is a complete application delivery controller — the same category of infrastructure that sits in front of enterprise applications worldwide, delivered as a cloud-native platform. Load balancing isn’t an afterthought or a paid extra; it’s a core capability in every plan.

That matters because real applications have more than one backend. A typical deployment runs at least two application servers behind a balancer, often more. Charging extra for that fundamental capability — as several WAF-only vendors do — is a billing decision, not a technical one.

Included as standard.

Load balancing, security inspection, caching, and logging operate inside the same request pipeline.

One

subscription

One

pipeline

One

dashboard

Route traffic the way your application needs.

Choose the traffic distribution method that matches your application architecture.

Round-robin

Distribute requests evenly across all healthy backends.

Hash-based

Route consistently by source IP, session cookie, or URL, for sticky sessions without server-side state.

Weighted

Assign more traffic to backends with more capacity.

Least connections

Route to the backend currently handling the fewest active connections.

Failures handled before your users see them.

CrownWall continuously checks the health of every backend, removing unhealthy nodes from rotation automatically and restoring them when they recover.

HTTP health checks

Request a URL, expect a specific status code and optional response body.

TCP health checks

Verify port availability for non-HTTP services.

gRPC health checks

Use the standard gRPC health-checking protocol.

Configurable thresholds

Tune how aggressively flapping backends are removed.

Built for infrastructure that moves.

Modern backends rarely have static IPs — they live in autoscaling groups, container orchestrators, and cloud environments. CrownWall resolves backend hostnames dynamically, picking up new instances and dropping terminated ones with no manual reconfiguration.

Optionally cache responses at the edge, with full control over cache keys, TTL, and which requests bypass the cache — reducing origin load and improving performance for read-heavy workloads.

Dynamic by default

Autoscaling, dynamic DNS, cache rules, and backend rotation work together without manual reconfiguration.

DNS

dynamic resolution

Cache

edge response

Failover

automatic

What this replaces.

For many customers, CrownWall replaces a separate reverse proxy, a cloud load balancer, a bolt-on WAF, and a paid bot management plugin — with one subscription, one dashboard, and one logging pipeline.

Feature tags

Round-robin

Hash-based

Weighted

Least-connections

HTTP/TCP/gRPC checks

Dynamic DNS

Response caching

Automatic failover

Keep-alive

Health-aware routing

Edge caching

Origin protection

Intelligent traffic distribution, included.

Traffic → Healthy origins

Delivery and security, from one engine.

Included as standard.

Route traffic the way your application needs.

Round-robin

Hash-based

Weighted

Least connections

Failures handled before your users see them.

HTTP health checks

TCP health checks

gRPC health checks

Configurable thresholds

Built for infrastructure that moves.

Dynamic by default

What this replaces.

Feature tags

Deliver every request to a healthy backend.