Keyplar vs Rindkey
Both move Lemon Squeezy sellers onto their own Stripe account with license keys, files and a customer portal. The big difference is what happens to the activations your customers already have.
What each one says it does
As of November 2026, from keyplar.com (pricing, migration import, Stripe, license keys and Lemon Squeezy alternative pages) and our own product. Things change, so check their site before you decide.
| Keyplar | Rindkey | |
|---|---|---|
| Price | $29 or $79 per month, flat. 14-day trial; you add a card at signup. | Free to start (50 active licenses, no card). Indie $24, Pro $49, Scale $99 per month. First 50 paying customers get 50% off for life. |
| Free plan | No | Yes |
| Where you take payments | Your own Stripe account. It also connects Lemon Squeezy and Polar as gateways, side by side. | Your own Stripe account, including Stripe Managed Payments. |
| How it connects to Stripe | A restricted API key plus one webhook endpoint. | A Stripe webhook, plus an optional restricted key (read-only) to map Payment Links and Managed Payments sales. |
| Lemon Squeezy import | Catalog, orders, subscriptions, then license keys. Says LS-issued keys are imported as they are and keep validating. | Products, license keys, activation limits, expiry dates, status, activations and files. |
| Existing activations | Says software customers already activated keeps validating. Its migration pages don't say whether activation records (instance IDs, seat counts) are imported. | Imported with their original Lemon Squeezy instance IDs, so installed copies keep validating and seat counts carry over. |
| License checks from your app | /api/v1/licenses/validate|activate|deactivate, server to server, with a server-side API key. | Lemon Squeezy-compatible /v1/licenses/activate|validate|deactivate. Same params and JSON. Public endpoints your shipped app can call without a secret. |
| What it delivers | License keys, files, links, customer portal. Pro adds GitHub repo access, Google Drive invites and a custom domain. | License keys, signed file downloads, customer portal. No GitHub repo access. |
Keys that work aren't the whole job
When a customer activates your app, Lemon Squeezy stores that seat as an instance ID, and your app usually saves that ID to validate against later. If the keys move but the activations don't, every installed copy is checking an instance that no longer exists. Then you either reset activation limits for everyone or answer "activation limit reached" emails.
Rindkey imports each activation with its original instance ID. Point your next release at rindkey.com/v1/licenses/… and the IDs your app already stored still validate.
When Keyplar may suit you better
- You sell GitHub repository access. Keyplar lists it. Rindkey doesn't do it.
- You want to keep Lemon Squeezy or Polar connected next to Stripe for a while, with one portal across all of them.
- Your app already validates keys from your own server and you don't need existing activations carried over.
Rindkey suits you if you ship a desktop app, plugin or extension that calls the Lemon Squeezy License API directly, and you want existing customers to stay activated without doing anything.
Rindkey isn't affiliated with Keyplar or Lemon Squeezy. Spot something out of date? Email hello@rindkey.com and we'll fix it.
See what your store needs before you move
The readiness check is free and read-only. Your Lemon Squeezy API key is used in memory for one request and never stored.