Shield · limits

What Shield does. And what it does not.

A security product is easier to trust when it says where it stops. Shield protects websites from bots, scrapers, attack probes and HTTP floods. Here is what lies outside that line, and who Shield is for.

Community is free on one server, with every protection.

§01Not covered

What Shield does not do

§02Who it is for

Shield is for

§03Who it is not for

Shield is not for

§04Covered

What Shield does

01

Bots and scrapers

In full protection scrapers, headless browsers and bare HTTP clients are refused; verified search engines and link previews always get in.

02

HTTP floods

Waves from thousands of addresses are recognised within seconds and held back; visitors already in keep buying.

03

Attack probes

Requests for secret files, known exploits, injections and login floods are refused before they reach the application.

04

Your data, your server

Every decision is made on your server, and no visitor IP leaves it.

§05Before you install

Start by watching

Shield starts in observe mode: floods and attack probes are stopped, everything else it would refuse is only recorded. After about a week the dashboard shows what your traffic looks like, and you decide when to switch to full protection.

Requirements: Linux, Docker, Python 3.8 or newer and administrator access (sudo); Shield keeps within 1 GB of memory. With Apache on Debian or Ubuntu the install is fully automatic; with nginx and Traefik the package holds the lines to add.

FAQQuestions

Questions about Shield's limits

Does Shield replace a firewall or an antivirus?

No. It protects websites from bots, scrapers, attack probes and HTTP floods. Keep your firewall, backups and updates.

Does it stop DDoS attacks?

It stops HTTP floods (layer 7), like the one that took an online shop offline on 20 October 2026. It does not stop volumetric network DDoS, which has to be filtered before the server, by the hosting provider or by a network in front of the site (CDN).

Does it work on shared hosting?

No. Shield has to be installed on the server that receives the visitors, with Docker and administrator access, which shared hosting does not allow.

Which web servers are supported?

Apache (automatic install on Debian and Ubuntu), nginx and Traefik. Caddy, HAProxy and Windows servers are not supported.

Can I try it without risk?

Shield starts in observe mode and, after installing, checks that every site answers as before; on any difference it rolls back by itself. sudo shield uninstall puts the server back as it was.

→Read next

Protection that says where it stops

Shield installs in minutes on your Linux server and starts in observe mode: you see what it would stop before it stops anything.

Install Shield → See the plans →