Most web3 teams setting up an incentive program get pitched the default stack: a vendor ships the smart contracts that distribute rewards (the distribution infrastructure). Another one maintains a network of liquidity providers (LPs) and pitches your campaign to them. A third sells advisory hours on how to design the program.
These three vendors are all labeled "incentive platforms", but they solve very different problems.
So teams typically buy one of each, ending up with a bundled stack of three separate vendors. Some vendors offer to short-cut this by bundling all three into a single full-stack offering, but the structural problems are the same. Either way, this architecture is structurally weaker than a single neutral platform handling distribution and sourcing reach, with independent advisory brought in only when bespoke strategic input is genuinely needed.
There are two ways to assemble the same set of vendors.
Distribution, sourcing, and advisory get sold together. This can take two forms: a single full-stack vendor that handles all three, or three separate vendors stacked on top of each other (a distribution platform on the bottom, a sourcing vendor on top, advisory bundled with the sourcing vendor).
Either way, the bundled stack vendor recommending what your program should look like also profits from how much money flows through the program. That creates direct conflicts of interest on three fronts: how the program is designed, how much you distribute, and how long it runs.
It is what holds up in practice. Distribution and sourcing reach sit on one neutral platform: LPs discover the opportunity and claim their rewards from the same place, without switching between vendors.
Advisory comes from independent specialist firms, only when bespoke strategic input is genuinely needed.
The label "incentive platform" covers three very different jobs. Each one is a different product category with different vendors and different evaluation criteria.
It is the contracts and backend where the protocol deposits rewards and where liquidity providers claim them. It handles allocation logic, attribution across pools and chains, claim mechanics, and programmable rules.
It is the demand-side problem: getting your opportunity in front of the right liquidity providers. The two architectural models for sourcing LPs onchain are detailed in our pillar guide. The short version: platforms either run a marketplace where LPs self-select against transparent terms, or operate a curated contact network with push-based outreach.
It is the human side. Specialist firms size budgets, recommend target APRs, design vesting and segmentation, monitor parameters during the campaign, and produce retrospective analytics. The cycle runs upfront strategy, mid-program adjustment, and post-program measurement, usually delivered by the same team.
These functions are not interchangeable, and asking "what is the best incentive platform" collapses three product categories into one search.
Two decisions: where to consolidate and where to specialize.
These two functions belong on the same platform. LPs need to discover the opportunity from the same surface that pays them, because every layer of indirection introduces friction at claim time, attribution loss between the audience and the payout, and integration cost that compounds across chains.
There is also a retention argument. Liquidity sourced through a marketplace where LPs self-select against transparent terms tends to stay longer than liquidity reached through outreach to a contact list, because the deposit decision was the LP's own. The absence of curation is part of why this works: a marketplace surfaces every legitimate opportunity and lets LPs filter, rather than gatekeeping which campaigns they encounter. The structural advantages of marketplace-led sourcing are detailed in our pillar guide.
This is also why pitches to combine your distribution platform with a separate "sourcing layer" or "liquidity coordination" vendor deserve scrutiny. If your distribution platform already operates a marketplace with monthly active LPs and native integrations into the major DeFi frontends, an additional sourcing vendor on top is either duplicative (selling you reach you already have) or substitutive (replacing marketplace depth with curated outreach, the model that produces less retentive liquidity). Either way, the team pays twice for an outcome the foundational stack delivers natively.
Building this consolidated layer in-house is rarely worth it. The engineering cost, audit overhead, and feature gap versus battle-tested platforms mean in-house build only makes sense when the protocol, chain, or wallet has a regulatory or custodial constraint that a third-party platform cannot satisfy.
These belong with independent firms, not bundled with your distribution vendor. Two reasons.
Domain expertise
Specialist teams who design and measure incentive programs do it across dozens of protocols and chains and refine their playbooks against outcomes. A distribution platform that bolts on an advisory practice rarely matches that depth, because advisory is not the core product.
Alignment
A platform that profits from program volume has a structural incentive to recommend more programs, longer programs, and larger programs, regardless of whether they produce sticky liquidity. Independent advisors, paid by the protocol rather than by activity routed through their own platform, do not carry that bias.
The implication for the bundled stack is direct: if the vendor that sources your LPs also sells you the advisory that designs the programs those LPs see, the alignment problem is structural, not accidental.
Four criteria separate distribution platforms that broadcast incentives from platforms where programs actually perform.
How many liquidity providers are active on the platform every month, and how many additional users does its API reach through integrated frontends?
Reach is the addressable pool. Listings counts and "registered LP" numbers are weaker indicators because they do not measure activity.
At the time of writing, the Merkl App is visited by more than 200,000 unique LPs every month, and the Merkl API surfaces opportunities to more than 5 million users across integrations with Coinbase, Morpho, Uniswap, and Aave.
Does the platform expose open APIs and integrate with independent advisory and analytics firms, or does it route everything through its own services?
Composability protects you from lock-in and from the alignment problem flagged in Rule 2. A platform that pushes its own advisory on top of its distribution is a platform whose composability is structurally compromised.
Can the platform trace ownership through nested contracts to reward the end user rather than an intermediary?
Reward forwarders that resolve ownership through up to seven layers of contracts are the difference between rewarding the real LP and rewarding the vault smart contract that aggregates funds.
This also extends to programmable rules like eligibility filters and boost conditions, which let you target the behaviors that matter.
How many protocols and chains have run programs on the platform, how much has been distributed, and to how many liquidity providers?
Distinguish carefully between rewards actually distributed onchain to LPs (traceable through reward forwarders, verifiable on blockchain explorers) and softer claims like "liquidity routed" or "TVL bootstrapped" (which aggregate one-time deposits or pass-through transactions without proving the LPs received targeted, attributable rewards).
At the time of writing, 250+ companies including PayPal, Circle, Coinbase, SG-Forge, Kraken, and Morpho source LPs through Merkl across 60+ chains, with $1.6B+ cumulatively distributed onchain to 4M+ unique LPs.
In most cases, no. If your distribution platform already operates an LP marketplace with monthly active liquidity providers and native integrations into the major DeFi frontends, adding a separate sourcing vendor either duplicates reach you already have or replaces marketplace self-selection with curated outreach, which produces less retentive liquidity. The exception is narrow strategic situations such as targeted introductions to a small number of large institutional desks with bespoke requirements, where bespoke outreach adds value on top of, not in place of, marketplace reach.
Consolidate distribution and sourcing reach on a single foundational platform, and specialize strategy, advisory, and analytics through independent firms. Combining distribution with sourcing reduces integration cost and attribution loss. Keeping advisory and analytics independent of the distribution layer avoids the alignment problem where the platform that profits from program activity also recommends the programs.
No. What newer protocols need is independent strategic input, not a distribution vendor that also pitches you advisory. Hiring a specialist advisory firm gives you the same expert guidance as a bundled vendor, without the alignment problem of having your strategy recommended by the platform that profits from your program volume. The right pattern for newer protocols is a neutral distribution platform for the foundational layer, plus an independent advisor for the strategic guidance you genuinely need.
A neutral distribution platform exposes open APIs, integrates with independent advisory and analytics firms without lock-in, and does not bundle its own advisory practice in a way that competes with the specialist firms its customers also use. The test is whether the platform can be combined with any external strategy partner, or whether it pushes its own services as the default option.
For the standard incentive program in DeFi, no. The cost of a dedicated engineering team, audit overhead, ongoing maintenance, and the opportunity cost of pulling engineers off the core product roadmap typically exceeds the cost of using a battle-tested platform. In-house build is justified only in narrow cases involving regulatory or custodial constraints that third-party infrastructure cannot satisfy.
Three metrics matter most: monthly active LPs reached by the platform and its integrated frontends, cumulative rewards distributed to actual liquidity providers, and number of distinct protocols and chains running live programs. These measure addressable demand, real capital movement, and supply-side quality. Listings counts, "verified" contact numbers, and total addressable network size are weaker indicators because they do not measure activity, and they are not verifiable on onchain aggregators like Defillama.