How to set up autobrr without Docker

Grabs releases the second they appear on your trackers, faster than the usual automation. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with autobrr

Its configuration is written before the container ever starts — including the web address it lives at, so autobrr generates correct links from the first page load instead of half-working behind a prefix.
Reached through your panel login. There is no second password to invent for autobrr and no port to open on your firewall.
autobrr keeps its filters, and the key that opens them, in its own store — and that key is made inside autobrr after you've created an account there. So sending its matches on to your download client, or to Sonarr, Radarr and Lidarr, is a step you make yourself.
When it asks where another app is, use the private address shown on that app's tile — the one in your browser's bar leads to the sign-in page instead, which is the usual reason this connection looks made and never works.

Why run autobrr yourself

The whole point of these tools is that they run unattended. On a desktop that gets shut down, they simply miss things.

What kind of server autobrr needs

These are small, patient programs. They spend most of their time asleep and wake up to check for something new, so 1 GB of memory covers several of them at once. What they need is to be running when you aren't watching.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run autobrr

autobrr runs wherever Cresdock runs, and the choice is about the machine, not the app:

At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so autobrr is reachable on your own network first and from outside only if you choose.
On a rented server. A small VPS is enough for most apps and is the usual answer when autobrr should be reachable from anywhere. The setup guide covers the specs and the one-command install.
Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so autobrr can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing autobrr

Put Cresdock on a server
One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.
Pick autobrr from the catalogue
Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.
Open it from your dashboard
Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  autobrr:
    image: ghcr.io/autobrr/autobrr:v1.82.1
    restart: unless-stopped
    ports:
      - "7474:7474"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./autobrr/config:/config

And that is the easy half. Still to do:

Install a reverse proxy and write a server block for it
Get a TLS certificate and set up automatic renewal
Create the folders above with the right ownership, or it will not start
Repeat all of it for the next app, and again on every server rebuild

On Cresdock, autobrr is one click and none of the above exists.

Common questions

Do I need to know Docker to run autobrr?

No. Cresdock installs autobrr in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. autobrr's configuration is written before it first starts, so it opens already set up.

What happens to my autobrr data when it updates?

Cresdock updates the autobrr image and leaves its stored data in place. autobrr keeps its own files in its own folder, which survives an update, a rebuild and a reinstall — and Cresdock never writes into it.

Can I run autobrr at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and autobrr is reachable on your own network first. A rented server is only needed when autobrr must be reachable from anywhere without a VPN.

Can I remove autobrr later?

Yes. Cresdock removes autobrr in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what autobrr itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: Bazarr · FlareSolverr · how autobrr connects to your other apps

Before you start: where to rent a server · what it needs to run · Cresdock vs QuickBox · the seedbox panel in full · sell workspaces to your customers