Install Varqeni on your own host
This is the overview: what the install puts on your host, what it needs from you and what it never does. For the commands, one step at a time, see Install with one command, then connect what you run.
Steps
- The release: one build, in one of two forms. The
varqenifile has everything inside, so the host needs no Python: any 64-bit Intel or AMD Linux with systemd from Ubuntu 20.04, Debian 10 or Red Hat and Rocky Linux 8 on. The package form needs Ubuntu 24.04 with Python 3.12. Either way the release carries a list of checksums, and nothing is installed if one does not match. - What it installs: separate services from the same build: the watcher, which only reads, the console on port 8088, and the responder, which stays off until you set it up. The watcher and the part that acts run as different system users with no login.
- How it starts: watching nothing. You connect each part you run, such as a PostgreSQL server or a change data capture pipeline, and each one is checked read-only before Varqeni watches it.
- What it never does: place a password for you, raise the autonomy level, switch on anything that acts or page anyone. Fixes stay off until you give the part that acts its own credentials and an approver rota.
- Removing it:
sudo varqeni uninstallstops and removes it and keeps your settings and evidence; add--purgeto remove those too.
What you should see: The self test and varqeni status show every read as passed or failed with the reason, so you see what Varqeni can and cannot see before it watches anything.
What it can and cannot do
Can
- Install from a checked release on a host you control, watch only what you connect, and show what it can and cannot see.
Cannot
- Promise ARM hardware support yet (the ARM build is tested under emulation), install on managed cloud services for you, place credentials itself, or turn on fixes during install.
What you provide
For each part you connect, a read-only way in: a database login with monitoring rights, a read-only Kubernetes account, a read-only path to Kafka Connect, your Prometheus address. Fortis can set these up with you. Passwords go only into a file that the root user and the watcher can read. Fixes on Kubernetes go straight through the Kubernetes API, so the host needs no kubectl; in the lab that path passed 40 of 40 estate fix trials, 40 of 40 service fix trials and 20 of 20 closed-loop autopilot trials.
What is not there yet
ARM (aarch64) hosts have their own build, tested under emulation but not yet on ARM hardware.
Related articles
- Install with one command, then connect what you runThe commands, one step at a time: install, see what you can connect, connect one part, check it and add more.
- How Varqeni is set up on your systemsFortis installs the agent during early access. It reads your pipeline through identities that can only read.
- What Varqeni reads, and what it does notVarqeni reads the state of your pipeline, never the rows of your data.
- Autonomy levels: observe, recommend, approve, act within policyHow much Varqeni may do on its own, from only watching to fixing known faults under a written policy.
Still stuck? Contact support or email info@fortisdatagroup.com.