Self-host Cap with Levelrail
A lightweight, privacy-friendly proof-of-work CAPTCHA, an alternative to reCAPTCHA or hCaptcha.
- Memory256 MiB
- Archarm64
- Services2
How to self-host Cap
-
Pull the images
2 images are pulled on your server.
Show images
tiago2/cap:3.0.4valkey/valkey:9-alpine
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Cap requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Cap. 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 Cap docs page.
Deploy Cap your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Cap from the CLI
levelrail-cli templates deploy cap-captcha --name my-cap-captcha Deploy Cap with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/cap-captcha/deploy Cap configuration
Cap services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| cap | tiago2/cap:3.0.4 | 3000 | none |
| valkey | valkey/valkey:9-alpine | none | cap_valkey_data -> /data |
Cap environment variables
| Variable | Service | Value |
|---|---|---|
| ADMIN_KEY | cap | Generated at deploy |
| REDIS_URL | cap | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: cap_valkey_data -> /data
Cap FAQ
How much memory does Cap need?
The catalog lists about 256 MiB of memory for Cap across its 2 services.
Does Cap run on arm64?
For Cap, an arm64 image is published; amd64 is image published.
Does Cap need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Cap bundle?
The template includes Redis, running as its own service.
Which ports does Cap use?
Cap listens on port 3000 inside the stack.
Where does Cap keep its data?
In a named volume: cap_valkey_data mounted at /data.
Can I deploy Cap on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Cap, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image tiago2/cap:3.0.4, valkey/valkey:9-alpine is what you deploy there.