The same platform, the same features, the same dashboard. All that differs is where the system runs and who owns the hardware.
Your routers send traffic statistics to the system. It evaluates them, and when it finds an attack it sends back an instruction to block it. You watch the dashboard in your browser.
Where the system runs is your choice. In the cloud we run it; with the hardware option the same software runs on a server in your own network. The diagram stays the same — only the middle box moves.
Functionally they are equals. They differ in where the data sits, who owns the hardware and how fast the system spots an attack.
| Cloud | Hardware in your network | |
|---|---|---|
| Where the system runs | our data centre in Czechia | your rack |
| Where the data is | with us, encrypted | with you |
| Up-front investment | none | purchase or leasing |
| How fast an attack is spotted | 15–60 s | a few seconds |
| Suitable for data retention | ~ | ✓ |
| Deployment | within 48 hours | within a week |
Faster detection on your own iron is no magic: a probe on a mirror port sees the packets immediately, while an export from the router only arrives once the connection ends. And mirroring cannot be sent to the cloud — it is a physical copy of the traffic on a port.
The fastest route to your first data. No hardware to buy, no changes to your traffic path.
Traffic and location data under Section 97 of the Czech Electronic Communications Act is better kept at your site, on your own server. The operator carries the responsibility for it. Security analytics in the cloud is not limited by this.
It sits in your rack, no data leaves it, and it is your property from day one.
Server hardware prices have risen sharply and continue to fluctuate — most of all for disks and memory. We therefore do not publish a fixed price list.
Worked example
from EUR 6,000
Typically EUR 6,000 to EUR 8,800 per server. The difference comes mainly from the size of the disk array — how much traffic the network generates and how long the data has to be kept.
The range is indicative, current as of today and not an offer. We will calculate the actual price from the size of your network and the retention period you need.
The bands match network size as used in the price list.
| up to 1,000 subscribers | 1,001–5,000 | 5,001–20,000 | 20,000+ | |
|---|---|---|---|---|
| Traffic | up to 5 Gbps | up to 20 Gbps | up to 50 Gbps | up to 100 Gbps |
| Processor | 8 cores | 16 cores | 24–32 cores | 2× 32 cores |
| ECC memory | 32 GB | 64 GB | 128 GB | 256–512 GB |
| Disks | 2× 960 GB NVMe + 2× 4 TB | 2× 1.92 TB NVMe + 4× 8 TB | 4× 3.84 TB NVMe + 8× 16 TB | 8× 7.68 TB NVMe + separate archive |
| Network for mirroring | 1× 10 GbE | 2× 25 GbE | 2× 40/100 GbE | 2× 100 GbE |
An Intel X710, E810 or ConnectX‑5/6 network card. Cheap cards on a mirror port above 1 Gbps drop packets silently, with nothing in the log. We will design the exact configuration around your network.
Tell us how many subscribers you have, how much traffic they generate and how long you need to retain data. We will come back with a specific proposal.
