Binom Installation Guide – How I Set it Up on a Vultr VPS in 2026

I’m setting up Binom V2 right now, so this guide is written from what I actually did, the issues I ran into and the exact steps you need to follow to successfully install Binom self-hosted on a VPS in 2026.

The whole thing is covered here in this Binom installation guide – from creating the server to pointing your domain to the tracker to making technical server adjustments to make it compatible for Binom to finally having a ready to use self hosted affiliate tracker that’s able to handle millions of clicks/visitors a day.

You need a Binom license and a domain, plus a server to put them on. I’m using Vultr for the server, but you can also use other options like Digital Ocean or Hetzner for this.

I’m going to install Binom V2 because that’s their latest version built on modern architecture i.e. ClickHouse + PHP as compared to MySQL in V1. So if pricing is not an issue for you, I’d highly recommend you to go with V2 as it can handle up to 260 million clicks per day as compared to 17m in V1, and redirect speeds and report generation are much more faster.

The installation process for Binom V1 is almost same as V2, but just make sure to use Ubuntu 22.04  LTS  x64 if you want to have an easy way to get V1 installed.

So, let’s get started!

What Binom V2 needs

Binom’s documentation recommends these specs:

Parameter	Recommended
OS	Ubuntu 24.04 or 26.04
RAM	4 GB
CPU	2 cores/threads
Free disk space	At least 50 GB
Virtualization	KVM

Keep those in mind while picking a plan. I went with Vultr, and the plan below clears every line.

Creating the server on Vultr

Go to Compute, then Create Instance. Before you do anything else, click Switch to old version at the top right, just below the nav bar. The new version won’t let you deselect Automatic Backups, and I don’t want them for this example. If you do want backups, you can skip this step.

Under Choose Type, select Cloud Compute – Shared CPU. The plan I picked is enough if you’re just starting out:

• AMD High Performance
• 2 vCPUs
• 4 GB RAM
• 100 GB NVMe
• 5 TB bandwidth
• $24/month ($0.033/hour)

AMD High Performance runs on AMD EPYC server processors. The Intel Xeon option is very similar, but EPYC often edges ahead on database work and value per core, so that’s the one I chose.

For location, pick the server closest to where you’ll run traffic. I’m running traffic to Italy and Spain through Binom, so I selected Paris.

For the image, select 26.04 LTS x64, the latest Ubuntu. This matters more than it looks. The 1-click installer for Binom V1 doesn’t support the newer Ubuntu versions, and it throws this:

1Click can be used with Ubuntu,
but only these versions:
    - 18.04.x
    - 20.04.x
    - 22.04.x

The Binom V2 auto installer does support 26.04, so you’re fine here.

Give the server a hostname and click Deploy Now. It needs a few minutes. Once it shows a green Running status in your list of instances, it’s ready.

Pointing your domain at the server

Click the three dots beside your instance and choose Server Details. You’ll see the server’s IP address along with the login details. For now, all you need is the IP address.

Copy it, go to your domain registrar, and add an A record:

Type: A
Host: @
Value: 203.0.113.10

Use your own server’s IP, of course. The one above is just a placeholder.

If you’d rather use a subdomain, put something like track or whatever you wanna name it in the host field instead of @.

Give it four or five minutes to propagate. A service like Whatsmydns will tell you whether the domain points to your server’s IP yet.

Running the Binom V2 installer

Log in to the server over SSH with the username and password from Server Details. The username is usually root, so you’re connecting to root@your-server-ip. I use Termius for this. The free tier is very generous and covers most of my SSH work.

Once you’re in, run these two commands:

wget https://data.binom.org/binom_v2_install.sh -O /root/binom_v2_install.sh

bash /root/binom_v2_install.sh install

The installer asks for your email address, then gets going. This is what you should see:

root@binom:~# bash /root/binom_v2_install.sh install

UFW is active, adding rules for ports: 80 443 8088

Please enter your email address or type 'exit' to quit:
[email protected]
Installing dependencies...
Installing docker...
Installing trivy...
Installing tracker...
Installing the default settings...

When it finishes, you get your login details:

Done!
Your tracker access:

http://203.0.113.10/index
Login: admin
Password: Xk9mPq2LrVt7NwZb4HdCs8YeAj5FuGgT
Tracker ID: 3f2a9c1e-7b4d-4e8a-9c6f-1d5e0a7b2c93

Save all of that somewhere safe. You’ll need the tracker ID in a minute.

If the installer says it needs 4GB of RAM

This one got me. I ran the installer and it stopped with:

root@binom:~# bash /root/binom_v2_install.sh install
Tracker requires 4GB of RAM on the server to operate. Exiting...

On a 4 GB server, that looks wrong, and it is. On Ubuntu 24.04 and newer, the kernel sets aside about 512 MB of RAM for crash dumps (kdump). A 4 GB server then reports only about 3.4 GB, and Binom’s installer, which expects at least about 3.9 GB of RAM, gives up. It’s a special case and it might not happen to everyone, but if it does, here’s the fix.

Step 1: confirm the cause.

grep -o 'crashkernel=[^ ]*' /proc/cmdline; grep MemTotal /proc/meminfo

If you see a crashkernel=... line and MemTotal is below 3900000, continue to Step 2.

Step 2: remove the crash-dump service.

apt-get purge -y kdump-tools

Step 3: make sure nothing still reserves the memory.

grep -rn crashkernel /etc/default/grub /etc/default/grub.d/ 2>/dev/null

If that prints nothing, go to Step 4. If it prints a line, delete the crashkernel=... setting from the file it names, then carry on.

Step 4: update GRUB and reboot.

update-grub && reboot

Step 5: check the memory again. Log back in over SSH and run:

grep MemTotal /proc/meminfo

MemTotal should now read about 3,9xx,xxx kB.

Step 6: run the installer again.

bash /root/binom_v2_install.sh install [email protected]

Still failing? If MemTotal is only slightly under 3,900,000 kB, lower the installer’s limit and run it again:

sed -i 's/"$ram_total" -lt 3900000/"$ram_total" -lt 3500000/' /root/binom_v2_install.sh

I wouldn’t install on a server with less than about 3.5 GB of usable memory, though.

Turning off kdump only means the server won’t save a crash report if the kernel itself crashes. It has no effect on Binom.

Installing Binom V1 instead

If you’re on Binom V1, the installer is different and the requirements are lighter. Binom’s V1 documentation asks for a VPS or dedicated server (shared hosting won’t work), 1 CPU core, 2 GB of RAM, SSD storage and KVM virtualization. Single-thread speed matters more than the number of cores, HDDs perform badly, and OpenVZ can cause file problems. For the OS, the minimum is Debian 11 or Ubuntu 22.04 (both minimal installs), and Binom recommends Debian 12 or Ubuntu 22.04. Ubuntu 22.10 and 23.10 aren’t supported.

So when you create the server, pick Ubuntu 22.04 or Debian 12 instead of 26.04. After that, log in over SSH and follow these steps.

First, download the installation script:

wget http://data.binom.org/binom_install.sh -O /root/binom_install.sh

Then run it:

bash /root/binom_install.sh install

The installer asks you a few things, starting with a domain for the tracker. You’ll use it to log in and for your campaign links. If the domain already points to your server, the installer sets up SSL for it automatically. If it doesn’t yet, the tracker will only be available over http. No domain at all? You can use your server’s IP address, but then you can’t log in over https.

Next it asks for your email address, then the time zone for the tracker.

When the installation finishes, you’ll see the access data for your tracker. Save it straight away, because it’s generated automatically and can’t be recovered.

Adding the tracker ID to your Binom account

Try to log in at the tracker URL right now and you’ll get this error:

License not found

Tracker id: 3f2a9c1e-7b4d-4e8a-9c6f-1d5e0a7b2c93

Please enter your tracker id into your Binom v2 license at binom.org

So that’s the next step. Go to your Binom dashboard at binom.org, open Licenses, and paste the tracker ID from the install output into the Tracker ID (v2) column.

If you’re setting up Binom V1 instead, you don’t need a tracker ID. Go to Licenses and add your domain there, and that activates the tracker.

Now go to the tracker login URL, which in my case was the server’s IP followed by /index, and log in with the admin details from the installer. This time it works. From here you can add traffic sources, affiliate networks, create campaigns and so on.

Adding your domain and SSL

The last step is the domain. You added the A record earlier, so it should have propagated by now.

Click Domains in the top right corner of the tracker UI, enter your domain and click Add New. If the domain already points to your server, Binom installs an SSL certificate for it straight away. Hit the refresh button and the SSL icon turns green.

From now on, when you create a campaign, you can pick this custom domain for the tracking URL and redirect.

That’s it. If you run into anything I haven’t covered here, tell me in the comments and I’ll fix the guide.