OpenPartner vs Tolt: when a Stripe-native affiliate tracker isn't enough

Tolt’s pitch is straightforward: connect Stripe, share a link, pay your affiliates. For a SaaS that just wants to turn on referral revenue without hiring an affiliate manager, that’s the right scope. Tolt does it well.

If your program stays simple, Tolt stays good. The friction shows up later — when your attribution needs to survive Safari, when last-click stops being the right model, when you want to pull raw events into your warehouse, or when an affiliate running a real tracker stack asks for an S2S postback. This post walks through what’s the same and where the two products diverge.

What’s similar

Both products do the basics that any affiliate platform should:

• Per-program commission rules (percentage or fixed, recurring or one-time)
• Stripe-native conversion tracking
• A partner portal with click and earning analytics
• Direct partner payouts (no platform skim on what the brand pays the partner)

If your program is small, last-click works for you, and you’re never going to leave the platform, you’ll be fine on either.

Where the products diverge

Open source vs closed source

OpenPartner’s full stack is MIT-licensed — the click router, the attribution engine, the admin portal, the SDK, all of it. Self-host on a $20 droplet with Docker Compose, or run our hosted version and walk away with a full data export whenever you want.

Tolt is closed source, hosted-only. Whatever attribution decisions get made, they happen inside their platform; you see the result, not the inputs.

Attribution depth

Tolt ships last-click within a configurable cookie window. That’s the right default and covers most SaaS programs.

OpenPartner ships four models — last-click, first-click, linear, position-based — and treats attribution as a query over raw events. You can switch models, run the Re-derive job to recompute history, and keep both versions of the data.

That matters when the program grows past one buyer journey. A content-affiliate program where partners write comparison posts the buyer reads three weeks before signup looks nothing like a creator-driven program where the buyer signs up the same hour they click. Last-click is a fine starting point; it’s a bad finishing point.

Cookie + cross-device handling

Both platforms set first-party cookies on the brand’s domain (the only way attribution survives Safari ITP, Firefox Total Cookie Protection, and Brave). The difference is what happens when the cookie isn’t there.

OpenPartner writes an Identity row at first identify — (userId, clickId). From that moment forward, conversions from the same userId attribute via the Identity table, even with no cookie. This is what makes attribution survive a 60-day signup gap on Safari and survive cross-device sign-ins.

Tolt’s cookie window is the cookie window. If the cookie expires or the user signs up on a device that never had it, you lose the click. For short-cycle SaaS that’s fine; for SaaS with a 14-day or 30-day trial, on Safari, with cross-device sign-ins — it’s a measurable attribution leak.

Integration surface

OpenPartner exposes three integration paths: a server SDK for inbound conversion events, outbound webhooks for downstream stacks, and partner postbacks that fire S2S to the partner’s tracker (Voluum, Binom, RedTrack) the moment their click converts.

Tolt is built for the SaaS-and-its-affiliates world; partner-side postbacks for performance-marketing trackers aren’t part of its model. If your partner mix is “creator share-link plus a couple of Twitter accounts” you’ll never miss this. If your partner mix is “performance affiliate with a Voluum stack who’s used to S2S postbacks from every network they’ve ever worked with” — you’ll feel it on day one.

Data portability

OpenPartner stores raw clicks, identities, events, and commissions in your Postgres. Settings → Export data produces CSV + JSON + a pg_dump-compatible SQL file. Re-import on another instance and attribution re-derives from raw events under the configured model. Lossless.

Tolt has CSV export. Useful for spreadsheets; not enough to rebuild your attribution elsewhere.

The honest decision tree

Pick Tolt if:

• You’re an early Stripe-billing SaaS and want the fastest possible “share this link” flow
• Your program is small enough that one attribution model is the right model
• You don’t have partners running their own tracker stacks
• Polished hosted UX matters more to you than infrastructure control

Pick OpenPartner if:

• You want self-host on day one or as an option for later
• You want multiple attribution models and the ability to swap them on historical data
• Your buyer journey crosses devices or trial windows on Safari
• Some of your partners run Voluum/Binom/RedTrack and expect S2S postbacks
• You want raw events in your own warehouse for analytics and audit

There’s no shame in starting on Tolt and migrating later. The shame is starting on a platform that locks the data in and not migrating later, when the costs of staying have silently grown past the cost of moving.

If you’re already past the simple-program stage, start on the Revshare plan — no monthly fee, you only pay when partners actually drive revenue.