Peakhour Products
Application security, request-path control, cache and delivery policy, traffic routing, and observability in one product system. Run Peakhour Edge as the full delivery layer, or keep an existing edge provider in place while WAAP, API security, bot decisions, rate limits, cache policy, image optimisation, TLS, logging, load balancing, and origin shield stay attached to one request path.
Application security controls for WAAP, API security, bot decisions, rate limits, cache policy, image optimisation, TLS, logging, load balancing, and origin shield.
One operating surface for security, delivery, and traffic signals
The product portfolio is not a pile of separate tools. A cache rule, rate-limit rule, or origin-shield policy can use bot verification, geography, API path, payload policy, traffic-control state, and log evidence so teams can see why traffic was served, routed, challenged, throttled, or blocked.
Start from a focused rule builder, then follow the linked controls into cache policy, API protection, bot control, image optimisation, and log forwarding without repeating the product grid.
Security controls
Inspect requests before origin, then allow, challenge, throttle, or block with evidence attached.
Cache, delivery, and performance controls
Serve more traffic from cache, protect origin capacity, tune payloads, and steer misses with request evidence attached.
Platform controls
Operate certificates, traffic steering, logs, and implementation support as part of the product system.
Map the Right Product Controls to Your Request Path
Review the Peakhour system as security decisions, cache and image policy, TLS state, load balancing, origin shield, and log evidence rather than isolated products.