# A download accelerator.

A program that splits one file into parts and fetches them over every link at once. For big downloads it is free, with no server to run. It speeds up its own downloads and nothing else.

## One program’s downloads.

A download accelerator works inside one program. Everything else on the computer still uses one link.

The same traffic with a download accelerator, and with Fenris. With the accelerator, a file it fetches is split over both links, while a video call and everything else stay on one. With Fenris, a file in any program is spread over both links, the call stays on the quickest with a copy on the other, and everything else can use both.

Two links, fibre and 5G. Wi-Fi and Ethernet to the same router are one line behind it, so neither approach gains anything from that pair.

## What each one is

The first row is described from the page of Plexo, a free download manager of this kind: [github.com/anmolkapil/plexo](https://github.com/anmolkapil/plexo). Checked on 22 Nov 2026.

**A download accelerator**

It asks for a file in several parts, each over a different link, and joins them on your disk. In Plexo’s words, “faster connections handle more of the file”, and it “requires no VPN or virtual network adapter”.

**Why it needs no server**

The website’s own server hands out the parts. Each part is an ordinary download over one link.

**Bonding**

In our words: every connection from every program is spread over every link, piece by piece, and put back together at a server you run.

## Situation by situation

| Situation                                     | A download accelerator                                                               | Fenris                                                               |
| --------------------------------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------- |
| One big download                              | Every link at once, with no server to run.                                           | Every link at once, through your server.                             |
| What it costs to set up                       | One program to install. Plexo is free.                                               | A server at the far end, and Fenris on each device or on the router. |
| A website that won’t hand out a file in parts | One link. In Plexo’s words, “Servers without range support use a single stream.”     | No difference. The website sees one ordinary connection.             |
| A video call                                  | Not carried. It stays on one link.                                                   | On the quickest link, with a copy on a second.                       |
| A game, a stream, a web page                  | Not carried.                                                                         | Carried, each kind its own way.                                      |
| A link drops                                  | Its downloads may carry on over the links left. Everything else on that link breaks. | The other links carry what was open.                                 |
| Other devices in the house                    | Each needs the program, for its own downloads.                                       | A router with Fenris covers every device behind it.                  |
| The address websites see                      | Each link’s own.                                                                     | Always your server’s.                                                |
| The road your traffic takes                   | Straight out.                                                                        | By way of your server: a detour, small when the server is near.      |

## Why calls are different

A download can be cut into parts because the whole file already sits on a server, and any part can be asked for again. A call has no parts to ask for: each moment is made once, and is too late a moment after.

So a call can’t be kept going from one end alone. Something at the far end has to take the same call over another link, **from the same address**. That is what a server gives you, and it is what bonding costs.

[How it works, step by step](https://fenris.network/how-it-works)

## Which to choose

- **A download accelerator, if big downloads are all you want faster.** There is no server to run, and Plexo costs nothing. For that one job it is the simpler tool.
- **Fenris, if calls and everything else should use every link too.** And if what is open should carry on when a link drops. It costs a small server at the far end. [Ask for early access](https://fenris.network/early-access)
- **Neither, if you have one link.** There is nothing to split a download over, and nothing to bond. One link can’t be made faster.
