Not a switch. A layer.
LicensorPro vs Lemon Squeezy
These two are not really competitors, and a page that pretended otherwise would waste your time. Lemon Squeezy takes the money and deals with the tax. LicensorPro decides whether a licence key is valid and ships the update. Plenty of people run both, and that is a sensible setup rather than a compromise.
The one-line version
| Lemon Squeezy | LicensorPro | |
|---|---|---|
| What it is | Merchant of record | Licensing & update server |
| Takes payments | Yes, as the seller | Through your gateway, which can be Lemon Squeezy |
| Handles global sales tax / VAT | Yes, as the seller of record | No |
| Issues licence keys | Yes, with licence length and activation limits, and an API to activate, validate and deactivate | Yes, with per-site activations, limits and expiry |
| Serves WordPress plugin updates | Yes, through their WordPress plugin plus licence keys | Yes, built in |
| Where licence data lives | Lemon Squeezy's platform | Your own server and database |
| Cost | 5% + 50¢ per transaction | $199–$799/year, flat · Solo $149.25 with WELCOME25 |
Lemon Squeezy is a Stripe company now
Worth knowing if you are picking a billing partner for the next five years. Their January 2026 update on the Lemon Squeezy blog puts it plainly: “When Stripe acquired Lemon Squeezy in 2024, it wasn't just about joining a bigger company.” and “Our goal is to provide Lemon Squeezy users an easy way to migrate to Stripe Managed Payments.” (checked 17 September 2026).
That is not a warning. Stripe is about as stable a home as a billing product can have, and nothing suggests Lemon Squeezy is going anywhere. But it does mean the roadmap is Stripe's roadmap, which is worth a moment's thought if being on a large platform's schedule is something you have been burned by before.
5% sounds small until you multiply it
A merchant of record earns its percentage. Lemon Squeezy becomes the legal seller, so EU VAT, US sales tax, invoices and remittance stop being your problem. For a solo developer that is genuinely worth paying for, and we will not pretend otherwise.
The thing to be clear-eyed about is that the percentage never stops, and it scales with your success rather than with the work being done for you.
| Monthly revenue | Lemon Squeezy fee | Per year |
|---|---|---|
| $1,000 | ~$50 + 50¢/txn | ~$600+ |
| $5,000 | ~$250 + 50¢/txn | ~$3,000+ |
| $10,000 | ~$500 + 50¢/txn | ~$6,000+ |
LicensorPro is $199 to $799 a year regardless of what you sell. But read that comparison honestly: it is not $6,000 against $399, because LicensorPro doesn't process payments itself. You would still be paying a gateway, and you would still owe the tax work to somebody.
Feature by feature
Lemon Squeezy rows come from its pricing page and licensing docs. Our rows are checked against the LicensorPro 2.5.1 release. An earlier version of this page listed affiliates, discount codes and a customer portal as things only Lemon Squeezy has; LicensorPro has all three, so they are now in the table.
✓ included✓ Pro+ only from that tier up~ partly (catch noted)✗ not availablenot tested hands-on paid screen we did not buy
What each one is4 rows
| Feature | Lemon Squeezy | LicensorPro |
|---|---|---|
| Merchant of record (sales tax and VAT) | ✓ Yes | No; can use Lemon Squeezy or another MoR as its gateway |
| Cost | 5% + 50¢ per transaction; some payments carry extra fees | $199 to $799 a year, flat, plus your gateway |
| Where licence and customer data lives | Lemon Squeezy's platform | Your own server and database |
| OwnershipLemon Squeezy's January 2026 update says its goal is an easy migration path to Stripe Managed Payments | Stripe (acquired 2024) | Independent; you run the software |
Licensing and updates8 rows
| Feature | Lemon Squeezy | LicensorPro |
|---|---|---|
| Licence keys with length and activation limit | ✓ Yes | ✓ Yes |
| API to activate, validate and deactivate | ✓ Yes | ✓ Yes |
| WordPress plugin and theme updates | Via their WordPress integration | Built in, with a WordPress SDK |
| Release channels and staged rollouts | not tested hands-on | Rollouts on Solo; beta, RC, dev channels on Studio |
| Signed licence responses checked by the SDK | not tested hands-on | ✓ Yes |
| SDKs outside WordPress | License API | PHP, Python, Java, .NET and JS |
| Dev and staging sites that don't use a seat | not tested hands-on | ✓ Yes |
| Keys survive a change of payment provider | n/a | ✓ Yes |
Selling10 rows
| Feature | Lemon Squeezy | LicensorPro |
|---|---|---|
| Checkout | Hosted, overlay and store | Through 19 gateway drivers, Lemon Squeezy included |
| Subscriptions, trials, upgrades and downgrades | ✓ Yes | Trials on Stripe and PayPal; prorated plan changes on Stripe and Polar |
| Discount codes and bundles | ✓ Yes | Codes Solo; bundles Studio |
| Affiliates | ✓ Yes | Studio |
| Customer portal | ✓ Yes | ✓ Yes |
| Abandoned cart and failed payment recovery | ✓ Yes | ✓ Yes |
| Usage-based billing, pay what you want, lead magnets | ✓ Yes | ✗ No |
| Fraud protection | AI fraud protection | Blocklist; the gateway's own tools |
| Email marketing | Built in; free to 500 subscribers | Renewal reminders and transactional email |
| Revenue reports | MRR, refunds, average order value | Revenue, MRR, churn, LTV, ARPU, conversion, refund rate |
Sources (4)
- Lemon Squeezy: https://www.lemonsqueezy.com/pricing
- LicensorPro: https://jnkplugins.com/licensorpro/pricing.php
- Lemon Squeezy: https://docs.lemonsqueezy.com/help/licensing/generating-license-keys
- Lemon Squeezy: https://www.lemonsqueezy.com/blog/2026-update
What only one of them does
Only in Lemon Squeezy
- Merchant of record: sales tax and VAT collected, filed and paid for you, plus AI fraud protection and chargeback handling.
- Usage-based billing, pay-what-you-want pricing, lead magnets and built-in email marketing.
- A hosted store and checkout overlays, with nothing to run.
Only in LicensorPro
- Licences, activations and customers in your own database, independent of any payment provider.
- Release channels, staged rollouts, dev and staging domains that don't use a seat, and SDKs that verify signed licence responses.
- Lemon Squeezy is one of 19 gateway drivers, so you can keep it for checkout and tax and still own licensing.
What LicensorPro looks like
Screens from LicensorPro 2.5.1 on our own machine with demo data. The licence page's API address is shown as licenses.northwind.studio instead of our local address.
How we compared. Lemon Squeezy pricing and features come from lemonsqueezy.com/pricing, its licensing help docs and its 28 January 2026 update post, read on 17 September 2026. We haven't opened a Lemon Squeezy store for this page. LicensorPro rows were checked against the 2.5.1 release and our pricing page. Rows marked not tested are ones Lemon Squeezy's pages don't settle.
The setup most people actually end up with
A merchant of record at the front for checkout and tax, LicensorPro behind it for licensing and updates. The webhook from the sale creates the licence; everything after that is yours. This site runs its own products the same way, with Polar as the merchant of record rather than Lemon Squeezy.
To be fair to Lemon Squeezy: if you are happy for your licence data to live on their platform, their licence keys and WordPress update plugin already cover a lot of what a small plugin shop needs, and you may not need a separate licensing server at all.
Which one should you actually pick
Lemon Squeezy alone is enough if…
- You are happy with their licence keys and WordPress update plugin, and with the data living on their platform.
- You sell a one-off download, or a handful of plugins with simple activation rules.
- You want the smallest possible number of moving parts, and 5% is a fair price for that.
Add LicensorPro if…
- You want licensing and updates that stay put if you ever move checkout away from Lemon Squeezy.
- You license PHP apps or scripts as well as WordPress plugins.
- You want your licence data on infrastructure you control.
Found something wrong on this page? Lemon Squeezy's pricing and ownership have both changed recently, and we would rather be corrected than be inaccurate. Tell us and we will fix it — [email protected].