E-commerce & checkout
Carts and payment flows stay reachable during a flood. Per-route rules and rate limits slow scrapers and card-testing at checkout, and the cache absorbs traffic that never needed your origin.
GuardX puts its own edge in front of your websites and APIs — mitigation, firewall and delivery in one platform, built in-house and operated in the EU.
Built on open standards
01Platform
Mitigation, firewall, delivery, DNS and certificates run as one system in front of your stack — configured from a single control plane.
Volumetric and application-layer floods are absorbed before they reach your origin. Always on, unmetered, and unnoticed by almost everyone using your product.
Managed protection out of the box, plus your own rules on path, header, country, network or rate.
Static content is served from the edge, so your origin only does the work that is actually new.
HTTP/2 200 x-guardx-cache: HIT age: 1832 cache-control: public, max-age=86400
Records, DNSSEC and one-click proxying, managed in the panel.
Certificates issued and renewed automatically. TLS 1.3 by default, HSTS with one switch.
02Under attack
No rerouting, no DNS switch, no emergency call. Protection is already in the path — and the invoice does not move with the size of the flood.
Mitigation runs on every request, from the first one. There is nothing to activate when it matters.
Real users keep their sessions in almost every case. Interrupting a person is the last resort, not the default response.
Attack traffic is never billed. Mitigation is part of every plan, including the free one.
03Products
Websites and APIs at layer 7 today. Whole networks at layers 3 and 4, and hardware behind the filter, are on the way.
04Use cases
The same platform protects a checkout, a login endpoint and, soon, a game server — what changes is which layer does the work.
Carts and payment flows stay reachable during a flood. Per-route rules and rate limits slow scrapers and card-testing at checkout, and the cache absorbs traffic that never needed your origin.
Machine traffic is your product, so protection is built to keep it flowing. Per-route rules and rate limits protect a login without touching the endpoints your customers automate.
Coming soon: traffic routed to us over GRE, cleaned and handed back, so UDP floods never reach the box and your server address stays out of view.
A portfolio of client sites under one account, with per-domain rules and analytics, and pricing that does not move when a client is attacked.
05Network
GuardX builds and runs its own platform. Our own engine inspects and caches your traffic on our own servers in the EU, and request logs are stored in the EU — no white-label firewall.
06Getting started
No agent to install, no library to import, no code to change.
We pick up your main DNS records, and you can paste a zone file for the rest. Nothing changes for visitors while you review them.
Point your registrar at GuardX. Certificates are issued automatically and traffic starts flowing through the edge.
Sensible protection is active from the first request. Add rules, limits or a stricter mode whenever you need them.
07Learning centre
A web application firewall inspects HTTP requests and blocks SQL injection, XSS and bot abuse before they reach your app. How it works and what it misses.
A DDoS attack floods a target from many machines at once until it stops serving real users. Attack types, warning signs, real-world scale and defences.
DDoS mitigation filters attack traffic while real users keep getting through. Detection, techniques compared, always-on vs on-demand, pricing and set-up.
Get started
Most sites are set up in minutes, with zero code changes.