/ edgescaleIntroducing EdgeScale Ingress
Publish it anywhere.
We defend it everywhere.
The moment you expose a service to the internet, you've taken on a second job: absorbing attack traffic, watching for abuse, keeping it fast for real users no matter where they are. EdgeScale Ingress does that job for you — globally, by default, the instant you publish a hostname.
Why it exists
Exposing a service used to mean exposing yourself.
01
Distance is risk
A single origin server means every request — legitimate or not — travels the full distance to reach you. The farther the trip, the more it costs your real users and the more room an attacker has to hide.
02
Visibility stops at the door
Most teams find out something was wrong with their inbound traffic after it already happened — from a spike in errors, not from actually seeing the request that caused it.
03
Protection becomes its own project
Standing up real edge protection today means new infrastructure, new vendors, new things to operate — before you've published a single service.
How it feels
Three steps. None of them are yours to run.
You do this
Publish a hostname
Tell Threatmatic what you want reachable from the internet. That's the entire setup step — no servers to provision, no certificates to manage by hand.
We do this
Route to the nearest edge
Every request finds the closest point of presence automatically, so real users get a short trip regardless of where in the world they're connecting from.
We do this
Inspect, then decide
Traffic is evaluated before it ever reaches your origin — the same detection engine already watching outbound traffic today, now standing in front of what you publish.
Built on what you already trust
Not a new engine. The same one, facing the other way.
Threatmatic's inspection engine already watches outbound traffic for your devices — flagging brute-force attempts, credential stuffing, and suspicious patterns before they become incidents. EdgeScale Ingress puts that same engine in front of the services you publish, so inbound traffic gets the same scrutiny outbound traffic already gets. One detection model. Both directions.
Coming to every Threatmatic organization
Your next published service shouldn't be your next liability.
EdgeScale Ingress is rolling out to design partners first. If you're already publishing something to the internet today — or about to — we'd like to make it someone else's problem to defend.