Zeq Edge — edge protection
Zeq Edge sits in front of your site. Point your DNS at the edge and you get the things an edge network gives you — a WAF and a cache — plus the thing only Zeq gives you: a per-Zeqond entangled state of every request. Your traffic isn't just filtered and cached; it's recorded on a tamper-evident, clock-stamped chain you can audit.
What you get
WAF
A web application firewall at the edge, screening requests before they reach your origin.
Cache
Edge caching for speed, with the hit rate reported alongside your traffic.
Audited requests
Every request becomes part of a per-Zeqond entangled state — a provable record of what hit your site and when.
Traffic on the clock
Requests are aggregated in a rolling 60-Zeqond window — about 46.6 seconds, or 77 ticks at 1.287 Hz — so the dashboard's counts (requests over the last day, cache-hit rate, threats seen) are binned to the framework's clock rather than an arbitrary wall-clock interval. Protection and audit are the same layer here: the edge that blocks the bad request also writes the proof that it did.
Open it
Read next
- Zeq-SSL — credentials for the traffic the edge fronts.
- Observing a machine — the audit chain the requests land on.
- Forensic Dashboard — the HF threat spectrum the edge screens against.