Use cases
Licensing for the software you sell
Every kind of software has its own licensing questions. Pick yours to see what it needs and how to set it up with Stripe.
Kinds of software
- Selling and licensing a productivity app with StripeLicense a notes, task or writing app used on several devices: what Apple forbids on iPhone, why a key is not an account, household limits, lost keys.
- Selling and licensing an AI app with StripeLicense an app that calls a paid model API: your backend verifies Clavem's signed token, provider keys stay off the device, and you meter usage.
- Selling and licensing an indie game directly with StripeSell a PC game from your own site with Stripe and license keys: offline play, device limits for gamers, big build files and storage, Unity, Godot and Unreal.
- Selling and licensing an on-device AI app with StripeLicense an app that runs language models on the user's computer: offline verification, model files over download limits, model licenses, long offline periods.
- Selling and licensing automation scripts with StripeSell Python, shell or PowerShell scripts with Stripe and license keys: what a key protects in readable code, exit codes for cron, and validate versus activate.
- Selling and licensing business software with StripeSell software to companies with Stripe and license keys: seat quantities, invoices, VAT IDs, renewals, and what Clavem lacks: team seats, SSO, webhooks.
- Selling and licensing design and creative tools with StripeLicense a design app or creative utility sold with Stripe: agency seat counts, upgrade prices for new versions, large asset downloads and student discounts.
- Selling and licensing developer tools with StripeSell IDE plugins, CLIs, libraries and desktop tools to developers with Stripe and license keys: per-developer seats, CI and dev containers, offline use.
- Selling and licensing education software with StripeLicense software sold to schools: lab images, shared computers, site licenses, school-year validity, and keeping student names out of device names.
- Selling and licensing scientific software with StripeLicense research software that runs on clusters without internet, must work years later and has academic and commercial prices: offline tokens, login nodes.
- Selling and licensing self-hosted software with StripeLicense software customers run on their own servers or in Docker: a seat per install, stable fingerprints for containers, no outage on a failed check.
- Selling and licensing trading tools with StripeLicense MetaTrader expert advisors and trading bots sold with Stripe: MQL5 Market rules, WebRequest limits, binding to a broker account, VPS moves, TradingView.
Moving from another platform
- Gumroad sellers: moving software licensing to Stripe and ClavemGumroad issues license keys for software. When to stay, and how to move to Stripe and Clavem: how its verify API differs, device limits instead of use counts.
- Paddle sellers: adding license keys to software sold through PaddlePaddle Billing no longer generates license keys. Keep Paddle and issue Clavem keys from your own webhook handler, or move payments to Stripe for automatic keys.
- What Lemon Squeezy sellers of software should do before 31 March 2027Lemon Squeezy stops processing on 31 March 2027. A plan by what you sold: license keys, files, subscriptions, affiliates, PayPal buyers, with dates and gaps.
Platforms
- Licensing a cross-platform desktop app with StripeOne license key for a desktop app on macOS, Windows and Linux: a shared device limit, per-OS release files, which stack guide to follow and where code differs.
- Licensing a menu bar app with Stripe and license keysMenu bar apps stay running for weeks and have no main window. How to enter a license key, re-validate on a timer, handle launch at login and keep trials simple.
- Selling and licensing a CLI tool with StripeLicense a paid command-line tool with Stripe: activate from the terminal, keep the key in a config file, handle CI runners with no state, and update the binary.
- Selling and licensing a Linux app with StripeSell a Linux app with Stripe and license keys: Flathub's monetisation policy, Flatpak network access, machine ids without a keychain, AppImage and .deb updates.
- Selling and licensing a macOS app with StripeSell a Mac app outside the App Store with Stripe and license keys. What Apple's guidelines allow, Keychain storage, device limits, Sparkle-style updates.
- Selling and licensing a Tauri app with StripeLicense a Tauri app with Stripe: do the License API calls from Rust, keep the updater's signing key apart from the license key, and set the HTTP permissions.
- Selling and licensing an Electron app with StripeLicense an Electron app with Stripe: keep keys in the main process, store them with safeStorage, verify tokens with node:crypto, and what autoUpdater needs.
- Selling and licensing Windows software with StripeSell a Windows app with Stripe and license keys: Store policy on third-party purchases, machine ids, silent installs for companies, proxies and updates.
Plugins and extensions
- Selling and licensing a Blender add-on with StripeBlender's extensions platform takes only free GPL add-ons, so paid ones sell elsewhere. License keys with Stripe, Blender's online-access setting, render nodes.
- Selling and licensing a Chrome extension with StripeThe Chrome Web Store ended paid extensions in 2021, so you charge yourself. Sell with Stripe and license keys: MV3 service worker checks, sync pitfalls, policy.
- Selling and licensing a Figma pluginFigma Community sells paid plugins for a flat 15% fee. When to use it, and when to sell with Stripe and license keys: null-origin CORS, clientStorage.
- Selling and licensing a JetBrains plugin with StripeJetBrains Marketplace sells paid plugins for a 15% commission and handles licensing and tax. When it is the better choice, and when to sell the plugin yourself.
- Selling and licensing a Photoshop (UXP) plugin with StripeAdobe's marketplace sells paid UXP plugins via FastSpring with a 90% payout. When to use it, and when to sell with Stripe: manifest permissions, storage limits.
- Selling and licensing a Raycast extensionRaycast Store extensions are public MIT-licensed code reviewed by pull request, so keep the value on a server. A password preference holds the key you check.
- Selling and licensing a VS Code extension with StripeThe VS Code Marketplace has no paid listings, so charge for your extension yourself. License keys, SecretStorage, remote machines that multiply devices, trials.
- Selling and licensing a WordPress plugin with StripeSell a premium WordPress plugin with Stripe and license keys: what WordPress.org forbids, per-site activation, staging sites, own-server updates, expired keys.
- Selling and licensing After Effects plugins with StripeScripts, CEP panels and native effects reach the License API differently. Where Adobe's marketplace fits, render nodes as seats, and how to check a key.
- Selling and licensing an Excel or Office add-in with StripeSell an Excel add-in with Stripe and license keys. AppSource's 3% fee and its work-account limit, web add-ins versus VSTO, same-origin rules, corporate rollout.
- Selling and licensing an Obsidian plugin with StripeObsidian's developer policies allow paid plugins if the README says so. Take payment with Stripe, keep keys out of synced vault files, count vaults and devices.
- Selling and licensing audio plugins with StripeLicense VST3, AU and AAX plugins sold with Stripe: no checks on the audio thread, one activation across formats and DAWs, offline studios and suite bundles.
- Selling and licensing CAD, BIM and 3D plugins with StripeLicense AutoCAD, Revit, SketchUp or Rhino plugins sold with Stripe: store listing or own checkout, virtual desktops, air-gapped machines, no floating licenses.
Who sells
- Adding license keys to an existing Stripe setupAlready selling through Stripe Checkout, Payment Links or Billing? Add license keys, device limits and downloads without changing your checkout.
- Licensing a small studio's software catalogue with StripeA studio selling several apps needs per-product keys, bundles, a release routine and clear roles. What the Studio plan holds, and what Clavem lacks for teams.
- Licensing the paid tier of an open-core projectA key check in public code can be forked away. Ship the paid tier of an open-core project as a separate gated download and verify signed tokens in open source.
- Selling and licensing software as a solo developerWhat it costs a one-person software business to sell with Stripe and Clavem: worked fee math against a percentage platform, free-plan limits, and your duties.