arrow_back All applications
autobrr
Automation · For racers and freeleech hunters

autobrr

By the time you reach a torrent, it's been there for 12 seconds.

Overview

You often hit a torrent listed as 1 seed that already has 10? Those ten are running autobrr. You were still clicking refresh.

autobrr listens live to the IRC announce channels of private trackers. The moment a release drops, it grabs it, applies your filters, and pushes the .torrent to your client of choice. All within a few hundred milliseconds. While others are still reloading the tracker page.

Concretely: you write rules. "Every 2160p REMUX from this source by this group, freeleech, under 80 GB." autobrr handles the rest, 24/7, no sleep, no coffee, no misses. It only grabs what matches, and it grabs before anyone else.

It's the weapon of choice for people who take their ratio seriously. And for those who simply want the content on their seedbox before they've had time to hit Play on Plex.

autobrr dashboard

The dashboard. Each row is a release you caught while others were still asleep.

Highlights

IRC, in real time.

Tracker announcements hit IRC long before they show up in the browser. autobrr catches the packets the moment they land. Latency: tens of milliseconds. That's the difference between seeding 50 people and seeding nobody.

Filters for the picky.

Resolution, codec, source, releaser, year, language, min/max size, freeleech, internal, scene, P2P. All filterable. Combinable. Excludable. You want everything except French DTS-HD remuxes under 40 GB? Three checkboxes.

Wired into your stack.

qBittorrent, Deluge, Transmission, rTorrent. Sonarr, Radarr, Lidarr, Whisparr for Trakt lists and TMDB matching. Discord, Telegram, Notifiarr notifications. You stay in charge of the workflow, autobrr is just the spark at the start.

Visible logs, clear debugging.

Every release that passes through is logged. You see why a torrent was taken, or why it was rejected. No black box, no magic. If your filters let through too much or too little, you know exactly where to fix.

Integrated in your seedbox

autobrr does nothing on its own, it's an orchestrator. Here's what it wires up for you:

  • check_circle Direct push to qBittorrent, Deluge, Transmission, rTorrent, no manual download step.
  • check_circle Matching with Sonarr and Radarr: only releases that match your Plex or Jellyfin lists are sniffed.
  • check_circle Trakt watchlists, Letterboxd lists, Steam lists, MAM lists: you define what you want, autobrr only grabs that.
  • check_circle Discord, Telegram, Apprise, Notifiarr notifications: you get pinged when the torrent lands in your client.

Frequently asked questions

Do I need to be a command-line god to use it? expand_more
No. Everything happens through a web UI. You write your filters by ticking boxes and filling in fields. The only time you'll touch anything ugly is if you want to write a custom regex to match an exotic releaser. And even then, ChatGPT handles it.
Is it legal? expand_more
autobrr itself is an open-source tool that connects to IRC servers. Nothing illegal in the binary. What you do with it on your trackers, that's your story. We give you the tool, not the instruction manual for trouble.
Does it eat a lot of resources? expand_more
Written in Go, single binary, a few dozen MB of RAM even when watching ten trackers at once. You won't feel a thing on your seedbox, other than torrents arriving faster than usual.
Why isn't it in your 1-click stack? expand_more
Because it's a geek thing, and we own it. We offer it, we make it available, and after that it's between you, your favorite tracker, and autobrr's official docs. Our support is great, but it won't read your passkeys for you, and it won't write your regexes either. If you need someone to hold your hand setting this up, this probably isn't the tool for you.

If you know what a ratio is, you know why you're here.

A French seedbox, fast, and a team that knows IRC isn't dead.

See our plans arrow_forward