Where CAD plugins are sold
Each CAD host has its own catalog, and the rules vary.
- SketchUp runs Extension Warehouse. Its help page says paid extensions appear “with either the price listed or a ‘Listing Page’ tag”. With a price, the buyer purchases in Extension Warehouse; with the Listing Page tag, they “visit the extension developer’s page to purchase and download”. The page also says most paid extensions offer a trial before purchase, and that purchases through Extension Warehouse are non-refundable. A Listing Page extension is one you sell yourself, and that is where Stripe and Clavem fit.
- Autodesk runs the Autodesk App Store, covering AutoCAD, Revit, Fusion and others. Its Publisher Agreement governs fees and licensing for listed apps. Read the current agreement before you choose between a store listing and selling direct; this page does not summarize its terms.
- Other hosts, such as Rhino, have their own catalogs and conventions. Check each one.
Where a store sells for you, weigh its fee against the work of running your own checkout and taxes. Where it sends buyers to your page, you are in the direct case regardless.
What is specific to CAD and BIM
Buyers are firms. A purchase usually goes through procurement. They ask for a quote, an invoice with a VAT number, a purchase order, sometimes a data-protection statement. Stripe can send invoices and collect a tax ID at checkout; see software for businesses and site licenses.
Hosts change yearly. A Revit add-in is built against a specific Revit version, and a firm may run two versions at once. License the product, not the host version: one Clavem product, with builds for each host version uploaded as files labelled revit-2026, revit-2027, and so on. A key for the product works for all of them.
Shared and non-persistent workstations. Engineering firms use shared machines, virtual desktops and remote sessions, where a user’s profile or the machine itself may be rebuilt at each login. Each rebuild can look like a new device. Plan for this:
| Environment | Problem | What to do |
|---|---|---|
| Persistent workstation | None | Activate once, validate at launch |
| Shared workstation, several users | One machine, many accounts | Store the license machine-wide so it takes one slot |
| Non-persistent virtual desktop | State is wiped; every session is a new device | Sell a key with a high device limit for the pool, or deliver the token with the image |
| Air-gapped machine | No outbound network | Verify the signed token offline and refresh from a connected machine |
No floating licenses. Some CAD tools run on a license server that lends seats to whoever asks. Clavem does not do this. Each key has a device limit and each device holds a seat until it is removed. A firm that wants a pool must buy a key with a higher limit and rely on the seats being freed by deactivation or on the device page. Say so before the sale, because some engineering buyers expect floating licenses.
Offline and sensitive networks. Machines that handle confidential projects may have no internet access. The signed token verifies with a public key in the plugin and needs no call; the plugin trusts it until refresh_by, 14 days after issue. For longer gaps, add an administrator flow: refresh the token on a connected machine and copy it over, since a token is not bound to one device. See offline verification.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Annual subscription per seat | Hosts change yearly, so ongoing updates carry a real cost |
| Device limit | 2 per seat; a higher limit for a firm’s pool | Desktop and laptop; pools for virtual desktops |
| Trial | 14 to 30 days, requested through a form | Firms evaluate on a schedule |
| Updates | Releases endpoint with one file per host version | The installer picks the right build for the host |
When a firm buys 10 seats, a Stripe quantity of 10 creates 10 keys, and each has its own limit. Hand them to the firm’s administrator, who assigns them.
Doing this with Clavem
Create a product per plugin, connect Stripe and map the price. After payment, the buyer gets keys and an order page with the installer. Revit and AutoCAD add-ins are usually .NET, so the C# guide applies, including offline verification and device activation; C++ plugins can follow the C++ guide. SketchUp extensions are Ruby, so call the License API with Ruby’s HTTPS library and verify the token with an Ed25519 gem; the call sequence is the same as in the other guides.
Clavem is not a merchant of record, so VAT and sales tax on firm purchases stay with you and Stripe. That is general information, not tax advice.
Guides to follow
- License key validation in C#
- Offline license verification in C#
- Device activation in C#
- Software updates in C#
Questions
Can I sell a SketchUp extension outside Extension Warehouse?
Yes in one case. SketchUp's help says paid extensions show either a price, which buyers pay for in Extension Warehouse, or a Listing Page tag, which sends them to the developer's page to buy and download. The second form is yours to sell and license.
Does Clavem support floating or network licenses?
No. Clavem issues keys with a device limit per key. Firms that want a shared pool of seats can buy a key with a higher device limit, which acts like a site license, or several keys.