Install VrilOps — and what you’re actually getting

VrilOps is not another CI dashboard in the cloud. It is a local desktop desk for deployments: your projects, your servers, your builds, and your transfers — sealed behind a PIN vault on the machine you control.

Think of it as the flight checklist for shipping to a VPS. Configure once. Re-run forever.

This guide covers Linux install via apt (the same signed repository as Vril Hum and VrilXor), Windows install, then a clear tour of the workflow so you know what you opened.

Install on Linux (apt)

Package name: vrilops

Repository: apt.vrilsoft.com (signed, amd64)

One-time setup + install

curl -fsSL https://apt.vrilsoft.com/vrilsoft-apt.gpg | sudo gpg --dearmor -o /usr/share/keyrings/vrilsoft-apt.gpg

echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/vrilsoft-apt.gpg] https://apt.vrilsoft.com stable main' \

| sudo tee /etc/apt/sources.list.d/vrilsoft.list

sudo apt update

sudo apt install -y vrilops

If you already use apt for Vril Hum or VrilXor, you only need the last two lines — the repo is the same.

Upgrade later

sudo apt update && sudo apt install --only-upgrade vrilops

Prefer a direct download? Grab the .deb from the linked publication (SHA-256 is shown so you can verify the file):

• Publication: https://vrilsoft.com/publications/vrilops-download
• Store: https://vrilsoft.com/products/vrilops-deployment-manager

sudo apt install ./vrilops_*.deb

Install on Windows

Download the Windows installer from this product page (or the publication Downloads section when attached), run it, then launch VrilOps from the Start menu.

First launch — PIN vault

Create a PIN on first launch (minimum 4 characters). That PIN unlocks the encrypted project vault for the session. SSH passwords and project metadata stay on this machine — they are not baked into the installer and are not uploaded to Vrilsoft.

Change PIN anytime from Help → Change PIN.

The workflow

1. Add Project — local folder, remote path, server IP/port, project type, SCP or RSYNC, SSH user/password, optional custom build options, optional systemd service path + sleep.
2. Build — clears contents of the sibling ../deploy folder (folder itself always remains), then runs the type-specific build.
3. Deploy — transfers deploy/ to the remote path; if a service is set, stop → sleep → transfer → sleep → start.
4. Build & Deploy — build first; deploy only if build succeeds.
5. Service — visible when a service path exists; checks active state and toggles start/stop.

Watch everything in the read-only SSH LOG (copy supported). Passwords are redacted.

Transfer methods

• SCP — classic secure copy. Optional flags are filtered so RSYNC-only options (like -avz --delete) cannot slip in and break the command.
• RSYNC — default -avz --delete when options are left blank, so remote contents stay in sync with your publish folder.

How the pieces fit

VrilOps (desktop)

├── PIN vault (projects + SSH secrets, local)

├── Project list (Build / Deploy / Build & Deploy / Edit / Service)

├── Build → ../deploy (contents only)

├── Deploy → SCP or RSYNC over SSH (sshpass)

└── Optional systemd stop/start around transfer

Quick checklist after install

1. Install or upgrade vrilops via apt, or run the Windows installer.
2. Set your vault PIN.
3. Add a project (browse local folder, fill remote + SSH).
4. Optional: Service File Path for systemd-aware deploys.
5. Build & Deploy — confirm on the server.

Need the long-form overview and Downloads list? See the publication: https://vrilsoft.com/publications/vrilops-download