PRODUCTS / APPLICATION DELIVERY

Application delivery

Route, secure, accelerate, and observe traffic at the edge. CrownWall combines global routing, modern TLS, load balancing, origin health, trusted headers, request IDs, and edge caching in one application delivery layer.

Global edge routing

One domain. Independent routes.

Route visitors to the right origin based on hostname and URL path. Attach different upstream pools, cache behavior, and security policies to each application route — APIs, web apps, and static paths can coexist under one domain.

APIs

route policies

Web apps

origin pools

Static

cache rules

HTTP/2 and modern TLS

Terminate HTTPS at the edge with HTTP/1.1 and HTTP/2 support. Multiple certificates can serve different hostnames on the same listener using SNI. Bring your own certificate or use one issued for your domain.

Force HTTPS

Automatically redirect HTTP visitors to HTTPS so credentials and session cookies never travel in cleartext.

Intelligent load balancing

Distribute traffic across healthy origins with round-robin or session-aware hashing — stickiness by client IP, URL, path, header, cookie, or query string when your workload needs it.

Origin selection

Round-robin

Simple distribution across healthy origins.

Sticky sessions

Hash by IP, header, cookie, path or query.

Route-specific pools

Different upstreams per hostname or path.

Independent policy

Security and cache settings per route.

Dynamic origin discovery

Point at a DNS hostname instead of fixed IPs. CrownWall refreshes the origin pool on a schedule as your infrastructure scales up, down, or moves.

Origin health monitoring

Continuous probes over HTTP, HTTPS, TCP, or gRPC remove failed backends from rotation until they recover — so users never wait on a dead server.

Origin connection optimization

Tune keep-alive, connection timeouts, and TLS settings, including upstream SNI, between the edge and your application for reliable, efficient backhaul.

Trusted forwarding headers

Send accurate client IP, host, and protocol information to your application so logs, rate limits, and audit trails reflect real users — not the edge.

Custom origin headers

Inject or override headers on origin requests per route — for tracing, environment tagging, or routing hints without application changes.

Request ID on every transaction

Each request receives a unique edge-generated identifier. The same ID appears in your access logs, on responses to clients, and on requests forwarded to origins — so support and security teams can correlate a browser report with backend logs in seconds.

Performance & caching

Accelerate common responses at the edge while keeping dynamic and sensitive routes fresh.

Edge response cache

Cache GET and HEAD responses at the edge to cut latency and origin load. Use aggressive TTL for static assets and short or zero TTL for APIs on the same domain.

Flexible cache keys

Control what distinguishes one cache entry from another: path, selected headers, and query parameters — so variants cache correctly without collision.

Opt out where freshness matters

Disable caching on checkout, account, or real-time endpoints while keeping it enabled for the rest of the site.

Cache analytics

Dashboard and metrics show hit ratio, misses, and rejections so you can tune TTL and key rules with data — not guesswork.