Self-hosted service
saltyorg/Saltbox avatar
saltyorg/Saltbox

Saltbox has no dashboard, refuses ARM, and ranks cloud storage last

Ansible-based solution for rapidly deploying a Docker containerized cloud media server.

892 stars88 forksPythonGPL-3.0

At a glance

What is it?
Ansible playbooks that deploy a Docker media server on a single cloud VM, derived from an older project of the same shape. The README is mostly a support matrix, a list of applications and a wall of contributor avatars; everything else lives on a documentation site.
Who is it for?
Use Saltbox if you want a whole media stack on one machine without assembling the containers yourself, and you are willing to configure it from a terminal. Three things to check before you start.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 22, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • saltyorg/Saltbox892 ★ · +7
Star history
Repository2026-09-122026-11-22
saltyorg/Saltbox885892

7 Stars in the last 71 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

There is no dashboard and no interface of its own

The most important line in the README is a note, and it says the project does not have a dashboard or a graphical interface of its own, and that every Saltbox-specific setup step and command is done in text editors and on the command line. That shapes everything else on the page. There is no screenshot of a control panel, no toggle to describe, no first-run wizard. The documentation link is the only manual, and the README's job is to tell you whether you are eligible to proceed. Worth pairing with the application list, which includes several dashboards and admin panels for other tools: the software it installs has interfaces, the software that installs it does not.

The support matrix is four separate refusals

Four lines in the README each rule something out, and reading them together gives you the deployment envelope. Fresh installations are supported on x64 machines running Ubuntu Server 24.04 or 26.04 LTS. Non-LTS releases of Ubuntu are not supported, and neither are Desktop installs, which is the distinction people most often get wrong when they have a workstation rather than a server image. Distributions other than Ubuntu are not supported, which rules out the other well-trodden server distributions people reach for. And ARM processors are not supported at all, which excludes most inexpensive cloud instances and every current Apple Silicon machine. So the eligible target is narrow: a 64-bit Intel server running a supported long-term-support release of Ubuntu Server.

New machines get two releases, existing ones keep a third

The version support is not one rule but two, and the difference matters when you are sizing hardware. A fresh installation must be on Ubuntu Server 24.04 or the newer 26.04 long-term-support release. An existing 22.04 long-term-support machine is still supported, but only as something already deployed. In other words the older release is a maintenance window, not an option: you can keep running what you have, and you cannot start there. Anyone provisioning a new VM and reaching for the most widely documented LTS release will find it is the one version the project will not install onto, which is the sort of thing that turns into an afternoon of image hunting.

Storage is the third function, not the first

The README states three primary functions and puts them in an order that does not match the one-line description. First is the automatic acquisition of media. Second is the ability to play it back from anywhere and from any device. Third, and explicitly to a lesser extent, is storing that media on the cloud. The repository description calls it a cloud media server, which reads as storage first, so the priority order is the useful thing here: the project is built around getting content in and playing it back, with the cloud mount as a supporting capability rather than the point. The application list supports that reading, since most entries are about acquisition and playback rather than about storage.

The application list mixes four different jobs

Nineteen applications are named before the list trails off, and they fall into four groups that are worth telling apart. Playback is Plex and Emby. Acquisition is Sonarr, Radarr and Lidarr, backed by SABnzbd for usenet, NZBHydra2 and Jackett as indexers, and Overseer for requests. Transfer and cloud movement is Rclone. Maintenance is Autoscan, Cloudplow, Plex Dupefinder and Plex Patrol, all of which exist to keep a library clean rather than to grow it. And the observability and administration layer is Tautulli, Traktarr, Organizr and Portainer, which is a container management interface for the whole stack. That last group is what you would reach for instead of a Saltbox dashboard.

The donation link and the repository have different owners

Small thing, but it is the kind of detail that catches you out when you are following a link from a README on a phone. The project asks for a donation and the link points at a different account from the one hosting the repository. The repository is filed under one organisation-style name and the sponsor link uses another. The README also carries a thank you to a commercial tool vendor for free licences for their tools, which is worth knowing because it tells you which editor and which automation tool the maintainers develop against. After that comes the longest part of the page: an HTML table of contributor avatars, several dozen accounts, each rendered with a picture element that switches on the reader's colour scheme.

Two linter configs, a uv toolchain, and no tagged releases

The repository root shows what kind of project this is. There is an Ansible configuration file and one main playbook, plus the directories an Ansible project needs: roles, an inventory, defaults, a library of custom modules, filter plugins, lookup plugins, resources and scripts. Galaxy requirements live in their own file. Two lint configurations sit side by side at the root, one for Ansible and one named after the project, which is what happens when a project outgrows the upstream linter's defaults. A schema directory suggests configuration is validated rather than trusted. The Python toolchain is pinned through a version file and a separate version file for the package manager, and there are backup and announcements files at the root, both of which imply scheduled operations rather than manual ones. There are no GitHub releases at all, so none of this is versioned in the usual way.

Editorial conclusion

Use Saltbox if you want a whole media stack on one machine without assembling the containers yourself, and you are willing to configure it from a terminal. Three things to check before you start. It refuses ARM processors and anything that is not Ubuntu Server, so a cheap ARM instance or a non-Ubuntu host is out. It has no interface of its own, so every action is a command and the documentation site is the manual. And with no tagged releases at all, there is no version to pin to: you are tracking the default branch, so read the support matrix for the release you are installing rather than trusting a version number.

Frequently asked questions

Does Saltbox have a web interface?

No. The README states it has no dashboard or graphical interface of its own, and that all Saltbox-specific setup and commands are done in text editors and on the command line.

Which operating systems can Saltbox be installed on?

Ubuntu Server only, and only long-term-support releases. Fresh installs are supported on 24.04 and 26.04 LTS on x64 machines, existing 22.04 LTS installations remain supported, and non-LTS releases, Desktop installs, other distributions and ARM processors are all unsupported.

What are Saltbox's primary functions, in order?

Automatic acquisition of media first, playback from anywhere and any device second, and storing the media on the cloud third, which the README describes as being to a lesser extent.

Which applications does Saltbox deploy?

Nineteen are named: Plex, Emby, Sonarr, Radarr, Lidarr, Rclone, SABnzbd, Tautulli, NZBHydra2, Jackett, Overseer, Autoscan, Cloudplow, Organizr, Portainer, Traktarr, Plex Dupefinder and Plex Patrol, plus others not enumerated.

Is Saltbox based on another project?

Yes. The README says it is heavily based on Cloudbox, and it is implemented as Ansible playbooks with roles, an inventory, custom modules, filter and lookup plugins, and its own playbook at the root.

Does Saltbox publish tagged releases?

There are no GitHub releases. The repository's last push is dated 2026-10-01 and it is not archived, so a deployment tracks the default branch rather than a numbered version.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. Project website
  4. README
  5. saltyorg/Saltbox on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/saltyorg-saltbox.svg)](https://hysenlabs.com/projects/saltyorg-saltbox)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/saltyorg-saltbox.svg)](https://hysenlabs.com/projects/saltyorg-saltbox)

Was this useful?