Binom vs Keitaro: Which Self-Hosted Tracker Fits Your Operation?

The short answer: choose Binom if a fixed advertised tracker entitlement—plus the option of a vendor-managed cloud deployment—is the main appeal. Choose Keitaro if your team is happy to run a VPS and wants its documented filters, flows, conversion types, and edition model. Neither choice is automatically better: both are serious tracking systems for routing traffic, recording conversions, and analyzing campaigns.

The practical decision is not “which logo wins?” It is who will operate the infrastructure, which routing rules you must reproduce, how your postbacks and costs arrive, and whether the tracker is the whole workflow or just one part of it.

Pricing snapshot checked 10 July 2026. Prices, plan limits, trials, and integrations change. Treat the vendor links in this article as the source of truth before paying or migrating.

Binom vs Keitaro at a glance

The two rows most likely to change your decision are who owns the server and whether the plan structure matches your domains, users, and traffic model. Routing is important, but it is not a useful place for a fake winner: both products give experienced buyers substantial control.

Start with the operating model, not the feature list

Both trackers can sit between a traffic source and an offer, collect click-level data, apply routing logic, and receive conversion callbacks. That makes feature-by-feature checklists deceptively similar.

The real difference begins with the operating model.

Binom: fixed entitlement, with self-hosted or managed deployment

Binom’s current pricing page presents one v2 tracker tier with the same feature set regardless of traffic, domain, or user volume. It lists unlimited users, unlimited domains, lifetime data retention, and a self-hosted price of $149 month-to-month or $104/month on yearly billing. The same page lists Binom Cloud at $299 and describes it as the option for organisations that want server management from Binom. Check the live price page before buying.

That gives a team two distinct evaluation paths:

• Run the tracker yourself if you want to select and operate the infrastructure.
• Evaluate Binom Cloud if you want the vendor to handle the server, monitoring, and optimisation layer it describes.

“Up to 260m/day” is a vendor capacity statement, not an independent benchmark or a promise that every deployment will handle the same workload. Redirect behaviour at real volume depends on campaign design, storage, server configuration, network conditions, and the rest of the stack. Treat it as a conversation starter for capacity planning—not as evidence that one tracker is universally faster.

Keitaro: a self-hosted tracker with edition-based limits

Keitaro’s own documentation describes installing the tracker on a server you purchase. Its listed minimum requirements include a clean compatible server, KVM virtualization, 20 GB SSD, and at least 4 GB RAM; processor requirements depend on expected clicks per day. Read the requirements in Keitaro’s FAQ.

Its public individual annual pricing view currently shows Starter, Advanced, and Expert at EUR40, EUR72, and EUR104 per month respectively. Keitaro’s edition documentation says the first three levels include 1 / 100 / 500 domains and 1 / 1 / 5 users. It also documents unlimited campaigns, flows, filters, and clicks, plus plan-dependent capabilities such as API access and integrations. Review the current edition table.

For a team that already owns server operations, this model can be a deliberate advantage: you decide how to provision, monitor, back up, and update the environment. For a team without that capacity, the same control becomes a recurring task rather than a one-time setup.

Pricing: calculate the full operating cost

Comparing the licence figure alone is tempting—and incomplete. A self-hosted tracker also needs infrastructure and operating ownership. The exact cost varies too much to put a universal dollar number on it, but the calculation is simple:

self-hosted tracker cost = licence + VPS + backups/monitoring + domains + team operating time

managed tracker cost = subscription + domains + services outside the tracker

For Binom, the key pricing question is whether the flat tracker entitlement or the managed Cloud option better matches your operating model. For Keitaro, begin with the required edition, then add the VPS and the people responsible for maintaining it.

Do not turn this into an ideology. Self-hosting is a good fit when the team already has reliable operational ownership and needs the control. Managed infrastructure is a good fit when the cost of that ownership would distract buyers from campaign work. The honest answer changes from team to team.

Routing and testing: both are capable, so test your actual rules

Binom documents three traffic-distribution approaches: weighted Normal Rotation, Smart Rotation based on uniqueness and conversions, and a mode that fixes a visitor to a path, landing, or offer. It also documents sending traffic through a landing page, directly to an offer, or into another campaign. See Binom’s campaign documentation.

Keitaro documents distribution based on conditions including GEO, mobile operator, browser, device, flow state, and schedule. Its edition documentation also lists split-testing and rotation. See Keitaro’s edition and feature documentation.

That means the useful trial question is not “does it have routing?” It is:

1. Can it recreate your three highest-spend rules exactly?
2. Can it preserve the visitor treatment you need when a person returns?
3. Can it send the right parameters to every lander, offer, and downstream endpoint?
4. Can the team understand why a specific visit went down a specific path?
5. Can you change a rule safely without breaking a live source?

Write these answers down before a migration. A clean-looking dashboard cannot compensate for a routing model that fails on the one GEO, device, or schedule edge case that carries your margin.

Postbacks, costs, and conversion status: validate the data path

A tracker can only report what it receives. Before choosing either platform, trace one conversion end to end:

ad click → tracker click ID / token → landing or direct route → offer → postback → tracker report → cost and payout view

Binom documents an S2S postback with click, campaign, traffic-source, device, GEO, cost, payout, and token values. Its API documentation also includes updating traffic costs and managing offers and landers. Review Binom’s postback and API references. API details.

Keitaro documents custom conversion types, postback-driven conversions, cost syncing from advertising platforms, and both Click and Admin APIs. The product page says its conversion types can reflect business outcomes such as purchases, leads, sign-ups, subscriptions, and repeat orders. See Keitaro’s feature overview.

Neither paragraph replaces a real test. Use a staging campaign or small live slice to verify all of the following:

• a source parameter reaches the intended tracker field;
• a click ID returns in the affiliate-network callback;
• a test postback appears once, with the right status and payout;
• imported or passed cost lands on the correct campaign and date;
• reports agree with the original source before you change budget decisions.

If one link in that chain is unclear, do not migrate production traffic yet. Find the missing mapping while the blast radius is small.

Which one should you evaluate first?

Start with Binom if this sounds like your team

• You want the predictability of Binom’s advertised flat entitlement for users, domains, and tracker traffic terms.
• You want a choice between running the tracker yourself and assessing a vendor-managed cloud option.
• Your routing and postback workflow fits the documented paths, rotations, tokens, and API operations.
• You will still verify actual capacity against your own campaign mix rather than relying on a headline throughput figure.

Start with Keitaro if this sounds like your team

• You are comfortable buying, configuring, monitoring, backing up, and updating a VPS.
• Your team needs Keitaro’s documented filter-driven flows, schedules, conversion types, reports, or integration model.
• The edition’s domain and user limits fit the way your team is organised now—not only the first month of a new campaign.
• You have a tested plan for server capacity as traffic grows.

Pause the decision if this is the real problem

If the hard part is not routing a click but reconciling PWA events, direct links, campaign operations, finance, and team responsibility across several tools, switching from one tracker to another may only move the same operational gap. In that situation, first document the workflow and decide whether a tracker-only stack is still the right shape for the team.

Where DarkCore fits—and where it does not

DarkCore is not presented here as a universal Binom or Keitaro replacement. A team whose priority is a particular self-hosted routing configuration should test that configuration directly in the tracker it is considering.

DarkCore becomes relevant when the workflow needs more than standalone tracker reporting. Its public product pages describe Streams for routing and splits, a PWA Tracker that keeps PWA and Direct Link activity in the same lifecycle, Finance, and Auto-rules. That is worth evaluating when the same people are trying to connect delivery, campaign decisions, and operational reporting across separate tools.

The right way to evaluate it is deliberately narrow:

1. Take one live campaign flow—not the easiest demo case.
2. List its routing conditions, click parameters, postback statuses, reporting fields, and failure conditions.
3. Confirm which of those requirements must remain in Binom or Keitaro and which can be handled in a connected DarkCore workflow.
4. Run a parallel verification window before changing production budget or retiring an existing tracker.

That approach is slower than a “switch now” promise, but it is how a team avoids losing attribution while trying to improve the rest of its operating system.

Common mistakes when comparing trackers

Treating the price card as total cost. A self-hosted licence does not include the VPS, backup discipline, monitoring, or the time someone spends owning incidents.

Comparing capacity slogans instead of your workload. Vendor capacity claims do not tell you how a specific mix of redirects, reports, data retention, and integrations will behave. Test your own path.

Ignoring plan limits until after setup. Domains, users, APIs, and integrations can be edition-specific. Choose the plan for the team you expect to run, not the smallest plan that can create one test campaign.

Migrating without a postback checklist. A beautiful dashboard is irrelevant if a click ID, status, payout, or source cost stops mapping during the cutover.

Assuming a tracker solves every operating problem. Tracker reporting can be excellent while finance, PWA lifecycle data, and team operations still live in disconnected systems. Identify that boundary before buying another tracker.

FAQ

Is Binom self-hosted?

Yes. Binom says it was originally self-hosted and now also offers Binom Cloud, which it describes as including the server, monitoring, and optimization. See Binom’s current pricing page.

Does Keitaro require a VPS?

Keitaro’s FAQ says automatic installation requires purchasing a VPS, and it publishes server requirements for installation. Read the current requirements.

Is “unlimited clicks” the same as guaranteed throughput?

No. A licence entitlement and real-world throughput are different things. Your server, tracking setup, report queries, retention, traffic mix, and downstream endpoints all affect what a deployment can handle. Use a controlled test for capacity decisions.

Which tracker is cheaper?

There is no honest universal answer. Compare the live plan price, required domains/users, VPS and operating cost for self-hosting, and whether a managed option removes work your team would otherwise perform. Recheck both vendors’ price pages immediately before purchase.

What should we test before moving live traffic?

Recreate representative routing rules, confirm source parameters and click IDs, send a test postback, verify cost/payout reporting, and run both systems in parallel long enough to investigate any mismatch. Do not use a hard cutover as the first functional test.

Sources and update policy

This comparison uses first-party vendor sources rather than affiliate review sites or competitor listicles. Check them again whenever a price, plan, integration, or technical limit appears in the article:

• Binom pricing
• Binom product page
• Binom campaign documentation
• Binom API documentation
• Keitaro pricing
• Keitaro edition plans
• Keitaro FAQ and installation requirements
• Keitaro features

Continue the decision

• Need the commercial context behind Binom’s licence? Read the source-linked Binom pricing guide.
• Deciding whether to own the tracker environment at all? Compare Binom and Voluum on self-hosted control versus managed cloud.

If your operation needs PWA delivery, routing, finance, and operating controls to work as one workflow—not merely another tracker dashboard—map a live flow with DarkCore before you migrate anything.