Skip to content
PEERYXNETWORK

Deployment requirements

Protection shaped around the network you operate

The right starting point is the service that must remain reachable, the route you control and the equipment that receives the traffic. Select your environment to see the questions that change the design.

An aisle between server racks in a data center.
Illustrative photograph · Brett Sayles / Pexels

ISPs and network operators

Protecting an access network means preserving the shared paths used by many subscribers while keeping route ownership and connection behavior predictable. Begin with the prefixes you operate and the resource that fails first.

View deployment requirements

Hosting and server providers

One attacked tenant should not turn an entire rack or virtualization cluster into an unexplained outage. Identify which resources are shared, which policy belongs to each customer and where protected traffic enters your platform.

View deployment requirements

Datacenters and colocation

A datacenter design has to connect network protection to real interfaces, customer routing and shared failure domains. Port speed, local filter performance and upstream service capacity each need their own acceptance boundary.

View deployment requirements

Game hosting providers

A server that answers a ping can still fail during player connection, resource loading or normal gameplay. Work from the game’s real public endpoint and origin path, then test the actions your players actually perform.

View deployment requirements

Enterprises and SaaS platforms

Keeping a public service available requires both a reachable network path and an application that can handle legitimate work. Identify the address and routing you control before choosing how protected traffic reaches the service.

View deployment requirements

Not sure which environment fits?

Use the architecture guide to compare protected delivery, local filtering and telemetry-led diversion from a few deployment facts. It produces a planning brief, not an automatic provisioning decision.

Open the architecture guide

Keep the service boundaries clear

Protected Transit IP supplies a network service. Defense Fabric licenses filtering on compatible equipment. Flow Collector observes telemetry and can control authorized diversion; it is not an inline filter. Choose the required layers separately.