Dual Edge Deployment

Bring Your Own Edge

Use Peakhour as your edge, or add Peakhour intelligence to the edge you already run. The same decision surface supports security, performance, traffic control, and evidence in both modes.

Plan Your Edge Deployment Compare Modes

Diagram showing Peakhour running either as the application edge or as an intelligence layer adding security, traffic, image, resilience, caching, log, and observability controls to an existing edge provider.

Compact dual-edge diagram showing Peakhour as the edge or as an intelligence layer beside an existing provider.

Two first-class ways to deploy Peakhour.

Choose Peakhour Edge when you want one platform to inspect, accelerate, deliver, absorb, route, cache, and observe application traffic. Choose Existing Edge + Peakhour when you need to keep a current CDN, cloud edge, or provider contract while adding Peakhour decisions and evidence.

Discuss your edge architecture

Full edge platform

Peakhour Edge

Route application traffic through Peakhour as the primary edge for WAAP, bot management, DDoS protection, rate limiting, caching, image optimisation, traffic management, log forwarding, and observability.

Visitors Peakhour Edge Decision surface Origin

Bot management WAAP Rate limiting Traffic routing Image optimisation DDoS Caching Logs Observability

Keep your current edge

Existing Edge + Peakhour

Keep Cloudflare, Fastly, AWS CloudFront, another CDN, or your own edge architecture while Peakhour adds intelligence, policy decisions, risk signals, enriched logs, and observability beside it.

Visitors Existing edge Peakhour intelligence Origin

Bot management WAAP Rate limiting Traffic control Image decisions DDoS signals Cache evidence Log forwarding Observability

Same capability map Bot management, WAAP, rate limiting, traffic management, image optimisation, DDoS, caching, log forwarding, and observability stay in scope across both deployment modes.

No forced rip-and-replace Peakhour can consolidate edge controls, or coexist with the provider and contracts already in place while the team stages adoption.

Evidence stays operational Requests carry Peakhour decisions into logs and dashboards so security, platform, and performance teams can see what happened and why.

Integration routing flow showing current edge traffic, Peakhour policy decisions, origin routing, and evidence visibility.

Start from your current edge reality and shape the control path

Teams usually begin with a practical edge constraint, then choose where policies should execute, and finally align security, delivery, and observability in one governed path. Peakhour supports that flow whether it runs as the primary edge or as an intelligence layer beside your existing provider.

Keep delivery continuity while controls mature

Preserve your current CDN or cloud edge where needed, while introducing Peakhour decisions for WAAP, bot posture, rate controls, and routing outcomes without forcing a full cutover on day one.
Consolidate onto Peakhour Edge when the operating model is ready

Move to a single edge control surface when consolidation improves ownership, change velocity, and policy consistency across security and platform teams.
Carry one decision vocabulary across both modes

Use the same request context and action semantics so operators can interpret bot, WAAP, rate, cache, and routing outcomes consistently across mixed or consolidated deployments.

A staged path instead of a binary bet

Peakhour can help assess the current edge, decide what should move to Peakhour Edge, and identify which controls should augment the existing path first.

Current-state audit reviews CDN, security, caching, image, routing, logging, and DDoS responsibilities.
Enforcement placement maps each control to the point where it can act with the right context and ownership.
Migration optionality supports coexistence first, consolidation later, or a sustained mixed path where that is operationally correct.
Telemetry-backed validation forwards enriched request context so operators can verify bot, WAAP, rate, cache, and routing outcomes.

Edge audit worksheet showing CDN, security, traffic, cache, and observability responsibilities.

Deployment evidence stays consistent across edge modes

The proof board shows both paths explicitly: Peakhour as the primary edge, or Peakhour intelligence running beside an existing provider. The same decision context remains usable in either operating model.

Policy Decision outcome Allow, challenge, throttle, or block

Route Path visibility Observe edge-to-origin handling

Telemetry Evidence continuity Correlate security and delivery signals

Dual-edge deployment board comparing Peakhour Edge and Existing Edge plus Peakhour paths with shared request decisions, origin routing, and evidence outputs. — Mode comparison evidence

Peakhour Edge or Existing Edge + Peakhour Deployment flexibility

One decision language for security and platform teams Governance

Request-level evidence for incident and change reviews Review readiness

Teams can validate behavior and explain outcomes without relying on disconnected screenshots from separate tools.

Plan the right edge deployment for your team

Bring your current edge strategy. Peakhour can run as the platform edge or add intelligence to the provider you already operate.

Talk to Peakhour → See How It Works

Integration routing diagram showing Peakhour fitting into an edge deployment path.