Anubis
Protect your sites from AI scrapers.
Anubis
techarohq/anubis:latest
Just deployed
Anubis
Weigh the soul of incoming HTTP requests using proof-of-work to stop AI crawlers.
Deploy and Host
About Hosting
Configuration
The variables in this template are the most likely to be used; for other configuration options, see the Anubis docs.
Why Deploy
AI scrapers have knocked down sites all over the web; protect yourself!
Common Use Cases
- Protecting a Git forge or personal site
- Keeping private data private
Dependencies for Anubis
None.
Deployment Dependencies
None.
Template Content
TARGET
The URL of the service that Anubis should forward valid requests to. You should set this within your private network; e.g. if you have an App service, you could set this to app.railway.internal:(your server port).
COOKIE_DOMAIN
The domain the Anubis challenge pass cookie should be set to. This should be set to the domain you bought from your registrar (EG: techaro.lol if your webapp is running on anubis.techaro.lol).
REDIRECT_DOMAINS
If set, restrict the domains that Anubis can redirect to when passing a challenge. If this is unset, Anubis may redirect to any domain which could cause security issues in the unlikely case that an attacker passes a challenge for your browser and then tricks you into clicking a link to your domain. Note that if you are hosting Anubis on a non-standard port (https://example:com:8443, http://www.example.net:8080, etc.), you must also include the port number here.
