← Directory

Vettarr

Vettarr is a self-hosted gatekeeper that checks media requests — links, Telegram posts, magnets, .torrent files, and Seerr requests — against rules you set…

  • Automation
  • Downloaders
  • Media Applications
Vettarr is a self-hosted gatekeeper that checks media requests — links, Telegram posts, magnets, .torrent files, and Seerr requests — against rules you set for age ratings, genres, size, seeders, and your existing library, then approves, holds, or refuses them. Approved items go to qBittorrent, Radarr, Sonarr, or back to Seerr. Every decision keeps its reasons, and a shadow mode previews decisions without acting, so homelab media-library owners can see what it would allow before enabling it.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

GitHub stars
1
Open issues
0
Last commit
2026-10-14
Latest release
v1.0.2
License
AGPL-3.0
Activity
rising

Checked today - source: GitHub (GeiserX/vettarr)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Requirements Requires a PostgreSQL database (the official postgres template works) plus integrations such as Telegram, TMDB, Prowlarr, qBittorrent, and Radarr. source
  • Configuration One file configures vettarr: /data/config.yaml — copy config.example.yaml from the project and edit it, keeping secrets in container environment variables as ${VAR}. The database schema is created in an empty Postgres database on first start and upgraded automatically on later starts. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which file configures rules, and where should secrets go?

Edit /data/config.yaml, starting from config.example.yaml. Secrets should stay in the container's variables as ${VAR}.

Do I need to create the Postgres schema manually?

No. The database starts empty, and vettarr creates the schema on the first start and upgrades it on later starts.

How do I enable authentication for the web UI?

Run the vettarr web hash-password command, put the printed hash in .env as WEB_PASSWORD_HASH, and uncomment web.auth in config.yaml.

Which port should I use for the web UI?

The web UI is served on port 4850 according to the quick start.

Can I review items from a phone or Telegram?

Yes. The web UI has Inbox and Review pages usable from a phone, and the Telegram bot can push each item that needs you with the same actions.

Do approved items download immediately after setup?

Not from the example config. It starts in shadow mode, and no source reads anything or downloads until you turn sources and actions on.

Answers sourced from github.com

Community

No community discussions collected yet.