Polar vs Lemon Squeezy for indie SaaS billing?

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

Polar and Lemon Squeezy are both merchant-of-record platforms, which means they handle sales tax and VAT compliance for you and take a larger cut than Stripe in exchange. Lemon Squeezy has more years in market, a more mature dashboard, and was acquired by Stripe in 2024, which affects its long-term roadmap. Polar is newer, developer-first, and leans into usage-based billing and a cleaner API — but it's less battle-tested at scale. Neither is "better" in the abstract; the right one depends on what you're selling and how much billing complexity you want to own yourself.

What merchant of record actually buys you

If you've ever tried to register for VAT in a dozen EU countries because you crossed a digital goods threshold, you already know why MoR exists. Both Polar and Lemon Squeezy sit between you and your customer as the seller of record. They collect the customer's payment, remit the correct sales tax or VAT, issue the invoice under their own entity, and hand you the net payout. In exchange they take a cut that's meaningfully higher than Stripe's ~2.9% — usually somewhere in the 4-6% range depending on the plan and payment method, plus payout fees. The exact number changes often enough on both platforms that you should pull current rates from their pricing pages rather than trust a number repeated in a blog post from six months ago.

The tradeoff is real: you give up some margin and a bit of control over the checkout experience, and you get freedom from being your own tax authority liaison. For a solo founder running one or two SaaS products, that trade is usually worth it. For someone running ten mobile and web apps across different markets, the calculus changes per product — more on that below.

Where they actually differ

Maturity and ecosystem. Lemon Squeezy has been live longer, has more integrations (Zapier, Make, more no-code tools), and a dashboard that feels designed for non-developers as well as developers. Polar's API and SDKs are newer and lean hard into being developer-first — if your mental model is "Stripe but someone else handles tax," Polar's docs will feel more familiar.

Stripe acquisition. Lemon Squeezy being owned by Stripe is worth sitting with. It could mean deeper future integration with Stripe's ecosystem, or it could mean slower independent iteration, or a future folding into a Stripe-branded product. Nobody outside Stripe knows the roadmap. If platform independence matters to you, weigh that uncertainty explicitly rather than assuming business as usual.

Usage-based and metered billing. Polar has put more public effort into supporting usage-based pricing models natively — relevant if you're billing by API calls, seats that scale, or credits rather than flat tiers. Lemon Squeezy's strength has historically been flat subscription and one-time digital product sales. If your pricing model is metered, check each platform's current docs for how they handle proration and overages before committing — this is an area both are actively building out, so what's true today may not be true in six months.

Checkout and storefront flexibility. Both offer hosted checkout pages and embeddable overlays. If you want a fully custom checkout flow, neither replaces a direct Stripe integration — you're choosing MoR convenience, which comes with some UI constraints on both sides.

Payout currencies and schedules. Payout frequency, supported currencies, and minimum payout thresholds differ and change over time. This is boring but it matters if cash flow timing affects how you run your business — pull the current numbers from each platform's docs rather than assuming parity.

The question underneath the question

For most solo founders asking "Polar or Lemon Squeezy," the real question is usually: "do I need a merchant of record at all, or can I run Stripe directly and handle tax myself?" If you're selling B2B software to a handful of customers who pay by invoice, direct Stripe plus a tool like Stripe Tax might be cheaper and simpler than giving up margin to an MoR. If you're selling a cheap, high-volume consumer subscription across many countries, MoR pricing starts looking like the cost of not hiring a tax accountant — which it effectively is.

Whichever way you land, one thing is non-negotiable: whatever billing platform you pick, give external tools read-only, scoped access rather than full account credentials. If you later connect a dashboard or analytics tool to pull subscription data, it should request the minimum permission needed — the same logic we lay out for Stripe restricted keys vs Connect OAuth.

Where this fits for a multi-product founder

Here's the part that doesn't show up in most Polar-vs-Lemon-Squeezy comparisons: if you run more than one or two products, you may end up on different billing platforms for different apps. A consumer mobile app monetized through RevenueCat and App Store/Play billing has nothing to do with your web SaaS on Polar or Lemon Squeezy. That's fine on its own, but it means your revenue picture is now split across three or four systems with three or four different definitions of "MRR," "churn," and "net revenue."

That's a billing decision bleeding into a reporting problem. Picking Polar over Lemon Squeezy (or vice versa) solves tax compliance for one product. It doesn't give you a combined view of what your whole portfolio is actually earning this month, which products are growing, and which are quietly dying. For that you need something sitting on top of your billing tools rather than instead of them — which is the gap SoleOS tries to fill, pulling Stripe and RevenueCat data (among other connectors) into one dashboard rather than another checkout flow. We're SoleOS writing about this because it's our space, so take that bias as given. If you only run one product on one billing platform, you don't need a portfolio tool at all — your billing dashboard's built-in reports are enough; see SoleOS vs a spreadsheet for where the line usually sits.

If you do run several products and want to see what combining Stripe and subscription data actually looks like before committing to anything, the live demo uses sample data and needs no sign-up, and the metrics dictionary shows exactly how MRR and churn get calculated so there's no mystery math.

Frequently asked questions

Does Polar or Lemon Squeezy cost less overall?

It depends on your transaction volume, geography, and whether you're on an annual or monthly plan with each. Both charge a percentage plus payout fees that are higher than raw Stripe rates because they're absorbing your tax compliance burden. Pull current fee schedules from both pricing pages and model them against your actual transaction volume and country mix rather than trusting a cross-site number — fees on both platforms have changed before and will again.

Can I switch from one to the other later?

Yes, but it's not instant. You'll need to migrate your product catalog, re-point checkout links, and handle the transition for existing subscribers, which usually means running both briefly in parallel or timing the switch around a billing cycle. Treat it like any payment migration: plan for a cutover window and test checkout end to end before sending real traffic to it.

Do I need a merchant of record if I only sell to US customers?

Maybe not. US sales tax nexus rules are state-by-state and generally kick in at higher revenue thresholds than EU VAT does. If you're US-only and under most states' economic nexus thresholds, running Stripe directly with Stripe Tax for calculation (without full MoR) can be cheaper. Reassess once you start seeing non-US signups or cross a few states' nexus thresholds.

How does this interact with mobile app billing?

It doesn't, directly — Apple and Google are the merchant of record for in-app purchases on iOS and Android, and they take their own cut (typically 15-30% depending on program and revenue tier). Polar and Lemon Squeezy are relevant for web checkout only. If you run both a web SaaS and a mobile app, you'll have RevenueCat or native store billing on one side and Polar/Lemon Squeezy on the other — see tracking Stripe and RevenueCat together for how to reconcile the two.

Which one is easier to set up as a solo founder with no finance background?

Both are designed for exactly this audience and neither requires a finance team. Lemon Squeezy's dashboard has historically been described as more approachable for non-developers; Polar leans on developers being comfortable reading API docs. If you're not sure, sign up for both with test mode, build a checkout flow for a single product in each, and see which one you'd rather look at every day — that hands-on comparison will tell you more than any spec sheet.