Seedr

BitTorrent ratio master - emulates BT clients and reports simulated upload to private trackers.

Inspired by JOAL, built from scratch with TypeScript and Vue.js.

How It Works

Seedr loads .torrent files, connects to their trackers, and announces simulated upload data - without actually downloading or uploading any content. It emulates real BitTorrent clients (qBittorrent, Deluge, Transmission, uTorrent, BitTorrent) by replicating their exact announce behavior: peer IDs, key generation, URL encoding, headers, and query parameter ordering.

Key features:

• 5 built-in client profiles with accurate protocol emulation
• HTTP and UDP (BEP-15) tracker support with automatic failover
• Bandwidth simulation with weighted distribution and jitter
• Real-time web dashboard with drag-and-drop torrent upload
• Port reachability checker via check-host.net
• Docker support with persistent data volume
• Configurable upload ratio targets, simultaneous seed limits, and more

Is It Safe?

Yes. But like anything in life, don't abuse it. Don't upload thousands of torrents simultaneously with unrealistic upload speeds like 2 GB/s. While trackers can't tell the difference between Seedr and qBittorrent traffic, they can detect when someone's uploading content they never actually downloaded at speeds that are physically impossible for their connection.

Quick Start

Docker (recommended)

mkdir seedr && cd seedr
curl -O https://raw.githubusercontent.com/rursache/Seedr/master/docker-compose.yml
docker compose up -d

The web UI is available at http://localhost:8080. Drop .torrent files into the data/torrents/ directory or upload via the dashboard.

Docker manual

docker run -d \
  --name seedr \
  -p 8080:8080 \
  -p 49152:49152 \
  -v ./data:/data \
  ghcr.io/rursache/seedr:latest

Local development

Requires Node.js 22+.

# Install dependencies
npm install
cd ui && npm install && cd ..

# Start in development mode (hot reload)
npm run dev

The dev server starts the backend on port 8080 with hot reload. The frontend dev server proxies API requests to the backend.

Production build

npm run build && npm start

To preview the UI with mock data (no real network activity):

npm run build && npm start -- --demo

Port Forwarding

The BitTorrent port (default 49152) is the port that trackers and peers use to verify your client is reachable. This is the port you need to forward on your router/firewall, not the web UI port. The web UI port (8080) should stay local and not be exposed to the internet. If you really want to expose the WebUI port as well, make sure to enable auth!

Configuration

All configuration is managed through the web UI Settings panel. Settings are persisted to data/config.json.

Setting	Default	Description
Client Profile	qbittorrent-latest	Which BT client to emulate
Port	49152	Listening port announced to trackers
Min Upload Rate	100 KB/s	Minimum simulated upload speed
Max Upload Rate	500 KB/s	Maximum simulated upload speed
Simultaneous Seeds	-1 (all)	How many torrents to seed at once (-1 = unlimited)
Upload Ratio Target	-1 (unlimited)	Stop seeding after reaching this ratio (-1 = never stop)
Min Leechers	1	Only report upload when this many leechers are present
Min Seeders	1	Only report upload when this many seeders are present
Keep With Zero Leechers	true	Keep seeding torrents that have no leechers
Skip If No Peers	true	Don't report upload if no peers are connected

Environment Variables

Variable	Default	Description
PUID	1000	User ID to run as (for volume permissions, optional)
PGID	1000	Group ID to run as (for volume permissions, optional)
WEB_PORT	8080	Web UI and API port
USERNAME	(unset)	Username for web UI authentication (optional)
PASSWORD	(unset)	Password for web UI authentication (optional)
DATA_DIR	data	Root directory for config, state, torrents, and client profiles
CLIENTS_DIR	$DATA_DIR/clients	Directory containing .client profile files
TORRENTS_DIR	$DATA_DIR/torrents	Directory for .torrent files (watched for changes)
LOG_LEVEL	info	Log level (debug, info, warn, error)

Authentication

The web UI and API have no authentication by default - this is intentional since Seedr is designed to run locally or in Docker with only the BitTorrent port exposed to the internet.

To enable optional Basic Auth, set both USERNAME and PASSWORD:

# Docker Compose - uncomment the environment section in docker-compose.yml
environment:
  USERNAME: admin
  PASSWORD: changeme

# Docker manual
docker run -d --name seedr -p 8080:8080 -v ./data:/data \
  -e USERNAME=admin -e PASSWORD=changeme \
  ghcr.io/rursache/seedr:latest

# Local
USERNAME=admin PASSWORD=changeme npm start

When enabled, the browser will prompt for credentials when accessing the UI. All API endpoints and WebSocket connections are protected. If only one of the two variables is set, authentication remains disabled.

Client Profiles

Seedr ships with several .client profile files that define how it emulates a specific BitTorrent client. Each profile controls peer ID format, key generation algorithm, URL encoding rules, HTTP headers, and query parameter ordering to match the real client's announce behavior.

Profiles are stored in the data/clients/ directory and can be selected from the Settings panel. You can also add custom profiles by placing .client files in that directory.

API

Method	Endpoint	Description
GET	/api/config	Get current configuration
PUT	/api/config	Update configuration
GET	/api/config/clients	List available client profiles
GET	/api/torrents	List loaded torrents
POST	/api/torrents	Upload a .torrent file (multipart)
DELETE	/api/torrents/:hash	Remove a torrent
POST	/api/torrents/:hash/announce	Force an immediate announce
POST	/api/control/start	Start seeding
POST	/api/control/stop	Stop seeding
GET	/api/control/status	Get engine status
POST	/api/control/port-check	Check port reachability

Real-time updates are available via Socket.IO on the same port.

Tests

npm test              # Run once
npm run test:watch    # Watch mode

License

This project is licensed under the MIT License.