Volume Licensing for Software

Volume licensing sells a large block of seats to one buyer in a single transaction, typically at a lower per-seat price than an individual or small-team purchase. The buyer is an organisation, not a person — a procurement team, an IT department, or a manager approving software for a whole department. This page is for the developer whose app is being considered for an org-wide rollout and who needs to understand what that buying pattern requires technically and commercially.

What volume licensing means

Volume licensing is the practice of selling many seats at once, in one agreement, to one purchaser. Rather than asking twenty people to each buy an individual license, or four small teams to each buy a team tier, an organisation buys a single block that covers everyone in one step.

The mechanism is identical to a team tier — a key with a seat count attached — but the scale and the buyer are different. A team purchase might involve a manager choosing a software tool. A volume purchase often goes through a procurement process: a quote, an approval, sometimes a purchase order. The technical requirements stay the same; what changes is the buyer’s expectations around seat count, deployment, and pricing.

Bulk seats and high activation limits

A volume license is, technically, one license key with a high activation limit. The activationLimit on that key determines how many machines may activate against it. An organisation licensing a hundred seats receives a key whose activationLimit is one hundred. The licensing server counts each device activation against that limit and rejects requests once it is reached.

There is nothing structurally different about a hundred-seat key compared to a five-seat key. The same activation call runs on each machine, the same server checks the count, and the same signed lease comes back to confirm entitlement. The scale is in the number, not in a different product category.

This matters because it keeps deployment simple. IT can distribute the key to all machines in the same way they would push any configuration value. Each machine activates individually when the app first runs. Read more about how individual device activations are counted and verified in device activations.

Deploying across an organisation

When IT rolls out software to a managed fleet, they typically bundle configuration with the installer. A volume license key is just a string — it can be embedded in a managed defaults file, pushed through an MDM profile, or pre-populated in the app’s preferences on first launch. Each machine runs the app, the key is already present, and the activation happens automatically without the end user entering anything.

After activation, the server issues a signed lease to that machine. Every subsequent launch verifies the lease locally without a network call. This matters in enterprise environments where machines may sit on restricted networks, have no outbound internet access at all, or be explicitly air-gapped for security reasons. The app checks its entitlement against the locally stored signed lease and continues without contacting the server. Only the initial activation, and periodic revalidations, require a connection.

The buyer can see which devices hold an activation through the customer portal and deactivate machines that have been retired or reassigned. Read more about the local verification step in offline license validation.

Volume pricing

Volume pricing acknowledges that a large buyer accepting a single invoice for a hundred seats is a different customer from someone buying five. The typical structure is a per-seat price that falls in steps: a standard per-seat rate up to a certain count, a lower rate above that threshold, and progressively lower rates for larger blocks. Large organisations may also prefer a custom agreement rather than a self-serve checkout.

Practically, this means defining a small number of volume tiers: perhaps a standard team tier, a mid-size tier, and a large-org tier. Each tier has a seat count and a price. Buyers who need counts that do not fit a preset tier, or who need a formal quote rather than a card payment, get routed to a direct conversation. Most independent app developers do not need a complex discount matrix — two or three tier sizes plus an invitation to contact you for larger needs covers the realistic range of buyers.

Doing it with Keylight

Volume licensing in Keylight is a license tier with a high activation limit, sold through a single Stripe checkout. You define the tier in your Keylight product — setting the activationLimit to match the seat count — and point your pricing page at the corresponding Stripe payment link. The Keylight server issues the key, counts every activation against the limit, rejects requests once the count is reached, and issues a signed lease to each successfully activated device.

For the largest buyers who want a custom quote, you take the order outside Stripe and issue the key manually in the Keylight dashboard with the agreed activation limit.

The code on each machine is the same activation call used on any other tier:

import KeylightSDK

// Activate a customer-entered key on this device
await licensing.activate(key: enteredKey)

switch licensing.state {
case .licensed:
    enablePaidFeatures()
case .invalid:
    // activationError carries the reason — e.g. activation limit reached
    showActivationError(licensing.activationError)
default:
    break
}

If the activation limit is reached — every seat in the block is already in use — the server rejects the request and the SDK surfaces the reason through activationError, prompting the user to contact their IT administrator to free a slot or request an upgrade. For the seat mechanism that underpins both team and volume tiers, see seat-based licensing. Pricing starts at $19/month with a free tier to test the full activation flow before you go live.