Varqeni Help

Install with one command, then connect what you run

Updated 11 November 2026

For what the install puts on your host and what it never does, see Install Varqeni on your own host. Every command below runs as root on that host.

AvailabilityBuilt, and not switched on for early access consoles yet. This page describes how it will work.

Steps

  • Install: run sudo ./varqeni-bootstrap.sh --bundle <the release>, where the release is a folder, a .tar.gz file or an HTTPS address. It checks the host, refuses a release whose checksums do not match, then installs. varqeni --version shows which build you have.
  • See what you can connect: sudo varqeni status lists postgres, kafka-connect, kubernetes, prometheus, airflow and services, each connected or not.
  • Connect one: sudo varqeni connect postgres asks for the host, database and a read-only login. The password is asked without showing it.
  • Checks first: Varqeni tests the connection and runs that part's self test. If anything fails it says why and changes nothing. When everything passes it switches the part on and starts watching it.
  • Add more later: connect the next part the same way. A change data capture pipeline needs kubernetes connected first.
  • Remove it: sudo varqeni uninstall keeps your settings and evidence; sudo varqeni uninstall --purge removes them too.

What you should see: After the first connect, the console answers at port 8088 and shows what you connected; areas with nothing connected list the command that would switch them on.

What it can and cannot do

Can

  • Install one file with one command on most 64-bit Linux hosts, then watch only what you connect, each part checked read-only first.

Cannot

  • Promise ARM hardware support yet (the ARM build is tested under emulation), connect a part whose checks fail, place logins for you, or start anything that acts.

If it does not work

  • If a connect fails, the line marked FAIL names what could not be reached or read. Fix that and run the same command again: nothing was changed by the failed attempt.
  • To script it, pass values with --set key=value and the password in VARQENI_PASSWORD, and add --yes so nothing is asked.
  • If the bootstrap refuses the release, download it again: a checksum that does not match means the files are not the ones Fortis built.

Still stuck? Contact support or email info@fortisdatagroup.com.