Run a lifetime deal (AppSumo-style) from your own server

Lifetime-deal marketplaces are the fastest way for a small software vendor to reach real buyers — AppSumo alone puts listings in front of over a million deal-hunters. What their onboarding pages do not spell out is the plumbing they expect you to already have. This guide lists it, from a vendor that just went through it, and shows how the store layer can be self-hosted end to end.

What a deal marketplace actually requires

When we submitted our booking app to AppSumo (August 2026), the redemption step required, verbatim from the form:

• a CSV of 1,000–10,000 purchase-ready codes — one column, no header, no duplicates, randomized
• a redemption URL on our own site where buyers enter their code
• redemption instructions for buyers, and a support email answered on an SLA
• codes must stay redeemable for months after the deal ends, and the listing stays live at least 120 days

So a "lifetime deal" is not a checkout button. It is a fulfillment system: unique single-use codes, an instant redemption page, license + download delivery, and a way for a buyer to come back for their files in month six.

The self-hosted version of that plumbing

This is exactly the shape of thing this catalog exists for, so we built it into Deliora, our self-hosted store, and ran our own deal on it. The pieces, so you can judge any tool (ours or anyone's) against the list:

• Code generation — a CLI mints any number of unique codes against a product + license tier, printed as exactly the single-column CSV the marketplaces ask for. Unambiguous alphabet (no 0/O or 1/I), because codes get read off phone screens to support staff.
• A public /redeem page — buyer enters code + email; the license key and download link render on the next page and arrive by email. No account creation before the reward.
• Race-proof single use — two people submitting the same code at the same instant cannot both win it; the database, not hope, enforces that. The same buyer re-entering their own code just gets their order back instead of an error.
• Normal orders underneath — every redemption is an ordinary order in the same pipeline as a paid checkout: same license API, same expiring download tokens, same buyer portal for re-downloads later. Refund handling revokes everything, deal order or not.
• The one follow-up — seven days after redemption, one email asks how it is going and, if it is going well, for a review. One. A drip campaign aimed at deal-hunters is how you earn the one-star reviews.

The economics, honestly

Marketplace splits are steep and you should walk in knowing them. On AppSumo's self-serve tier (read from their partner flow, 2026-08-05): 90% goes to you on sales you drive through your own deal link, but sales their marketing drives start at 25% to you, climbing only past $50K net. On a $19 deal, their-traffic sales net you roughly $4.75 each.

That math only works if you treat a marketplace deal as paid discovery — reviews, backlink, buyers you had no path to — rather than a revenue channel, and if your marginal cost per sale is near zero. Self-hosted software with self-hosted fulfillment is the rare case where it genuinely is: no per-seat cloud bill grows with the deal.

Honest boundaries

• Running a deal is a contract: minimum listing windows, redemption periods, support SLAs. Read the agreement; do not list what you cannot support.
• A redemption system does not get you approved — the product, pricing, and listing quality do. This guide covers the plumbing, not the pitch.
• If you sell through WordPress already, EDD with a codes plugin can be assembled into something similar; the difference is one integrated app versus a stack of parts. Choose on maintenance appetite, not ideology.

The redemption system described here ships in Deliora — the same app this store runs on, which is also how we know the codes survive contact with real deal-hunters.