Binom Pricing in 2026: Plans, Operating Costs and What to Compare

The short answer: Binom’s current public price page makes it unusually simple to compare the licence: Binom v2 is listed at $149 per month or $104 per month on the yearly selection, while Binom Cloud is listed at $299. That is only the invoice for the tracker. The decision that changes the real cost is whether your team will own a production server, its capacity, backups and incidents—or pay for Binom’s managed Cloud option instead.

This is not a replacement for Binom’s own price page. It is a buyer’s guide to the costs and questions around that card. Pricing, trial terms, capacity and plans are volatile, so this snapshot was checked on 10 July 2026 and links to the vendor’s primary documentation throughout.

Binom pricing at a glance

The official page also lists an “additional license” price for each billing selection. Its meaning can depend on the account arrangement, so confirm it with Binom before including it in a team budget. Check the live Binom price page before paying.

Read the capacity language carefully

Binom says its fixed tracker price is not tied to traffic volume and separately displays “traffic up to 260m/day” for v2. Those are vendor plan statements, not a capacity test for your exact stack. Daily clicks alone cannot describe a workload: traffic spikes, reporting depth, data-retention choices, storage, source integrations, and the way campaigns are built all matter.

Do not buy on a throughput headline. Ask Binom to help size the deployment for your peak clicks per minute, expected geography, reporting workload, and retention period; then test the routes and reports that actually carry your spend. Its server-selection guide itself treats server selection as traffic- and geography-dependent. See Binom’s server-sizing guidance.

What the self-hosted price really buys

Binom v2 is a tracker licence, not an all-in infrastructure bill. The public price page says feature access, user count, domain count, and storage time do not change with the displayed pricing rate. For the right team, that predictability is a real advantage: adding another buyer or domain does not automatically move the tracker onto a different public tier. Binom’s pricing and product pages describe the fixed model.

But self-hosting moves operating responsibility into your company. Binom’s v2 installation guide calls for a clean KVM VPS or dedicated server running Ubuntu 22.04 or 24.04, with at least 4 GB RAM, two CPU cores/threads, and 50 GB free disk as minimums. It explicitly says that the optimal configuration depends on desired performance and daily traffic. Read the current installation requirements.

Your monthly cost model is therefore:

Binom v2 licence
+ server sized for peak traffic and retained data
+ domains and DNS operations
+ independent backups and recovery testing
+ monitoring / alerting
+ the time of the person who owns updates and incidents
= self-hosted cost of operation

Not every line needs to be a separate vendor invoice. A team with an existing, disciplined operations function may already have monitoring, backups, and on-call coverage. A solo buyer may have to buy those capabilities or accept more operational risk. The point is to price the work honestly rather than calling a $104 or $149 licence the total cost.

Storage and backups are operating costs, not footnotes

The price page advertises lifetime data retention. That is a licence statement, not a reason to stop capacity planning. Binom’s documentation notes that retained clicks consume server disk and advises planning storage around traffic volume. Its v2 import/export documentation also says auto-backup files are kept on the same server as the tracker. See the v2 import/export and backup documentation.

For a production setup, ask a narrower question: where is the independently recoverable copy, who can restore it, and when was that restore last tested? A backup on the same machine may be useful operationally, but it is not the same thing as a tested recovery plan for a server failure or account mistake.

Who should choose Binom v2?

The self-hosted route is a strong fit when all of the following are true:

• You want the control of running the tracker on infrastructure your team administers.
• You can assign a named person or provider to server sizing, patching, monitoring, backups, access control, and recovery.
• The unlimited-user and unlimited-domain model fits the way your operation is organised.
• You are prepared to validate capacity with a representative traffic slice before moving critical spend.

It is a poor fit when nobody really owns the server after the first campaign goes live. “We can install it” is not the same as “we can run it safely at peak traffic.”

When Binom Cloud changes the equation

Binom describes Cloud as the option for teams that do not want to purchase and configure a server; its FAQ says Cloud plans include server, monitoring, and optimization from Binom. The public Cloud card is listed at $299 and includes auto installation, a seven-day trial, unlimited users, unlimited domains, lifetime data retention, and a published traffic figure of up to 2m/day. Review Binom’s current Cloud terms on the price page.

That does not make Cloud universally better. It changes what you are buying: less infrastructure ownership, in return for a higher service price and a different capacity envelope shown on the public card. It is generally the sensible first evaluation for a team that wants to focus its scarce time on campaign operations and does not already operate Linux servers confidently.

Before choosing Cloud, get written answers for the workload that matters to you:

1. What does the listed traffic figure mean for your peak—not average—click rate and report usage?
2. What support and response path applies to your account and time zone?
3. What is the backup, restoration, and data-export process for your workspace?
4. Which operational tasks are handled by Binom and which remain with your team?
5. How do you move between Cloud and self-hosted if your requirements change?

These are procurement questions, not accusations. A Cloud plan is easiest to evaluate when ownership boundaries are explicit before traffic is moved.

Feature fit: test the data path, not only the dashboard

Binom documents campaign paths, direct routes, weighted and smart traffic distribution, fixed visitor treatment, source tokens, costs, and server-to-server postback parameters. Its campaign documentation lists the available routing and postback fields.

That is enough capability to make the meaningful evaluation specific. Put one representative campaign through a controlled test and verify this chain:

traffic source → tracker URL and source parameters → route → landing or offer
→ click identifier → conversion callback → payout and cost report → decision

For the test, require evidence that:

• your required source parameters land in the intended reporting fields;
• a returned conversion can be matched to the expected click;
• the correct payout, currency, and conversion meaning appear in reporting;
• cost updates land on the correct campaign and date;
• the three routing rules that drive the most spend behave as expected;
• an exported report contains the fields your finance or BI process actually needs.

This is much more valuable than asking whether the tracker supports “postbacks” in the abstract. A feature only exists for your operation once its inputs, status meanings, and outputs survive a real test.

Fair alternatives, by operating model

There is no useful “best tracker” list without a workload. These are reasonable places to evaluate when the operating model—not a generic feature checkbox—is the deciding factor.

Run the same proof campaign through every serious finalist. Price pages change; a representative campaign exposes the integration, reporting, and operating work that will still exist after a sales call.

A migration and due-diligence checklist

Do not make a hard cutover the first test of a tracker. Migration affects click paths, parameters, callbacks, reports, and the people who depend on them. Use a parallel verification window long enough to investigate mismatches before budgets or routing rules move.

Before you sign or start a trial

1. Document the present state. Export a list of traffic sources, domains, campaigns, landing pages, offers, routing rules, tokens, postback URLs, conversion meanings, report columns, API consumers, and user access.
2. Write a volume profile. Record peak clicks per minute, not just daily average; traffic geographies; retained-data horizon; and the heaviest report your team runs.
3. Put the commercial terms in writing. Confirm current price, billing cadence, trial length, additional licences, plan limits, renewal terms, support route, and any migration assistance.
4. Name the operating owner. For self-hosted, assign server, backup, monitoring, update, incident, and access responsibilities before installation—not after an outage.
5. Define success. For example: 99.9% of test clicks have expected parameters; every test callback matches once; costs and payouts agree within an agreed tolerance; and required reports export cleanly.

During the proof and migration

1. Build one low-risk but representative flow rather than your simplest demo.
2. Keep the old tracker running while traffic is split or mirrored in a controlled way that your source agreements permit.
3. Compare clicks, matched conversions, cost, payout, timezone, attribution fields, and report totals at agreed intervals.
4. Test reporting permissions and API keys with the least-privileged roles your real team will use.
5. Test recovery: restore a non-production copy or otherwise validate that the documented backup process works.
6. Record every mapping decision so the next operator does not have to rediscover a critical token or status rule.

Before full cutover

• Freeze a rollback path: old domains, tracker URLs, postback endpoints, credentials, and the owner who can reverse the change.
• Reconfirm budgets, caps, conversion statuses, and reporting timezone.
• Monitor the first live window closely; do not make unrelated routing or campaign changes at the same time.
• Keep the old system’s data accessible long enough for reconciliation and payout disputes.

Binom’s own v2 import/export documentation is useful for moving Binom v2 data, and notes that a one-to-one tracker transfer should go through support. Treat that as one part of the project; it does not validate whether external sources, callbacks, finance exports, or downstream consumers survived the move. Read the v2 import/export guidance.

Where DarkCore fits—and where it does not

DarkCore should not be treated as a generic reason to leave Binom. If your primary requirement is a particular self-hosted Binom deployment, evaluate that deployment on its own merits.

DarkCore is relevant when the hard problem is broader than click routing: the same team needs traffic routing, PWA and Direct Link activity, custom conversion statuses, operational analytics, and finance to refer to the same campaign workflow. Its public product pages describe Streams with priority rules and weighted splits; a PWA Tracker that connects PWA installs, opens, Direct Link alternatives, and postback events to one analytics and CRM layer; Analytics segmented by source, stream, offer, geo, device, and custom metrics; and Finance built around the same campaign data.

That is a good conversation to have when you are manually reconciling results across separate systems. It is not evidence that DarkCore already covers every routing detail, server-control preference, or existing integration in a mature Binom installation. The honest evaluation is the same one recommended above: take one live flow, list its must-have rules and fields, prove the status and reporting path, and keep the incumbent system available until the numbers match.

If that is your situation, map the workflow with DarkCore before committing to a replacement project.

FAQ

How much is Binom per month in 2026?

On 10 July 2026, Binom’s public pricing page listed Binom v2 at $149 per month and $104 per month on the yearly selection. It listed Binom Cloud at $299. Recheck the official page before purchase because prices and terms can change. Binom pricing

Does Binom Cloud include hosting?

Binom says its Cloud plans include the server, monitoring, and optimization. The Cloud card also lists auto installation. Confirm the specific operational boundaries, backup approach, and support terms for your account before migrating production traffic. Binom pricing FAQ

Does self-hosted Binom require a server?

Yes. Binom’s v2 installation guide calls for a clean KVM VPS or dedicated server and publishes minimum OS, RAM, CPU, and disk requirements. Those are minimums; size the server for your actual workload. Binom v2 installation requirements

Is Binom’s price really unlimited?

The vendor says its fixed price does not vary by traffic volume, storage time, users, or domains, while the v2 price card also shows a traffic figure. That is a pricing model and a published plan statement—not proof that every workload can run on every server configuration. Test your expected peak traffic and reporting use. Binom pricing

What should I compare besides the licence price?

Compare the required server, retention and storage plan, backups, monitoring, support, domain operations, peak traffic profile, postback mappings, report exports, integrations, and the time someone will spend operating the platform. Then compare those costs against the managed Cloud option, not only against another tracker’s headline subscription.

Sources and update policy

This article deliberately uses first-party product, pricing, and documentation pages for volatile claims rather than affiliate review sites. It was checked on 10 July 2026. Before acting on a price, trial, plan limit, capacity figure, feature, or migration process, verify it on the vendor source below and update this article when a material term changes.

• Binom pricing
• Binom product overview
• Binom v2 installation requirements
• Binom server-sizing guidance
• Binom campaign and postback documentation
• Binom v2 import/export and backup guidance
• Keitaro pricing
• Keitaro installation FAQ
• Voluum pricing

Continue the decision

• Compare the two self-hosted tracker operating models in Binom vs Keitaro.
• If the next question is managed cloud versus server ownership, read Binom vs Voluum.