What is different about selling to developers
Developers install from a package manager rather than a store, and they can inspect what your tool sends. Four habits shape the licensing.
- They read the code and the traffic. Obfuscation will annoy them and will not hold. Say what the tool sends: the key, a device name, a fingerprint. See what a license check sends.
- They run tools unattended. CI, scheduled jobs and remote machines have no one to type a key. See CLI tools for the CI pattern.
- They buy for teams. A single purchase can cover five seats and need an invoice.
- They work offline sometimes. On a train, on a locked-down network, on an air-gapped build server. A signed token that verifies offline is the right default.
Where the check runs
The kind of tool decides where the license lives and which page to read next.
| Your tool is | The check runs in | Special concern | Read |
|---|---|---|---|
| A VS Code extension | The extension host | No paid listings on the Marketplace; remote machines | VS Code extensions |
| A JetBrains plugin | The IDE’s JVM | The Marketplace sells and licenses for you, for a fee | JetBrains plugins |
| A command-line tool | The binary | CI runners with no state | CLI tools |
| A desktop app for developers | The app | Per-OS releases | Desktop apps |
| A library or SDK | The developer’s build, or the library at load | Your customer’s users must not be affected | below |
| A self-hosted server | The server process | Restarts, containers, no outbound access | Self-hosted software |
Libraries and SDKs
A paid library is licensed differently because there are two parties downstream: the developer who buys it and the people who use the app they build. Put the check where it only touches the buyer.
- At install or build time. The developer’s machine or CI calls
validate, and your tooling enables the paid build or writes a signed token into the project. - At load time, offline. Ship the product’s public key in the library and verify a signed token that the developer embeds in their app. No network call happens in the end user’s session, so your library cannot cause an outage there.
Avoid a live validate on every end-user launch. It adds latency, a failure point and a privacy question to someone else’s product, and the License API is rate limited at 60 requests a minute per key, so one key shared across thousands of users will be refused.
Team purchases
A company that buys five seats pays through Stripe with a quantity of 5. Clavem issues one key per seat, up to 100 per line item, each with its own device limit. The buyer hands the keys out. There are no team seats or admin console, so a manager who wants to move a seat from one developer to another has two ways: the developer removes their device on the device page and the new person activates, or you disable and reissue. If your buyers expect an admin console, that is a real gap; see seat-based licensing for teams.
Remote and ephemeral environments
A developer who uses SSH, dev containers and cloud workspaces creates a new “machine” every time one is rebuilt. Each activation takes a device slot until someone frees it. Three defenses:
- Send a stable
fingerprint, so a container that is rebuilt on the same volume returns the same seat. - Use
validatewithout an instance id for throwaway environments, which takes no slot. - Set the limit above the number of real machines, 5 rather than 2, and handle abuse when you see it.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Annual subscription with updates, or perpetual with paid major versions | Match the support and release effort you carry |
| Device limit | 3 to 5 per developer | Laptop, desktop and remote environments |
| Trial | 14 days, or a free tier | Developers install first and decide later |
| Updates | Releases endpoint with the key in a header | Keeps the key out of URLs and logs |
Doing this with Clavem
Create a product and connect your Stripe account. The first purchase issues a key and an order page with the download. The License API has three calls and no secret, so a plugin, a binary or a Node script can call it. Pick your stack: Go, Rust, Python, Node.js, Deno or Java. Clavem also has an MCP server so you can look up and issue licenses from your editor with a management API key.
Clavem is not a merchant of record. If you sell to developers across the EU, VAT is yours to handle through Stripe or to hand to a merchant of record; the merchant of record article compares the choices. That is general information, not tax advice, so ask an accountant.
Guides to follow
Questions
Should I license a developer tool per developer or per machine?
Per developer is the usual unit, and the device limit stands in for it. A limit of 3 to 5 covers a laptop, a desktop and a remote environment. Teams buy one key per seat, which Stripe's quantity field produces for you.
Can I put a license check in a library that other apps ship?
You can, but a check that phones home from your customer's end users is a bad deal for them. Check at build or install time on the developer's machine, or verify a signed token offline with no network call at all.