Self-hosted with the Scalio Installer¶
The Scalio Installer runs the Scalio apps on a Linux server of your own: in your data centre, on Hyper-V, VMware or Proxmox, or at a cloud provider. One server can run several apps. The Installer installs, updates and backs them up; everything is done in the browser.
Applies to: self-hosted
With SaaS, Scalio runs the app for you and you can skip this page.
How it works¶
- The Installer is a container on your server. Next to it runs Caddy, a web server that gives every app its address with a certificate.
- Every app runs in its own containers with its own database. The apps have no access to Docker and no port on the server; only Caddy answers on ports 80 and 443.
- The Installer loads the apps from a list that Scalio signs. It checks the signature and loads every image by its checksum, so nobody can slip in a changed image.
- Scalio has no access to your server. There is no remote access, no Scalio account and no SSH key from Scalio. You stay responsible for the server: operating system, firewall, monitoring and the backup target.
What you need¶
| One app | Each further app | |
|---|---|---|
| Processors (vCPU) | 2 | 4 in total from three apps |
| Memory (RAM) | 4 GB | +1 to 2 GB |
| Disk | 40 GB | +10 GB, plus your data |
- Operating system: Ubuntu Server 24.04 or 26.04 LTS, or Debian 12 or 13, 64-bit (x86_64 or arm64). With our ISO or VM image you get Ubuntu 26.04 LTS ready to go.
- Network: a fixed address. Ports 80 and 443 reachable for the users (and from the internet if you use Let's Encrypt without DNS). Outbound HTTPS to the internet for the images, updates and Microsoft.
- Addresses (DNS): one name per app, for example
nexus.company.com, pointing to the server. Optionally one more name for the Installer itself, for examplesetup.company.com. - E-mail (optional): an SMTP mailbox the apps send invitations and alerts from.
What the server costs depends on your platform. A VM of this size is a small server at every cloud provider; on your own Hyper-V, VMware or Proxmox host it only needs the resources above.
Install¶
Choose one of three ways. All three end at the same Installer.
On a fresh Ubuntu or Debian server, as a user with sudo rights:
The script installs Docker from the official Docker repository, creates /opt/scalio, opens ports 80 and 443
if the firewall ufw is active, switches on the automatic security updates and starts the Installer. It changes
nothing else on the server.
Download the Scalio ISO and check it (sha256sum -c SHA256SUMS). Boot a new VM or server from it. The
installation asks only for language and keyboard, network, your administrator account and SSH. There is no
default account and no default password. The ISO uses the whole first disk, switches on the firewall
(22, 80, 443) and the automatic security updates.
Download the image for your platform and check it with its .sha256 file:
- Hyper-V:
.vhdx.zip. Unzip it and create a generation 2 VM with this disk, 2 vCPU and 4 GB RAM. If Secure Boot is on, choose the template Microsoft UEFI Certificate Authority. - VMware, VirtualBox, Proxmox:
.ova. Import it; it brings 2 vCPU, 4 GB RAM and a 40 GB disk. - Proxmox, KVM:
.qcow2. Import it as the disk of a new VM.
At the first start the console asks for keyboard, user name and password (at least 12 characters) and optionally your SSH keys from GitHub. With cloud-init (Proxmox, VMware vApp, Azure) the account from cloud-init is used and the console does not ask.
When the server is ready, the console and every SSH login show the address of the Installer and a
one-time code. On the ISO and VM image, sudo scalio-code shows a new code at any time (valid once, for 30
minutes). After the script, the code is in its output.
The setup wizard¶
Open the address in the browser (https://<IP of the server>). The browser warns about the certificate the first
time, because the IP address has a certificate from the Installer's own certificate authority. Sign in with the
one-time code. The wizard then asks:
- Language of the Installer.
- Apps that should run on this server.
- Addresses: the name of each app and its certificate (see Certificates).
- License: sign in to Scalio Compass with a device code and pick a license, enter a license key, or continue without a license (free edition or trial, depending on the app).
- E-mail: the sender for all apps (optional, can be set later).
- Install: the Installer downloads the signed images and starts the apps.
- Recovery sheet: download it and keep it safe. It holds the keys of every app; without it, a backup cannot be restored on a new server. The wizard only finishes once you have saved it.
The overview then shows the setup code of each app (icon Setup code in the tab Apps). With it you create the first administrator in the app. After that, the app no longer accepts the code.
Certificates¶
Each app, and the Installer itself, can use one of four kinds of certificate:
| Kind | When |
|---|---|
| Let's Encrypt | The name is reachable from the internet on port 80 or 443. Free, renewed automatically. |
| Let's Encrypt over DNS | Internal names. The Installer proves the name through your DNS provider and needs an API token with rights for the DNS zone. Supported: Cloudflare, Amazon Route 53, Azure DNS, deSEC, DigitalOcean, Gandi, GoDaddy, Hetzner, Infomaniak, IONOS, Namecheap, netcup, OVHcloud, Porkbun and more. |
| Internal certificate authority | No internet, no DNS provider. Every device must trust the root certificate (download in the tab Apps). |
| Own certificate | A certificate of your company (PEM file with chain and the private key without password). |
You change the certificate of an app with the shield icon in the tab Apps.
Everyday work¶
The Installer has three tabs:
- Overview: available updates, the apps at a glance and the state of the server (disk, memory, load, containers).
- Apps: one row per app. The icons start, stop and restart the app and change its certificate, license, setup code and pre-releases; the bin uninstalls it. Install more apps adds apps at any time.
- Settings: backup, server updates, support, address of the Installer, accounts and alerts.
Updates of the apps¶
The Installer checks for new versions and shows them in the overview. Update to … first saves the database of the app, then switches to the new version; the database never goes back to an older version. If the app is busy (for example a long job), the Installer waits and asks before it updates anyway. With Show pre-releases per app you also get release candidates (see Pre-releases).
The Installer itself is updated with sudo scalio-update on the server (ISO and VM image) or by running the
script again. The apps and their data stay as they are.
Backup¶
Under Settings → Backup you choose a target: only this server, S3 (Amazon, Wasabi, MinIO, Infomaniak …), Azure Blob Storage, SFTP or a Windows share (SMB). Every night the Installer saves the database and files of every app, encrypted with your backup password. Without the password nobody can open a backup, Scalio included: keep it with the recovery sheet. On the first night of every month the Installer restores one backup as a test and shows the result; Test restore now starts it at once.
Server updates¶
The server installs security updates every night by itself. If an update needs a restart, the server restarts only in the window you set under Settings → Server updates (day and hour; or never, then you restart yourself). The apps start again by themselves.
Alerts¶
Under Settings → Alerts by e-mail you get one mail when a container stops or is unhealthy, the disk is over 90 % full or a certificate runs out in less than 14 days, and one when it is fine again.
Access to the Installer¶
- Address of the Installer: its own name (for example
setup.company.com) with one of the certificates above. The IP address keeps working. - Accounts for the Installer: user name, password and an authenticator app (for example Microsoft Authenticator). The one-time code from the server keeps working, so a lost phone never locks you out.
Support¶
Scalio has no access to your server. For help, download the support package under Settings → Support and send it with your request. It holds versions, state and the latest log lines, without passwords, keys or licenses.
Taking over an older Nexus installation¶
If Scalio Nexus already runs on the server with its own Docker Compose and updater, the Installer finds it and offers Take over Nexus. It saves the database, stops the old containers (they stay for a way back), installs Nexus with the same data, secrets and license and restores the database. If anything fails, the old containers start again as before. Nexus is not reachable for a few minutes. If the address changes, also change the redirect URI of the Nexus app registration in Microsoft Entra.
Files on the server¶
| Path | Content |
|---|---|
/opt/scalio/apps/<app>/ |
Compose file and .env of each app (the .env holds secrets, readable by root only) |
/opt/scalio/backups/ |
Local backups and the database saved before each update |
/opt/scalio/setup/ |
Settings of the Installer |
Never change these files by hand; the Installer writes them again. To remove everything, uninstall each app with
Delete the data too and then remove /opt/scalio.