Deluge

That split is the whole design. It means one Deluge running on a machine in a cupboard can be driven from a desktop window, a terminal or a browser, on the same computer or from anywhere on the network, and it is the reason people describe Deluge as a service with a face on it rather than as an application.

What Deluge is and who makes it

Deluge is a client program that speaks the BitTorrent protocol, so it reads a torrent file or a magnet link, finds peers, trades pieces and hashes each one before it writes it to disk. How a transfer works covers that sequence. What distinguishes Deluge from its two siblings is that it ships three official interfaces onto one daemon, a desktop window, a console interface and a web interface, and that almost every feature beyond the core arrives as a plugin rather than as a preference.

The project is volunteer software written mostly in Python, published under a free software license, with the source public and no advertising, no bundled offers and no paid edition anywhere in it.

What engine Deluge runs on

Deluge runs on libtorrent, the same C++ engine qBittorrent uses, reached from Python through the library's own bindings. Everything at protocol level therefore comes from libtorrent: the distributed hash table, peer exchange, local peer discovery, protocol encryption, the microtransport protocol and the piece picker that asks for the rarest pieces first.

Two things follow. Deluge and qBittorrent move data at much the same rate on the same swarm, because the same code is doing the moving, and any comparison claiming otherwise is describing the interface or the defaults. And Deluge carries a Python runtime in addition to the engine, which is the cost of the plugin system and shows up as a larger memory footprint than a client that carries no runtime of its own.

How Deluge is driven

Deluge is driven through whichever of its three interfaces suits the machine, all of them talking to the same daemon.

• The desktop interface opens a window on Windows, macOS or Linux. In its default mode it starts a private daemon for you and behaves like an ordinary application; in thin client mode it connects to a daemon running elsewhere.
• The console interface runs in a terminal, which is how a headless server is driven when nobody wants a browser open.
• The web interface is a small server that speaks to the daemon and serves a page, on port 8112 by default, so any browser on the network becomes the interface.

The daemon itself listens for its interfaces on port 58846. Close every interface and transfers keep moving, because the interface was never the thing doing the work. That is the single behavior that most surprises people arriving from a one window client.

What Deluge does that qBittorrent and Transmission do not

Deluge is extensible by design, and that is its real difference. Features that other clients either build in or leave out are plugins here: labeling transfers into groups, adding torrents automatically from a watched folder, scheduling bandwidth by hour and day, running a command when a transfer completes, applying a blocklist, sending notifications, and serving the web interface itself. Each is switched on individually, and anybody who writes Python can add another.

Transmission also splits daemon from interface, but keeps a fixed feature set and no extension mechanism at all. qBittorrent puts a comparable feature set in the core program with no plugin layer. Deluge is the one that lets you assemble the client you want, and the one that asks you to.

What Deluge leaves out on purpose

Deluge leaves the core deliberately thin. A fresh installation does less than a fresh qBittorrent installation, because the project's answer to most feature requests is a plugin rather than a preference. It also leaves out every revenue mechanism: no advertising in the window, no offers in the installer, no telemetry, no premium tier. And like every client, it leaves out any promise about privacy, since the protocol requires peers to reach each other by address. The swarm sets out what the other peers can see.

Where an official Deluge build comes from

An official build comes from the Deluge project or from your operating system's package manager, and on Linux the second route is the usual one, since Debian, Ubuntu, Fedora and the BSD ports trees all package it. The project publishes the source and its own builds for Windows and macOS. Verify the published checksum or signature, and refuse any installer offering a toolbar, a search bar or a system cleaner during setup, because the project ships none of those. A download portal that wraps somebody else's installer in its own is not part of the chain, whatever the icon on it looks like.

Whether Deluge, and the torrent files it opens, are safe

Yes for the program, and mostly yes for the files, with one distinction that matters. Deluge itself is open source, publicly readable and free of anything but the client in the builds the project publishes. A torrent file is a separate question, and it is not the risk people assume: it is a small metadata file listing names, sizes, piece length and a hash for every piece, it contains none of the data and it cannot execute. Opening one tells your client what to go and ask for. The risk lives entirely in what arrives afterwards, and the hash check proves only that the pieces match the metadata, never that the result is harmless. Is it safe? deals with that properly.

Who Deluge suits, and who it does not

Deluge suits somebody who wants one client running permanently on one machine and reached from several others, and who is willing to switch on the pieces they need. A home server, a spare machine or a workstation that stays on all week is the case it was designed for, and the thin client mode is what makes it pleasant rather than merely possible.

It suits somebody less well if they want a program that is complete the moment it is installed. Anyone in that position is better served by qBittorrent, which puts the same class of features in the core with nothing to enable, and The clients compares all three on the axes that genuinely differ.