Shield · website protection · on your server

Your site stays up. Even under a bot wave.

Shield sits in front of your site, on your server. Customers and search engines get through; bots, scrapers and waves don't.

# Download the installer
curl -fsSLO https://luviner.com/downloads/shield-setup.py
# Pull Shield
docker pull luviner/shield:2.4
# Analyse the server (changes nothing)
python3 shield-setup.py analyze
# Write the package and install
python3 shield-setup.py plan
sudo ./ward-setup-*/install.sh

Linux with Docker. On Apache the install is automatic; on nginx and Traefik the package holds the lines to add.

Read the full documentation →
§01Measured on real traffic

A wave that took an online shop down. Replayed with Shield in front.

38s
to recognise a wave from 17,000 different addresses
−99%
requests reaching the site during the wave (from 122 to 1.2 per second)
0
customer actions refused (cart, login)
0
false alarms in a week of normal traffic

Real logs of a B2B shop on Magento that the wave had taken down for over an hour. Since 2 November 2026 Shield protects it in production.

§02The problem

Thousands of addresses, one request each. Per-IP limits never fire.

Together they take every connection, and customers find the site down. Shield looks at the traffic as a whole.

§03What it does

Protection that knows your site

01

Recognises waves

It knows how many new visitors usually arrive. When far more come, unknown ones get a short check in the browser.

02

Customers and Google always in

Customers hold a pass. Verified search engines, link previews and sitemaps always get through: SEO is untouched.

03

Stops attacks

Secret files, known exploits, login floods: refused before they reach the application.

04

If it stops, the site does not

With Apache and nginx, if Shield stops the site stays reachable. Visitor data never leaves the server.

§04How it installs

First it looks, then it installs, then it checks by itself that everything answers as before.

  1. Analyse

    Looks at the server without changing anything.

  2. Prepare

    Asks only what it cannot detect and writes the package.

  3. Install and verify

    Switches over in seconds and rechecks. If anything changes, it rolls back by itself.

  4. Observe, then protect

    Starts by observing. Once you have seen the data, you switch to full protection.

§05How it works

Ready-made rules.

Shield protects your site with ready-made rules: you never have to write one.

  1. 01 Shield Website protection Stops bots, scrapers and traffic waves. Customers and Google get through. →
  2. 02 Lynx Server monitoring Notices on its own when a server or container misbehaves. →

Protect your site from the next wave

The Community plan is free for one server, with every protection.

Install Shield → See the plans