Side by side
Gumroad facts are as of November 2026, from its pricing page and help center.
| Clavem | Gumroad (as of November 2026) | |
|---|---|---|
| Price | Free for 50 active licenses; $29, $79 or $199 a month | No monthly fee |
| Fees on 100 sales of $49 | $29 plan, plus Stripe’s fee: about $201 | 10% plus 50 cents: $540 |
| Merchant of record | No | Yes, for tax collection and remittance |
| License keys | Created when Stripe confirms a payment; one per seat | Enabled on the product’s content page; multi-seat option |
| Device limits | Activation limit per license; buyer device page | None built in; a uses count that you interpret |
| Offline checks | Signed sgt1 token |
Not published |
| Downloads | Upload releases; order page; update endpoint | Product content and files delivered to the buyer |
| API | Activate, validate, deactivate; management API | A verify call; refunded and disputed flags in the response |
| Migration path | CSV or JSON import | Export keys and buyers, then use the file importer |
Fees on 100 sales of $49
Gumroad lists 10% plus 50 cents per transaction for sales through your profile or direct links, and 30% when a new customer finds you through its Discover marketplace. On 100 direct sales of $49 ($4,900) that is $490 plus $50, or $540.
Clavem plus Stripe on the same sales: Stripe’s standard US card rate is 2.9% plus 30 cents (as of November 2026), $172.10, plus the $29 Indie plan: $201.10. The difference of about $339 a month buys Gumroad’s tax handling, so decide what that is worth to you. Counting Stripe’s fee, Gumroad costs more than Clavem from about 8 sales of $49 a month on the Indie plan, or about 22 sales on the Studio plan.
Because Clavem counts active licenses, 100 sales a month of a lifetime product reaches 1,000 licenses after ten months. From then on the Studio plan, $79, covers up to 10,000.
Fees as sales grow
First-month cost at $49 a sale, one-time purchases, US card sales, no tax added. Clavem is the Indie plan plus Stripe’s 2.9% plus 30 cents; Gumroad is 10% plus 50 cents.
| Sales a month | Revenue | Gumroad | Clavem plus Stripe |
|---|---|---|---|
| 20 | $980 | $108.00 | $63.42 |
| 100 | $4,900 | $540.00 | $201.10 |
| 400 | $19,600 | $2,160.00 | $717.40 |
Gumroad’s figure includes tax handling; Clavem’s does not. After the first month a lifetime product accumulates licenses, so the plan steps up from Indie to Studio past 1,000 active licenses.
How the keys behave
Gumroad’s verify call takes a product id and a license key, and returns the purchase: buyer email, sale id, a uses count, and refunded and disputed flags. By default each verify call raises uses by one, so a check on every launch burns through your count unless the call sets increment_uses_count to false. Gumroad’s help says you can correct a wrong count in the Sales dashboard.
Two more details from Gumroad’s help matter for subscriptions. The license API keeps reporting a key as enabled until you disable it, and gives you subscription_ended_at, subscription_cancelled_at and subscription_failed_at timestamps to act on. Your app has to read those fields and decide.
On Clavem the equivalent is automatic. A subscription license expires at the end of its paid period plus three days of grace, comes back when a late payment settles, and a refund in Stripe disables the license. Activations are counted against a seat limit, and the buyer frees a seat from a device page. See device limits.
When Gumroad is the better choice
- You want a hosted storefront, checkout and tax handling in one place, with nothing to connect.
- You sell a product whose key is a courtesy, not a gate, so a uses count is enough.
- You are starting, with few sales, and a percentage fee costs less than a monthly one.
- You value discovery on its marketplace, and accept the 30% on those sales.
When Clavem is the better choice
- Your sales are high enough that a 10% fee is larger than a flat plan.
- You need real device limits, signed offline checks, or a clean subscription lifecycle.
- You want to keep your own Stripe account, customers and payout schedule.
Moving from Gumroad to Clavem
Gumroad’s license endpoints are different from Clavem’s, so the app changes more than a hostname.
- Collect each license key with its buyer’s email from Gumroad’s sales data, and check that your export includes the key column before you rely on it. Gumroad’s example keys are four groups of eight hex characters, and Clavem keeps keys as written, matched without regard to capitals.
- Create a Clavem product and import the file. Set
activation_limitfor each row, or leave it empty to use the product’s limit. Gumroad’s license documentation describes a uses count rather than devices, so there are no devices to carry over. See importing licenses. - Replace the verify call with activate on first run and validate on every launch. See the API reference.
- Move sales to Stripe Checkout or Payment Links and map the Stripe product to the Clavem product.
Run the import again after the cutover date, so keys sold through Gumroad up to that day are included. Imports are safe to repeat: keys already in your account are skipped. More detail: moving from Gumroad.
Questions
Does Gumroad limit how many devices use a license key?
Not by itself. Gumroad's help says enforcement is up to the seller. Each verify call can add to a uses count, and you decide what count is too many. There is no activate and deactivate pair in its license documentation.
Is Gumroad a merchant of record?
Yes. As of November 2026 Gumroad's pricing page says that since 1 January 2025 it handles sales tax collection and remittance as merchant of record. Clavem does not take payments or handle tax.
Can I keep my Gumroad license keys if I move to Clavem?
Yes. Export your keys with their buyers and import the file. Each key is kept as written, and customers keep the key they have. Your app must change, because Gumroad's verify call and Clavem's validate call differ.