Skip to content

Segal Edge

Place caching and application security controls between public traffic and the origin.

Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.

How the service fits.

CDN options attached to eligible hosting plans. Arbitrary edge functions and universal WAF coverage are not included.

  1. 1

    Route a verified hostname through the delivery service

  2. 2

    Apply the supported cache and security rules

  3. 3

    Measure origin health and cache behavior before tuning

Service architecture

  • Cache policies define which responses can be reused
  • TLS and origin configuration must agree on hostnames
  • Security controls follow the selected delivery product

Operating boundaries

  • Programmable edge functions are not implied by CDN support
  • WAF and cache features vary by hosting or delivery plan
  • Purging a cache does not roll back the origin application

Deployment & support

Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.

Upstream service: Web Hosting CDN. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.

Upstream technical reference

Connect the rest.

Explore platform architecture