---
title: "Deploy Autobrr"
description: "Modern, easy to use download automation for torrents and usenet"
category: "Storage"
url: https://railway.com/deploy/autobrr
---

# Deploy Autobrr

Modern, easy to use download automation for torrents and usenet

**[Deploy Autobrr on Railway](https://railway.com/template/autobrr)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/autobrr/manifest.json

- **Creator:** OpenSource Templates
- **Category:** Storage
- **Total deploys:** 1

## Template content

### Autobrr https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/autobrr.svg

- **Image:** ghcr.io/autobrr/autobrr:v1.87.0
- **Public domain:** Yes

## Documentation

# Deploy and Host Autobrr on Railway

Autobrr is a modern, easy-to-use download automation tool for torrents and Usenet. It monitors IRC announce channels and RSS feeds, applies powerful filters, and pushes matching releases to your download clients (qBittorrent, Deluge, rTorrent, Transmission, SABnzbd, and more).

[![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/new/template/autobrr)

## About Hosting Autobrr

Hosting Autobrr on Railway runs a single container using the official image `ghcr.io/autobrr/autobrr:v1.87.0`. Configuration and database live on a persistent volume at `/config`. The web UI listens on port 7474 and is exposed through Railway’s public HTTPS domain. `RAILWAY_RUN_UID=0` is set so the process can write to the Railway volume without permission issues.

After the first deploy, open the public URL, create your admin account, then add indexers, filters, and download clients.

## Common Use Cases

- Automatically grab new releases from private trackers the moment they are announced on IRC
- Filter by resolution, codec, group, size, freeleech, and dozens of other rules
- Push matches to qBittorrent, Deluge, rTorrent, Transmission, or Usenet clients
- Cross-seed and automation workflows without manual searching
- Lightweight alternative to more complex automation stacks while keeping full control of filters and actions

## Dependencies for Autobrr Hosting

- **Autobrr image:** `ghcr.io/autobrr/autobrr:v1.87.0`
- **One persistent volume** at `/config` (config + internal database)
- **Railway public domain** mapped to port 7474
- No external database required (SQLite is used by default)

Optional: connect Autobrr to your existing download clients (qBittorrent, etc.) over the network or via another Railway service on the same private network.

Upstream: [Autobrr Docs](https://autobrr.com) · [GitHub](https://github.com/autobrr/autobrr) · [Discord](https://discord.gg/autobrr)

### Implementation Details

| Item              | Value                                      |
|-------------------|--------------------------------------------|
| Image             | `ghcr.io/autobrr/autobrr:v1.87.0`          |
| Web UI port       | `7474`                                     |
| Config volume     | `/config`                                  |
| `RAILWAY_RUN_UID` | `0` (required for volume write access)     |
| Domain            | `${{RAILWAY_PUBLIC_DOMAIN}}`               |

## Topology

| Service     | Role                          | Volume    | Public | Notes                          |
|-------------|-------------------------------|-----------|--------|--------------------------------|
| **Autobrr** | Download automation + web UI  | `/config` | Yes    | Port 7474, runs as root (UID 0)|

#### Volumes (drives) — what to mount

The volume is already defined in the template.

| Mount path | What is stored                                      |
|------------|-----------------------------------------------------|
| `/config`  | Configuration, SQLite database, logs, session data  |

Do **not** remove the volume — settings, filters, and history will be lost on the next deploy.

## Quick Start

1. Click the **Deploy on Railway** button above.
2. Sign in (or create a free Railway account) and deploy.
3. Wait 1–2 minutes for the service and volume to come up.
4. Open the **Autobrr** service → **Settings** → **Networking** and open the generated public domain.
5. Create your admin account on the first-run setup screen.
6. Add indexers (IRC or RSS), create filters, and connect your download clients.

That’s it. Autobrr will start monitoring and acting on matching releases.

## Configuration

Most settings are managed in the web UI after the first login. Container-level variables:

| Variable           | Default                        | Notes                                      |
|--------------------|--------------------------------|--------------------------------------------|
| `PORT`             | `7474`                         | Internal listen port (Railway proxies it)  |
| `DOMAIN`           | `${{RAILWAY_PUBLIC_DOMAIN}}`   | Public domain for the service              |
| `RAILWAY_RUN_UID`  | `0`                            | Required so the process can write to `/config` |

You can add further Autobrr environment variables (prefixed `AUTOBRR__`) if needed — see the [official configuration docs](https://autobrr.com/configuration).

### Custom Domain

1. Autobrr service → **Settings** → **Networking** → **Custom Domain**.
2. Add your domain and follow Railway’s DNS instructions.
3. Railway provisions TLS automatically.
4. Access the dashboard at `https://your.custom.domain`.

## Updating Autobrr

1. Autobrr service → **Settings** → **Source**.
2. Change the image tag (e.g. `v1.87.0` → a newer release).
3. Redeploy.

Configuration and data are preserved by the `/config` volume. Check the [Autobrr releases](https://github.com/autobrr/autobrr/releases) before upgrading.

## Traps

**Ways this still fails:**

- **Volume permissions** — Without `RAILWAY_RUN_UID=0` the container cannot write to the Railway volume and will fail to start or lose data.
- **Missing `/config` volume** — Settings, filters, and the internal database live here. Detach it and everything resets on the next deploy.
- **Download clients not reachable** — Autobrr must be able to reach your torrent/Usenet client. Prefer private networking if the client is also on Railway, or ensure the public/private IP and ports are correct.
- **IRC indexers behind firewalls** — Some private trackers require specific IRC server access; make sure outbound connections from Railway are allowed.
- **First login** — You must create the admin account on the initial setup screen; there is no default username/password.

View live logs: service → **Deployments** → latest deployment → **View Logs**.

## Why Deploy Autobrr on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Autobrr on Railway, you get a modern, always-on download automation tool with persistent storage and automatic HTTPS — ready to talk to your download clients with minimal setup.



## Similar templates

- [Garage S3 Storage](https://railway.com/deploy/garage-s3-storage) — Ultra-light S3 server: fast, open-source, plug-and-play.
- [Redis](https://railway.com/deploy/redis-1) — Self Host Latest Redis with Railway
- [EasyImg](https://railway.com/deploy/easyimg) — Simple self-hostable Nuxt.js personal image hosting system.

Open this page in a browser: https://railway.com/deploy/autobrr