Pick swizzin if the seedbox is yours alone and you want the quicker installer and a server panel. Pick PMSS if several people will share the server, because PMSS gives each user their own memory and CPU limits, disk quota and private process list, and swizzin sets none of those up by default. That is what came out of installing both with their own installers on the same size of Debian 12 virtual machine on 2026-10-29 and scoring each on the same 60 points. PMSS is Pulsed Media's own open-source stack, so its weak points are on this page as plainly as its strong ones.
Which one to install
Your situation
Install
Why (points below)
Several people share one server
PMSS
Per-user memory and CPU limits, disk quotas, hidden processes and per-user traffic counters (17-24)
One person, one server, wants a web panel
swizzin
Finished in one go on the test VM; panel with an admin view; HTTP redirects to HTTPS (8, 40-44)
A server you will update for years
PMSS
One update command with rollback to a named release, a documented Debian major upgrade, config templates, client watchdogs (46-52)
How the points were scored
The 60 points were written before either stack was scored, and the same list is used for every PMSS comparison. Each point scores 2 (yes), 1 (partly) or 0 (no). Points that are measurements (install time, packages, disk, memory, ports, issue replies) show the measured value instead of a score. "Not established" means the test could not show it either way; those points count for neither stack. Totals are given per category, never as one number, because a different number of points apply to each stack.
Only what each project's own public installer puts on a fresh server counts, plus its own documentation and source code. Pulsed Media hosting features, such as account setup or AI credits, score nothing for PMSS. Evidence comes from our install run, the project's documentation or its source code, and each row names which.
Each stack went onto a fresh virtual machine with 6 vCPU, 3 GB RAM and a 32 GB disk on the same host. PMSS also got a separate 40 GB /home disk, because its installer checks for one. The test created no PMSS seedbox user, so the PMSS per-user points (18-19, 22, 38, 40, 42-43) were read from source code and installed files rather than tried as a user. That is the place where this comparison could lean toward PMSS, and it is marked in each row.
Scores by category
Share of the applicable points each stack scored per category. The two stacks tie only on torrent clients.
The 60 points
A. Project and openness: PMSS 8 of 10, swizzin 6 of 10
#
Point
PMSS
swizzin
Evidence
1
Whole stack under an OSI licence, no closed parts needed to run it
2
2
Both GPL-3.0. The PMSS default install also downloads some third-party binaries (Resilio Sync, FileBot, AI command-line tools) whose licences were not reviewed.
2
No paid tier, licence key or phone-home needed for any core feature
1
2
Neither has a paid tier or licence key. PMSS loads part of its panel from pulsedmedia.com at page load by default (local fallback and an opt-out exist). swizzin: none found.
3
Actively developed: commits to the default branch in the last 90 days, with tagged releases or a stated update channel
2
0
PMSS: commits to main daily, releases on 2026-09-28, 10-10 and 10-21. swizzin: last master commit 2026-02-13, over 90 days before the test.
4
Maintainers answer issues: median days to a first maintainer reply over the last 20 issues
0.3 days; 19 of 20 answered
16 of 20 unanswered
Last 20 issues opened by outside users. Most PMSS replies come from the project account, which includes Pulsed Media's AI sysadmin; 14 of the 20 issues came from one contributor.
5
Documentation covers install, update, adding users, each app, uninstall and extending
1
1
Both document install, update and users. PMSS has no per-client user pages and no full uninstall; swizzin has no full uninstall and some apps without a page.
6
Automated tests or CI in the repository
2
1
PMSS CI lints and runs unit tests. swizzin CI checks issue templates and file modes; per-app test scripts run by hand. Neither tests the install in CI.
The swizzin installer checklist: nginx, the panel and a torrent client in one run (point 8).
B. Install and footprint: PMSS 9 of 12, swizzin 10 of 12
#
Point
PMSS
swizzin
Evidence
7
Supported OS list includes current releases (Debian 12/13, Ubuntu 24.04)
1
1
PMSS: Debian 10 to 13 (13 experimental), no Ubuntu. swizzin: Debian 11/12 and Ubuntu 20.04 to 24.04, no Debian 13.
8
One-command install from the project's official instructions
1
2
Both have a one-line install. On our test VM the PMSS install exited with an error and needed two update runs, and it stopped in an editor to confirm the hostname. swizzin finished in one go.
9
Unattended (scripted, no prompts) install mode
2
2
PMSS --non-interactive, swizzin --unattend. Neither was run in this test.
10
Install time on the shared test bed
about 220 min incl. two update runs
about 18 min
One sample each. The PMSS run shared a heavily loaded host (load near 50, guest CPU steal up to 44%); swizzin ran earlier the same day.
11
Packages added by the install (dpkg count before and after)
+1,050
+203
dpkg package count after install minus before. PMSS installs its whole app catalogue up front; swizzin installs apps on demand.
12
Disk used after install (GB)
8.5 GB
2.7 GB
Space used on / after install. PMSS also put 1.2 GB of client builds on /home.
13
Idle RAM and CPU after install, measured with nothing added
319 MiB in processes, no users
395 MB used
Not the same measure: PMSS is the sum of process memory; swizzin is "used" from free. PMSS also reserves 1 GiB for the kernel, a third of a 3 GB VM.
14
Works without a reboot, or says clearly when one is needed
2
2
Both came up without a reboot. The PMSS README asks for one after install.
15
Host prerequisites it needs and checks (separate /home, FQDN, free space)
1
1
PMSS checks for a separate /home and free space; swizzin checks for root only. Neither checks the FQDN or RAM.
16
Installer can be re-run or updated in place without breaking an install
2
2
PMSS: re-running its update command repaired the failed install. swizzin: box update.
C. Users and isolation: PMSS 14 of 14, swizzin 9 of 16
#
Point
PMSS
swizzin
Evidence
17
Multi-user (several independent seedbox users on one server)
2
2
Both add, remove and change users from the command line.
18
One torrent client process per user, run as that user
2
2
Both run each user's torrent client as that user. PMSS also puts it in the user's own cgroup.
19
One web front end per user (or per-user routing) with no cross-user access
2
2
Both route each user to their own web service with their own login. Read from source; no two-user test.
20
Per-user CPU, RAM and I/O limits
2
0
PMSS caps memory, tasks, CPU and I/O weight per user. swizzin sets no per-user limits.
21
Per-user disk quotas
2
1
PMSS turns on disk quotas at install. swizzin has them as an optional app.
22
Users cannot see other users' processes
2
0
PMSS mounts /proc with hidepid, so users do not see each other's processes. swizzin does not.
23
Users cannot read other users' files by default
not established
2
swizzin homes are mode 750. PMSS: no user was created in this test, so not checked.
24
Per-user traffic accounting and bandwidth shaping
2
0
PMSS counts and can shape traffic per user. swizzin has server-wide traffic counters only.
ruTorrent, the rTorrent web interface PMSS ships to every user.swizzin asks which qBittorrent build to install (point 29).
D. Torrent clients: PMSS 12 of 12, swizzin 12 of 12
#
Point
PMSS
swizzin
Evidence
25
rTorrent with ruTorrent
2
2
Both. PMSS ships four prebuilt rTorrent versions; its older from-source build failed in our run (see below).
26
qBittorrent
2
2
Both. qBittorrent was the client installed and tested on swizzin.
27
Deluge
2
2
Both.
28
Transmission
2
2
Both.
29
Choice of client version, or several clients per user
2
2
PMSS keeps several builds per client and has a version picker in the panel. swizzin asks for the qBittorrent version at install.
30
Clients ship with tuned defaults (diff of the shipped config against the client's upstream defaults)
2
2
Both change the clients' upstream defaults (connection limits, buffers, preallocation).
The swizzin app list at install; more apps install later with box install.
E. Apps and tools: PMSS 17 of 18, swizzin 13 of 18
#
Point
PMSS
swizzin
Evidence
31
Sonarr, Radarr, Prowlarr and the other *arr apps
2
2
Both offer Sonarr, Radarr and Prowlarr.
32
Plex, Jellyfin or Emby, with ffmpeg available
2
2
Both offer Jellyfin and ffmpeg; swizzin also offers Plex and Emby.
33
Usenet clients (SABnzbd or NZBGet)
2
2
Both install SABnzbd and NZBGet.
34
rclone available to users
2
2
Both.
35
Backup tools (borg or restic) available to users
2
0
PMSS installs borg and restic. swizzin has neither.
36
Remote access: SSH shell, SFTP and FTP(S), with sane limits
1
1
Both give SSH and SFTP. PMSS FTP has no TLS (a known open issue); swizzin FTP is an optional app with TLS but no per-IP limit.
37
File browser in the web interface
2
2
Both.
38
Docker for users without root (rootless)
2
0
PMSS sets up rootless Docker per user. swizzin has no Docker module.
39
WireGuard or another VPN client for users
2
2
PMSS runs WireGuard and OpenVPN servers for users. swizzin offers WireGuard.
The swizzin panel login, served over HTTPS with a self-signed certificate (points 40-42).
F. Web interface: PMSS 8 of 10, swizzin 10 of 10
#
Point
PMSS
swizzin
Evidence
40
A dashboard or panel ships with the stack
2
2
Both. PMSS has a per-user panel; swizzin a server panel.
41
HTTPS by default on the web interface
1
2
Both serve a self-signed certificate. swizzin redirects HTTP to HTTPS; PMSS serves its landing page over plain HTTP.
42
Login required on every web UI it installs
2
2
Both require a login for every app. The PMSS root page is a static landing page.
43
Panel shows the user's resource use (disk, traffic)
2
2
Both show disk and traffic. PMSS was read from source (no user to log in).
44
Admin view for the server owner
1
2
swizzin's panel has admin-only cards. PMSS has command-line admin tools only.
45
Usable at phone width (panel screenshot at 390 px)
not established
not established
Not tested at 390 px for either.
G. Operations: PMSS 14 of 14, swizzin 9 of 14
#
Point
PMSS
swizzin
Evidence
46
One update command for the whole stack
2
2
PMSS: one update command. swizzin: box update.
47
Updates keep user data and settings; a documented way back if one fails
2
1
PMSS can roll back by naming an earlier release. swizzin has no stack rollback.
48
Remove an app cleanly
2
2
Both remove apps by command.
49
Service configs generated from templates (edits survive updates the documented way)
2
1
PMSS writes service configs from templates with documented local overrides. swizzin writes configs inline, and box update resets its own scripts.
50
Health checks or automatic restart of failed per-user services, with logs
2
1
PMSS checks and restarts each user's clients from cron, with logs. swizzin sets automatic restart on many apps but not on its torrent clients.
51
Major OS release upgrade path documented (e.g. Debian 12 to 13)
2
1
PMSS has a documented major-version upgrade command. swizzin has a guide that says major upgrades are not officially supported.
52
Admin CLI or API for the user lifecycle (add, suspend, delete, change plan)
User and data migration between servers (a tool or documented method)
2
2
PMSS has a user transfer tool. swizzin documents an rsync method.
60
Where to get help: issue tracker, forum or chat, documented and answered within the last 90 days
2
1
PMSS: Discord, and GitHub issues answered within days; Pulsed Media gives no free support for PMSS on your own server unless the server was bought from Pulsed Media. swizzin: Discord and GitHub Discussions; answer times not checked.
Where swizzin is ahead
The swizzin installer is lighter and finished in one run on the test VM (points 8 and 10-12). It installs apps when asked rather than all at once. Its panel has admin-only cards and plain HTTP is redirected to HTTPS. Its catalogue adds Plex and Emby.
Where PMSS is ahead
PMSS is built for a server several people share. Each user's torrent clients run inside the user's own resource limits, disk quotas are on from the start, /proc hides other users' processes, and traffic is counted per user. Upkeep is where the gap is widest: configs come from templates with documented local overrides, cron checks restart each user's clients and log it, an update can be rolled back to a named release, and a Debian major upgrade is one documented command. It also installs borg and restic, sets up rootless Docker per user and applies network tuning (BBR, larger socket buffers). The project is under daily development; swizzin's last commit to its main branch was in February 2026.
What went wrong with PMSS in this test
The PMSS install did not go cleanly, and these failures are part of its score:
The installer stopped in a text editor to confirm the hostname. The --hostname and --non-interactive flags avoid that, but the one-line install in the README does not use them (point 8).
On a heavily loaded host the first package step hit PMSS's 20-minute limit per command. That interrupted dpkg, and the update exited with an error because the retries in the same run do not repair an interrupted dpkg first. Running the update command again repaired it.
The older from-source rTorrent build ran out of time on the first rerun and out of memory on the second (it compiles with 12 jobs on a 3 GB VM), and the update still reported success both times. The four prebuilt rTorrent versions were installed, and the default one started.
PMSS reserves 1 GiB of memory for the kernel whatever the RAM size. On a 3 GB VM that is a third of the memory.
FTP has no TLS, and the landing page on port 80 is served over plain HTTP (points 36 and 41).
For one person on their own server, install swizzin: it is quicker to set up and its panel is the better single-user dashboard. For a server several people share, or one you plan to keep updating for years, install PMSS: per-user limits, hidden processes, per-user traffic counters, rollback to a named release and a one-command Debian upgrade are things swizzin does not have, while swizzin's leads over PMSS are matters of setup comfort.
Rather not run the server yourself? Pulsed Media seedboxes run PMSS in Pulsed Media's datacenters in Finland, with the updates and monitoring done for you. See the seedbox plans.
See also
Swizzin — what swizzin is, where it came from and how its box command works
