Private Armory is a standalone Sliver Armory implementation for self-hosted Sliver Armories. This allows you to easily distribute and update your private Sliver extensions (BOFs, etc.), aliases (.NET tooling, etc.), and bundles.
See the wiki for the latest installation instructions.
Yes, the Sliver client will install packages from 3rd party Armories before checking the official Sliver Armory. This allows you to override packages by creating a private package with the same command_name.
No. The official Sliver Armory is entirely hosted on public GitHub, i.e. none of the official Armory's underlying infrastructure is managed by the Sliver authors. However, this model is not viable for private/3rd party armories, and thus this implementation allows you to self-host your own Armory.
Yes, out of the box Private Armory supports a simple token authentication scheme, feel free to submit a PR to support other types of authentication.
Private Armory is licensed under GPLv3, some sub-components may have separate licenses.