Honestly reviewed for non-technical founders who want to escape Bitly pricing. No vendor spin, just what you actually get.

TL;DR

What it is: Open-source (AGPLv3 core) link attribution platform — short links, click-to-conversion tracking, and affiliate program management in one tool [3].
Who it’s for: Marketing teams and founders who need to know exactly how their links are generating revenue, not just how many clicks they got. Also teams running affiliate or referral programs [2][3].
Cost savings: Self-hosted Dub is free. Bitly’s paid tiers start around $8–35/month for basic analytics, scaling significantly for teams. Self-hosted Dub runs on your own infrastructure with no per-link or per-click fees.
Key strength: The analytics depth. Where Bitly gives you click counts, Dub tracks the full customer journey — click, lead, sale, LTV — and lets you verify data against what your affiliate partners are reporting [2][3].
Key weakness: Self-hosting Dub is meaningfully more complex than most self-hosted tools because the default stack depends on cloud services (Tinybird for analytics, Upstash for Redis, PlanetScale for the database). You’re not just spinning up one Docker container [README]. Enterprise governance features are commercial-only.

What is Dub

Dub started as a side project Steven Tey built while working at Vercel — he wanted to understand how developer advocacy work (articles, tutorials) translated into actual revenue for the company [3]. The URL shortener part was almost incidental. What he kept running into was the attribution problem: links get clicked, but figuring out which links generated actual customers versus just pageviews was messy.

He launched Dub.co publicly, left Vercel in late 2023, and raised $2 million from OSS Capital, Vercel CEO Guillermo Rauch, Balaji Srinivasan, the founders of Framer, and others [3]. As of this review the GitHub repo sits at 23,187 stars.

The TechCrunch profile of Dub from early 2025 [3] is worth reading because it gives honest context for why this product exists: the Honey browser extension scandal, where affiliate attribution was being stolen by a coupon tool that would swap out the original affiliate link at checkout. Tey’s pitch is that transparent, creator-owned attribution — embedded in the link itself rather than sitting in a coupon code — removes the ambiguity that made the Honey situation possible. Whether or not that’s your specific problem, it explains why Dub’s product direction is attribution-first rather than URL-shortening-first.

Today the platform powers 100M+ clicks and 2M+ links monthly, with customers including Twilio, Buffer, Framer, Perplexity, and Vercel [README]. Huberman Lab uses it for affiliate tracking [3]. The Malaysian government is reportedly using the open-source codebase for a government link shortener [3].

Why people choose it

The Product Hunt reviews [1] and the Efficient App case study [2] paint a consistent picture: people come to Dub from Bitly or Short.io, and they don’t go back.

Versus Bitly. This is the direct comparison Dub wins most clearly. One reviewer put it plainly: “After trying every single option available on the market — Bitly, Short.io, self-hosted miscellaneous services — we found a home with Dub. It’s the only tool we’ve felt congruent paying for.” [1] The Efficient App team, which runs a software comparison site and tracks affiliate revenue as a primary business metric, migrated from Short.io to Dub. Their reason wasn’t that Short.io was broken — it was that Short.io’s reporting was “a complete mess” and they never actually used it [2]. Dub’s analytics are usable enough that their team checks data on-the-go throughout the day, which is a signal that the UI isn’t fighting you [2].

The attribution gap Bitly and Short.io leave open. The specific improvement the Efficient App team calls out is verification: “Dub has actually helped us catch click tracking discrepancies with some of our largest partners, which would have cost us thousands of dollars in lost income had we not noticed as quickly as we did.” [2] This is the case for Dub in one sentence. If you’re running affiliate partnerships and trusting the partner’s reported click counts, you have no leverage. Dub gives you an independent count to compare.

Versus self-managed redirects. Several Product Hunt reviewers mentioned that before Dub they were handling redirects themselves — custom routes, manual OG image management, trying to parse server logs for attribution data [1]. “We used to self-manage our redirects but Dub provided so much value with features such as link cloaking and easily managing OG/Twitter meta images that we gradually found ourselves using Dub more and more.” [1]

Features

Based on the README, website scrape, and reviews:

Core link management:

Short links with custom branded domains — the site claims boost in click-through rates of ~30% with custom domains [website]
QR codes auto-generated with each link [website]
Link cloaking [1][website]
OG/Twitter image management per link [1][website]
Device and geo targeting [website]
A/B testing across link destinations [website]
Deep link support [website]
Link expiration [website]
Password protection [website]
UTM builder built in [website]
Folders for link organization [website]
Webhooks [website]

Conversion analytics (the differentiator):

Full funnel tracking: click → lead → sale [3][website]
Real-time analytics dashboard [2][website]
Customer-level data: referral source, device, geography, UTM parameters, lifetime value [website]
AI-generated custom reports and auto-tagging of links [3]
Verified click data you can compare against affiliate partner reporting [2]
Integration with Shopify and Stripe for conversion tracking [3]

Affiliate and partner programs:

Built-in partner management platform — set commission rates, track payouts, generate 1099-NEC reports [website]
Multiple commission structures (percentage, flat fee, recurring, lifetime) [website]
Partner-facing dashboard [website]
The homepage calls out $10M in partner payouts processed to date [website]

Enterprise (commercial-gated):

SSO/SAML via BoxyHQ [README]
RBAC [website]
The README marks an /ee directory explicitly as the Enterprise Edition under a commercial license [README]

Pricing: SaaS vs self-hosted math

The license situation first. Dub uses an “Open Core” model [README]:

Core (99%): AGPLv3 license — you can self-host, inspect, and modify the code, but if you distribute a modified version, you must open-source your changes. This is a meaningful restriction if you’re embedding Dub in a commercial product.
Enterprise Edition (1%, /ee directory): Commercial license. SSO, advanced RBAC, and enterprise governance features are here.

This is not MIT. For a solo founder self-hosting for their own use, AGPLv3 is fine. For a SaaS company that wants to modify and embed Dub in its product, the licensing conversation gets more complicated.

Dub Cloud pricing: The scraped website data doesn’t include the pricing page details directly. Dub does offer a free tier (confirmed in TechCrunch [3]), with paid tiers for more links, analytics history, and team features. Specific tier pricing was not available in the data sources for this review. Check dub.co/pricing for current numbers.

Bitly for comparison (the main SaaS alternative): Bitly’s free tier is limited to 10 links per month with basic analytics. Paid plans start around $8–35/month for individuals, scaling to hundreds per month for teams with advanced analytics. The specific pain point users consistently cite is that Bitly’s analytics don’t go deep enough to verify affiliate attribution — you get clicks, not customer journeys [2][1].

Self-hosted cost math: Software is free (AGPLv3). But self-hosting Dub is not a simple Docker run — see the deployment section below. Realistic server costs for a working self-hosted instance: $10–30/month depending on whether you use managed cloud services or self-host everything including the database and analytics pipeline.

Deployment reality check

This is where Dub differs significantly from most self-hosted tools in this category, and the difference matters for non-technical founders specifically.

The default tech stack [README]:

Next.js — the application framework
Prisma + PlanetScale — database (PlanetScale is a serverless MySQL platform, not something you spin up locally)
Upstash — managed Redis (also a cloud service, not self-hosted Redis)
Tinybird — real-time analytics pipeline (a managed ClickHouse service)
Vercel — the default deployment target

This is designed to be deployed to Vercel + Tinybird + Upstash + PlanetScale, not to a single VPS with Docker Compose. The self-hosting guide at dub.co/docs/self-hosting/guide exists, but the dependencies mean you’re either paying for four separate cloud services (partially defeating the “escape SaaS” goal) or doing significant work to replace them with self-hosted alternatives (PostgreSQL instead of PlanetScale, self-hosted Redis instead of Upstash, something else for analytics instead of Tinybird).

For a technical founder who wants to replace each cloud dependency with a self-hosted equivalent — doable, but this is a half-day to full-day project, not a 30-minute Docker Compose run. For a non-technical founder: this is not a one-click install situation.

The self-hosting guide has been cited positively by the GitHub community, and the project does have 23,000+ stars suggesting many people have gotten it running. But honest expectation-setting: Dub’s deployment story is oriented around their hosted SaaS product. The self-hosting path exists and works, but it requires genuine technical comfort.

Pros and cons

Pros

Attribution depth Bitly doesn’t have. The full click → lead → sale funnel, verifiable against affiliate partner reports — this is the core product advantage and it’s real [2][3].
Affiliate program management built in. Not just tracking but actually running partner programs with payouts, dashboards, and commission structures [website]. Competitive tools charge separately for this.
Genuinely loved by daily users. Product Hunt reviewers aren’t hedging — “I can’t imagine doing my job without Dub anymore”, “saved me at least 4 hours of work weekly” [1]. That’s the signal of a tool that fits its use case well.
23,000+ GitHub stars. Real community, real usage. The source code is readable and educational, even for people not self-hosting [1].
Verified by large marketing teams. Perplexity, Twilio, Framer — these are teams with options [README]. Huberman Lab for affiliate tracking at scale [3].
AI auto-tagging and custom reports without AI taking over the core product — Tey explicitly said they don’t want AI to overshadow the fundamentals [3].
QR codes, device targeting, A/B testing, deep links — more link features than you’d expect from a “URL shortener” [website].

Cons

AGPLv3, not MIT. If you’re building a commercial product on top of Dub or need to embed modified versions, consult a lawyer before assuming self-hosting is cost-free [README].
Self-hosting complexity. The default stack is cloud services (Tinybird, Upstash, PlanetScale, Vercel). True self-hosting requires replacing each with open alternatives — not a beginner task [README].
Analytics depth requires the SaaS or full setup. The Tinybird-powered real-time analytics pipeline is what makes Dub’s attribution valuable. Self-hosting without a ClickHouse-equivalent will likely degrade this [README].
Enterprise features are commercial-gated. SSO is in the /ee directory, commercial license. If your team needs SAML SSO, plan for an enterprise conversation [README].
Small company, young product. Raised $2M. The product is impressive and the team is fast-moving (“We ship fast” is literally an H2 on their homepage), but this is a seed-stage startup [3]. Bet accordingly.
No pricing page in the scraped data. Hard to compare tier-by-tier against Bitly without current pricing. Check dub.co/pricing directly before committing.

Who should use this / who shouldn’t

Use Dub if:

You’re running affiliate or referral programs and need to verify what your partners are reporting back to you.
You’re a marketing team at a growth-stage startup where links drive meaningful revenue and you want a single dashboard instead of stitching together click data from five different affiliate platforms.
You’re technical enough to deploy Next.js apps and work with external managed services (or willing to pay for Dub’s hosted version).
You value open-source code for inspection, contribution, or educational purposes — the codebase is reportedly clean and readable [1].

Skip it (stay on Bitly) if:

You’re shortening a handful of links for social posts and don’t care about downstream attribution.
Self-hosting setup complexity isn’t worth the savings for your use case.
You need a one-click install that runs on a single VPS.

Skip it (look at alternatives) if:

You need MIT licensing specifically — the AGPLv3 core has implications for commercial use cases that MIT doesn’t.
Your use case is internal URL shortening without affiliate tracking — there are simpler tools for this.

Alternatives worth considering

Bitly — the incumbent. Easier to set up, no self-hosting required, but analytics depth is significantly less than Dub for affiliate attribution use cases. Still the safe choice if you just need a URL shortener.
Short.io — what the Efficient App team migrated from [2]. Cheaper than Bitly for volume, but the reporting UI has been criticized as difficult to work with.
YOURLS — older, simpler self-hosted URL shortener. Genuinely easy to self-host (single PHP app), but it’s a URL shortener, not an attribution platform. No conversion tracking, no affiliate programs.
Kutt — another open-source URL shortener (MIT), Docker-friendly, much simpler to self-host than Dub. Right choice if you just need short links and basic click stats.
Shlinkio/shlink — open-source (MIT), PHP, Docker-friendly, REST API first. More mature self-hosting story than Dub but no affiliate/conversion features.
Rewardful / PartnerStack — if what you actually need is affiliate program management and you don’t care about link shortening specifically, these are purpose-built.

Bottom line

Dub is the right tool if your specific problem is affiliate attribution — knowing which links generated real revenue, being able to verify that against partner reports, and running your partner program from one place. For that use case, the Product Hunt reviewers are right: it’s the best available option, and the Efficient App case study [2] shows exactly how much money that attribution visibility can recover. The open-source codebase is a genuine advantage for inspection and trust, even if the self-hosting path is more complex than the marketing suggests.

For non-technical founders, the honest recommendation is to use the hosted version and treat the open-source nature as insurance — you can see the code, you’re not locked to a black box, and if the company went away you’d have the code. Self-hosting Dub is an engineering project, not an afternoon. If that setup work is the blocker, that’s exactly what upready.dev deploys for clients.

Sources

Product Hunt — Dub Reviews (23 reviews, 5.0/5). https://www.producthunt.com/products/dub/reviews
Alex Bass, Efficient App — “Efficient App Saves Thousands of Dollars with Dub” (Dub customer case study). https://dub.co/customers/efficient
Ivan Mehta, TechCrunch — “Dub.co is an open source URL shortener and link attribution engine packed into one” (Jan 16, 2025). https://techcrunch.com/2025/01/16/dub-co-is-an-open-source-url-shortener-and-link-attribution-engine-packed-into-one/