# SetupOrion, a menu-driven installer for a hundred self-hosted tools > oriondesign2015/SetupOrion is a shell installer that puts more than a hundred self-hosted applications on a fresh Debian server through an interactive menu, covering infrastructure, monitoring, databases, backups and more. The upstream project is MIT licensed, and the README is explicit that the server must be empty before you run it. **oriondesign2015/SetupOrion** — Dito como o maior e melhor Setup de soluções Open Source, 100% Gratuito. - Repository: https://github.com/oriondesign2015/SetupOrion - Website: https://setuporion.sh - Stars: 768 · Forks: 259 - Language: Shell - License: MIT - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/oriondesign2015-setuporion ## What the installer actually does SetupOrion is described as the largest and best setup of open source solutions, 100 percent free, and the README explains the intent plainly: it is an auto-installer meant to help the community install the main tools from the automation and marketing market on a server. The key design point is stated early. You do not have to install everything it contains, because you can choose which tools you want from the installer's menu. That is what separates it from a provisioning script that lays down a fixed stack. The project is by OrionDesign, and the README asks that you give credit when you use it. It also states it is completely free and open source, which is worth checking against the fact that the README's own support section asks readers to subscribe to Hostinger through an affiliate link with a coupon code, or to join a paid community membership. The tool is MIT licensed and the code is in the repository, but the funding model is referral and community membership, and a reader should know that before deciding how much to trust a script that installs software. The repository is small. The top level has a LICENSE.txt, the README, an Extras/ directory and two files named Setup and SetupOrion. The primary language is recorded as shell, and the default branch is main. The last push was on 2026-10-15, while the only listed release is v.2.2.6 from February 2024, so the script is being edited more often than it is being tagged. ## Running it and the empty server requirement The README describes the installer as a short piece of code that updates your server, downloads the setup script and runs it, so that anyone can use it. The command to run in the terminal of your server is: ```bash bash <(curl -sSL get.setuporion.sh) ``` That is a pipe from the network straight into a shell, which is the pattern most security guides tell you not to use, and it deserves a second look. The short domain get.setuporion.sh serves whatever the maintainers serve at that moment, and the script runs with root on your server. Reading the script first, or cloning the repository and running the local file, costs a minute and removes the question of what changed since you last looked. The recommendations section of the README is where the operational constraints live. It recommends a VPS from Hostinger, Hetzner, Digital Ocean or AWS, and says other providers are neither recommended nor encouraged. Debian 12 is the recommended operating system with a minimum of 4 GB of RAM and 2 vCPUs, and the README notes you still have to analyse the requirements of each application you intend to install, since the aggregate minimum is not the requirement of any one tool. Then there is the warning that matters most. The server must be empty for the installation to be performed, and running the setup with other tools already present can result in loss of data. The installer is assumed to be doing things like enabling services, writing configuration and opening firewall ports, and none of that is safe to do on a machine where something already lives. The README describes the process as waiting a few moments while the script starts, and then choosing the tools you want from the menu. ## What is in the catalogue, by category The README says the installer covers more than 100 tools, organised by category, with each entry in the tables linking to the official repository so you can read the upstream project before installing it. That linking is a small but meaningful design choice: the catalogue is a pointer to upstream documentation rather than a replacement for it. The infrastructure and monitoring category is the largest. Traefik is there as a reverse proxy and load balancer with automatic SSL through Let's Encrypt. Portainer gives a visual panel for Docker and Docker Swarm. MinIO provides S3-compatible object storage, RustDesk is a self-hosted alternative to TeamViewer, and Code Server is VS Code running in a browser. Monitoring has a stack of it: Grafana for dashboards and metric visualisation, Prometheus for metric collection, storage and alerting, cAdvisor for container resource usage, Uptime Kuma for availability monitoring of sites and services, Checkmate for server and availability monitoring, and Ntfy for push notifications over HTTP to phone and desktop. NetBox covers network infrastructure management, IPAM and DCIM. Backup has three entries with quite different scopes: Duplicati for encrypted backup to cloud and external storage, PgBackWeb for scheduled PostgreSQL backups with a web interface, and ZeroByte for backup automation for self-hosters built on restic. The databases and data category covers MongoDB as a document-oriented NoSQL store, RabbitMQ as a messaging and queue server, Qdrant as a vector database for semantic search and AI, ClickHouse as a columnar database for high-speed analytics, RedisInsight as a graphical interface for exploring and administering Redis, and PgAdmin 4 as a web interface for PostgreSQL administration. The selection tells you the audience: self-hosters running a personal or small-team stack, not operators of large Kubernetes estates. ## What the licence covers and what the repository holds The licence on the repository is MIT, which means the code is free to read, modify and redistribute, and the LICENSE.txt file sits at the top level of the repository for anyone who wants the terms in full. The repository itself is thin, which tells you how the project is distributed. The top level has the README, the LICENSE.txt, an Extras/ directory and two files, Setup and SetupOrion. That is consistent with the install model: the script is meant to be fetched and run rather than built, so there is no package, no test suite and no release artefacts to inspect beyond the source. The Extras/ directory is not described in the README excerpt available here, so it is hard to say what it contains. In a project of this shape it would typically hold additional assets, configuration templates or helper files that the main script sources. The version record is the one thing that raises an eyebrow. There is a single listed release, v.2.2.6 from February 2024, whose tag name uses a v followed by a dot rather than the usual v2.2.6 form, and the last push to the repository is dated 2026-10-15. A script that is edited regularly but rarely tagged means you cannot pin a known version, and you cannot diff your server against a stated release to see what changed. The documentation is also only the README. There is no separate site describing the installation in more depth, no troubleshooting guide and no changelog beyond what the git history shows. For a tool that runs with root on a production-shaped machine, that thinness is the main practical limitation. ## How this compares with the official install methods Every tool in the catalogue has its own documented installation, and most are one command with a compose file or a systemd unit. The difference in approach is that SetupOrion automates the parts around the software, not the software itself. What an installer like this can absorb for you is the boring sequence: base system updates, Docker installation, directory layout, compose file generation, credential files, service enabling, and a reverse proxy entry with a certificate. A self-hoster installing Traefik, Portainer, MinIO and Uptime Kuma by hand is copying four sets of compose files and remembering four sets of paths. The alternative approaches each do one slice of the same job. Ansible or SaltStack give you the automation but expect you to write the playbooks, which is the same work with more machinery. Docker Compose stacks you assemble yourself give you reproducibility for one application but not for a dozen. A bare metal panel such as Coolify or CapRover does the multi-application job in a different way, with a web interface and its own opinions about where your files live, and they are applications rather than scripts. The honest downside is reversibility. A script that installs a hundred things leaves you with a server whose state you did not build, and there is no uninstall. When something breaks eight months later, the person debugging it has to reverse-engineer what the installer did, and the answer is in a script they have to read rather than in a file they wrote. There is also a currency question. The catalogue points at upstream repositories, so the install mechanism follows each project's own releases, but the entries themselves are only as current as the last time somebody updated the list. A tool that has renamed its compose structure since then will install in a way that does not match its current documentation. ## Conclusion Adopt SetupOrion if you stand up throwaway or demonstration servers for self-hosted tools and want the common ones installed in one pass rather than by following a dozen separate READMEs. Skip it for any machine that already holds data, because the README warns that running the installer alongside other tools can cost you that data. Verify first by reading the script before you pipe it into bash, and check that the tool you want is actually in the list, since the catalogue covers popular applications rather than everything. ## FAQ ### What is SetupOrion and what does it install? It is a shell installer that installs more than 100 open source self-hosted applications on a server through an interactive menu, organised by category. The README says you do not have to install everything, because you choose which tools you want from the menu. ### How do I run the SetupOrion installer? The README gives one command to run in the server terminal: bash <(curl -sSL get.setuporion.sh). It updates the server, downloads the setup script and runs it, and then you pick the tools you want from the menu. ### What are the system requirements for SetupOrion? The README recommends Debian 12 with a minimum of 4 GB of RAM and 2 vCPUs, and notes you still need to analyse the requirements of each application you plan to install. Hostinger, Hetzner, Digital Ocean and AWS VPS are recommended, other providers are not encouraged. ### Can I run SetupOrion on a server that already has applications? No. The README states the server must be empty to carry out the installation of the tools, and that running the setup with other tools may result in loss of data. It is designed for a fresh server. ### Which categories of tools does the SetupOrion catalogue cover? The README lists infrastructure and monitoring tools such as Traefik, Portainer, MinIO, Grafana, Prometheus, Uptime Kuma, NetBox and Duplicati, plus a databases and data category with MongoDB, RabbitMQ, Qdrant, ClickHouse, RedisInsight and PgAdmin 4. ## Sources - [License: MIT](https://github.com/oriondesign2015/SetupOrion/blob/main/LICENSE) - [oriondesign2015/SetupOrion on GitHub](https://github.com/oriondesign2015/SetupOrion) - [Project website](https://setuporion.sh) - [README](https://github.com/oriondesign2015/SetupOrion/blob/main/README.md) - [Releases](https://github.com/oriondesign2015/SetupOrion/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/oriondesign2015-setuporion