Licensing for developer tools

Developer tools are an unforgiving thing to license. The customers are technical, the machines they run on are hostile to network calls, and a tool that succeeds spreads from one engineer to a team faster than its licensing was designed for. This page covers how to license a devtool so it survives all of that.

Where developer tools actually run

A consumer Mac app runs on a home laptop with ordinary Wi-Fi. A developer tool does not. It runs:

• On air-gapped machines — secure environments with no internet by policy.
• Inside CI runners that are firewalled to a narrow allowlist of hosts.
• Behind strict corporate firewalls that block outbound traffic on anything unusual.
• On a laptop in offline mode while the developer is heads-down or travelling.

Every one of those environments breaks a licensing scheme that phones home. If your tool needs a server call to confirm its license, it will fail — not for pirates, but for paying engineers doing exactly what they paid to do. And these customers diagnose the failure precisely: they will see the blocked request and know your licensing is the problem.

This makes offline license validation not a nice-to-have but the baseline. The license must be a signed key the tool verifies locally, with no network call, so it works on the air-gapped box and in the firewalled CI runner. Periodic online revalidation, when the machine does have a connection, catches revocations — but it never blocks the tool from running.

Technical customers notice licensing

Developers are unusually attentive to how a tool behaves. A licensing scheme that calls home on every launch, that adds a startup delay, or that feels like DRM will be noticed, discussed, and held against the product.

A signed-key model is the least intrusive option available. Verification is local computation — no telemetry-shaped request, no latency, no dependency on your servers being up. The tool launches instantly whether or not there is a network. For a technical audience, “it just works offline and doesn’t phone home” is a feature they will explicitly appreciate, not merely tolerate.

Scaling from one developer to a team

The defining lifecycle of a successful devtool: one engineer buys it, loves it, and tells their team. Suddenly the license needs to cover ten people. If your licensing cannot express that without re-architecting, you either lose the team sale or hand out an unlimited key and lose the revenue.

A licensing layer handles this through the activation limit, which doubles as a seat count. A solo license allows a small number of device activations; a team license allows more. Each engineer’s machine activates against the shared license, the activation system tracks the count, and when the team grows they move to a higher tier. The same key model scales from one seat to many — no second system, no migration.

Doing it with Keylight

Keylight issues every license as an Ed25519-signed lease. Your tool ships with the public key and verifies the lease locally — so it runs on the air-gapped machine and in the firewalled CI runner. A Stripe payment issues the license automatically; team tiers simply carry a higher activation limit.

The Apple-platform SDK gives a Mac utility the same checkOnLaunch() and state model used everywhere:

import KeylightSDK

await licensing.checkOnLaunch()

switch licensing.state {
case .licensed:
    enableTool()
case .trial(let daysLeft):
    showTrialBanner(daysLeft: daysLeft)
case .expired:
    showRenewalPrompt()
case .invalid:
    showActivationSheet()
}

For a command-line tool, the same signed-lease verification applies — the tool checks the lease at startup and proceeds. Verification never needs the network; only the occasional background revalidation does, and that degrades gracefully when the machine is offline.

Sell developer tools the way developers want to be sold to: a signed key, instant offline launch, no call home, and a seat model that grows with the team. See offline license validation for the verification model, the activation system for seats, and Pricing for plans — from $19/month with a free tier.