Self-host Anubis with Levelrail
A reverse proxy that makes clients pass a small proof of work before reaching your site, which blocks most scraper bots. Sits in front of one upstream you choose. The signing key is generated for you.
- AuthorTecharoHQ
- LicenceMIT
- Memory64 MiB
- Services1
Needs setup: set TARGET before the first start.
How to self-host Anubis
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/techarohq/anubis:v1.28.2
-
Create the app
One service starts in a single Compose app, on port 8923.
-
Fill in the secrets
1 secret is generated and stored encrypted, 3 settings are preset, you provide 1 value.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Point a domain at this address. Requests that pass the challenge are forwarded to the upstream URL you entered.
Anubis requirements
- Memory
- About 64 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8923
- Domain
- Optional, an sslip.io address is used without one
- Settings
- 1 to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Anubis. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Anubis docs page.
Deploy Anubis your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Anubis from the CLI
levelrail-cli templates install anubis --name my-anubis --env ANUBIS_TARGET=VALUE Deploy Anubis with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/anubis/install \
-d '{
"name": "my-anubis",
"env": { "ANUBIS_TARGET": "VALUE" }
}' Anubis configuration
Anubis services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| anubis | ghcr.io/techarohq/anubis:v1.28.2 | 8923 | none |
Anubis environment variables
| Variable | Service | Value |
|---|---|---|
| BIND | anubis | Preset by the template |
| DIFFICULTY | anubis | Preset by the template |
| ED25519_PRIVATE_KEY_HEX | anubis | Generated at deploy |
| METRICS_BIND | anubis | Preset by the template |
| TARGET | anubis | You must set this |
Ports and volumes
- Ports
- 8923
- Volumes
- none
Anubis FAQ
How much memory does Anubis need?
The catalog lists about 64 MiB of memory for Anubis.
Does Anubis run on arm64?
For Anubis, arm64 support is not confirmed; amd64 is unknown.
What licence is Anubis under?
Anubis is licensed under MIT, which is permissive, with few conditions on reuse.
Does Anubis need configuration before it starts?
Yes. Anubis has required settings: TARGET.
Which ports does Anubis use?
Anubis listens on port 8923 inside the stack.
Can I deploy Anubis on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id anubis for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/techarohq/anubis:v1.28.2 is what you deploy there.