Clavem

Selling and licensing a Blender add-on with Stripe

Blender's own Extensions Platform only hosts free, open-source add-ons under the GPL, so a paid add-on is sold through a marketplace such as Superhive or from your own site. Sell with Stripe, check the key with a call that respects Blender's online-access setting, and remember that GPL code can be copied.

Where paid Blender add-ons are sold

Blender’s own Extensions Platform is a free, open-source catalog. The manual says it “only supports free and open source extensions compliant with Blender’s license”, and the required license for add-ons is GNU General Public License v3.0 or later. A paid add-on cannot be sold there.

Sales happen on a marketplace or your own site. Superhive, which describes itself as “formerly Blender Market”, is a store for Blender tools, and sellers pay it a fee, so read its current pricing page before you compare. Selling from your own site with Stripe keeps the whole sale and the customer’s email, at the cost of handling VAT and sales tax yourself through Stripe. You can also do both: a marketplace listing for reach and your own checkout for buyers who find you directly. A key from Clavem works with either, as long as the marketplace allows license checks in the product, so read its seller terms.

The GPL changes what a key can do

The platform requires the GPL for add-ons, and an add-on you sell yourself is often GPL too. The GPL lets every buyer use, change and share the code. A license check inside GPL code can be removed by anyone, legally.

So do not sell the key as a lock. Sell what a key can still deliver:

  • Updates. Version delivery behind a valid key, with release notes.
  • Support. Answers for key holders.
  • Assets. Presets, libraries and models that are separate files with their own license.
  • Online features. Anything your server renders, stores or computes.

State it plainly in the product page. Buyers of Blender add-ons know the GPL, and a seller who is honest about it earns more trust than one who pretends a check is DRM. The piracy article takes the same view.

What is specific to Blender

Online access is a setting. Blender has an “Allow Online Access” preference, and the manual says an add-on that uses the internet “must check for the (read-only) property bpy.app.online_access”, which can also be set with --offline-mode and --online-mode. Respect it. If online access is off, skip the License API call and use the stored token; do not show an error. Blender notes that it cannot stop third-party add-ons from ignoring the setting, so ignoring it will be noticed.

Dependencies must ship with the add-on. Extensions “must be self-contained”, with their third-party Python modules included. Blender’s recommended way is Python wheels listed in the manifest; the alternative is vendoring a pure-Python package as a sub-module. Python’s standard library has no Ed25519 verification, so choose one for the token check: a wheel such as PyNaCl, built for each platform you support, or a small pure-Python verifier. The check happens once per session, so speed is not a concern. The offline page lists the token steps.

Persistent data. An add-on must not assume its own folder is writable. Use Blender’s per-user extension data path for the key, the instance id and the token. Keep a random id there as the fingerprint, with socket.gethostname() as the instance_name.

Render nodes run Blender with no interface. Studios render with blender -b on many machines. A check that opens a dialog hangs a headless render. In background mode, read the stored token, verify it offline and carry on; never prompt. If your pricing counts render nodes, say how, and sell those as separate keys with a higher device limit.

Several Blender versions on one machine. A user may run 4.2 and 5.x side by side. If each version keeps its own extension data, each activates separately. Send a fingerprint that does not depend on the Blender version, such as a hash of something device-wide, so they share one seat.

Setting Suggested value Why
License type One-time for the current major version, plus paid major upgrades A major-version license is easy to explain and to price
Device limit 2 to 3 Workstation, laptop and a render machine
Trial A limited free edition on the Extensions Platform It is GPL, free and discoverable
Updates Releases endpoint, with files labelled per Blender version The add-on can check at startup and tell the user

Release files for add-ons are small ZIP files, so even the free plan’s 1 GB of storage holds many versions.

Doing this with Clavem

Create a product, connect Stripe, map the price. After payment, the buyer gets a key by email and an order page with the ZIP. In Blender, the add-on’s preferences panel takes the key. Call activate once, then validate when Blender starts and online access is allowed, in a background thread so Blender’s interface does not freeze. The Blender add-on guide shows the flow, and the Python guide covers the HTTP calls. Send your own User-Agent header, because some services block the default Python one.

Guides to follow

Questions

Can I sell an add-on on extensions.blender.org?

The Blender manual says the Extensions Platform only supports free and open-source extensions compliant with Blender's license, and requires add-ons to be licensed GPL 3.0 or later. A paid add-on is sold elsewhere, and you can list a free edition on the platform.

Does a license key stop people copying a GPL add-on?

No. Anyone who has the GPL code may copy and change it, including removing a key check. A key gates what you deliver and run: updates, support, bundled assets and online services.

Sources

  1. Blender Manual, Extension Licenses (checked November 2026)
  2. Blender Manual, Add-ons (internet access, bundled dependencies) (checked November 2026)
  3. Superhive, formerly Blender Market (checked November 2026)