Your ground.
Ardarik runs in your infrastructure and nowhere else: there is no cloud service to route through. Traffic, logs and what it learns stay in your network, and it needs no connection to us to protect you.
The last line of defence.
Ardarik stands between attacks and your applications: a security gateway that is open at its core and runs only on your own ground.
Firewall · Intrusion detection · Intrusion prevention
Machines write the attacks now.
Language models produce them at volume, in endless variation, at any hour. A list of known patterns no longer holds on its own.
It knows the attack. It knows your application.
The rule engine
Every request runs through the OWASP Core Rule Set, on an engine we wrote ourselves in Rust.
The learned profile
It learns each application from its own traffic, on your hardware, and measures every request against it. Enterprise edition.
Four principles
Nothing to hide.
At launch the core is published under AGPL-3.0: the proxy, the rule engine, the parsers, the log. Do not trust us. Read it.
Read the sourceNo black box.
When Ardarik stops a request, it tells you why. In a sentence, not a rule number.
Which check objected, and to which part of the request. In its code, a block without a reason cannot be built.
European by origin.
Designed and engineered in Germany by Cloo GmbH, for organisations that answer to European law.
Plain words first.
The console is written for network administrators, not for specialists in web attacks. It says what happened first and keeps the precise term one step away.
Free at its core. One price for the rest.
The open core protects on its own. The Enterprise edition is licensed per instance; applications, requests and users are not counted.
See pricing
Europe must hold its own line.
A continent that sends its traffic through other people’s defences does not decide what gets through. On why the last line has to stand on your own ground.
Read the essay