Everything Lemon Squeezy did after the sale, on your Stripe account.
License keys, activations, file downloads and a customer portal. 132 days until Lemon Squeezy stops processing.
What breaks when Lemon Squeezy stops
If you sell software or files on Lemon Squeezy, go through each one.
Read-only. Your Lemon Squeezy key stays in memory for one request and is never stored.
- 01Every installed copy of your app that checks its licenseShipped builds call
api.lemonsqueezy.com/v1/licenses/validate. What happens to that API after the shutdown isn't documented. Plan as if it stops and paying users get locked out. - 02Activation limits and existing activationsEach seat a customer activated lives in Lemon Squeezy as an instance ID. Lose them and you either reset limits for everyone or lock people out.
- 03The license keys themselvesThe Lemon Squeezy order export has no license-key column. Keys have to come out over the API before you leave.
- 04Key delivery on new salesStripe Managed Payments won't generate or email a license key when someone buys.
- 05File downloadsLemon Squeezy says customers may lose access to files and links after March 31 if you haven't migrated.
- 06Renewals that keep keys aliveSubscription renewals stop on Lemon Squeezy. Key expiry has to follow the new Stripe subscription instead.
- 07Your customers' “where's my key?” pageThe My Orders page goes away. Without a replacement, customers email you.
Your customers lose their downloads
No license keys? You still have a problem. Lemon Squeezy says buyers may lose access to files and download links after March 31 if you haven't moved them. People who bought from you months ago will come back to a dead link.
- 01We copy your files overEvery product file moves from Lemon Squeezy to private storage on Rindkey.
- 02Past buyers keep accessEach customer gets a simple page, opened from an emailed link, where they can download everything they bought. No password to remember.
- 03New sales just workWhen someone buys through Stripe, they get their download by email straight away. Refunds remove access.
Import, change one URL, keep selling on Stripe
Bring every key and activation over
Products, keys, limits, expiry dates and activations come across from Lemon Squeezy. Instance IDs stay the same, so existing activations keep validating.
$ rindkey import lemonsqueezy --dry-run ✓ 2 products ✓ 1,482 license keys # 3 disabled, 41 expired ✓ 2,907 activations # instance IDs preserved ✓ 6 files → private storage
Illustrative output.
Same endpoints, params and JSON
Point your next release at Rindkey. Activate, validate and deactivate behave the same, so your app's license code doesn't change.
// before POST https://api.lemonsqueezy.com/v1/licenses/validate // after: same body, same response POST https://rindkey.com/v1/licenses/validate ✓ { "valid": true, "license_key": {…} }
Every checkout issues a key
Connect a Stripe webhook. Each purchase creates and emails a key and unlocks downloads. Refunds and cancelled subscriptions revoke access on their own (you choose what a refund does).
Works with Stripe Managed Payments — the fulfillment Lemon Squeezy says you need when you move. Checkout, Payment Links, local-currency pricing, subscription changes at link.com and refunds Stripe issues for you are all handled.
Customers help themselves
A magic-link page where buyers find their keys, free up a seat on an old laptop, and download files through signed links that expire.
Built for the one thing that can't go down
Your customers open your app every day. The check that says “yes, this person paid” has to answer every time.
For developers
- Drop-in Lemon Squeezy License API: same
/v1/licenses/activate|validate|deactivateendpoints, params and JSON. - Import keeps LS instance IDs, activation limits, expiry and status.
- LS API key held in memory for a single request, GET calls only, never written to storage or logs.
- Downloads: HMAC-SHA256 signed URLs, 15-minute expiry, license status checked on every request.
- Per-seller Stripe webhook secrets encrypted at rest with AES-256-GCM; webhook signatures verified with a 5-minute tolerance.
- Offline grace: Ed25519-signed tokens (1 to 30 days) your app verifies locally; drop-in TypeScript verifier in the docs.
- Runs on Cloudflare Workers at the edge, with D1 and R2 storage.
A small independent team
Rindkey is built and run by a small independent team, not a big platform. We started it because the Lemon Squeezy shutdown leaves people who sell software and digital files without a home for their keys and downloads.
Rindkey is new. We don't have customer quotes yet, so you won't see made-up ones here. Questions, or want help planning your move? Email hello@rindkey.com. We answer every message.