Four kinds of product. One set of building blocks.
The same entitlement, activation and metering serve SaaS, a desktop install, a customer’s data center and an offline device. Each section shows how the pieces map to yours, next to a working demo that opens in your browser. Mirage runs on a real license. The other three simulate their licensing in the browser.
SaaS product
Your backend holds the license, so end users go straight to work.
Each customer has one entitlement, with seats for their users and meters for what they consume.
- Feature gates travel inside the license and are checked in-process. Each customer keeps exactly what they bought, even when you edit the catalog later.
- API quotas carry tier thresholds; MeteredUsage.OverageStatusChanged reaches your CRM when a customer crosses one.
- Plan changes mid-period are policy settings in the portal.
Desktop application
Activated with a code, locked to the machine, expected to keep working on a plane.
Sold perpetual or by subscription, with team seats and add-on modules.
- Component-matched fingerprints survive a RAM upgrade, and the customer keeps the same seat.
- Floating team seats: the service refuses the N+1th checkout, and a released session frees the seat.
- Add-on modules arrive with the next license refresh, in the version the customer already runs.
On-premises & air-gapped
The license is a signed artifact the software verifies by itself, and it travels by network or by file.
Over the network, or on a USB stick — the trust model is the same.
- Request file out, signed response in. Activation works fully offline.
- Usage is exported as a file and answered with a signed receipt that renews the lease.
- Every exchange starts inside the customer’s network. The software works fully offline. Their machines hold just a public key and signed files.
Connected devices
The device itself is the licensee.
Each unit activates against its own entitlement, keyed to a hardware fingerprint.
- Per-unit plans keyed to a VIN or serial number.
- Buyable options are gated on-board, and every use is checked locally.
- Off-network usage queues locally and reconciles on reconnect.
One contract, several kinds of deployment
The same product often ships as SaaS, as a desktop install and into a customer’s data center. That can be one customer, on one contract. One entitlement carries all of it, with an activation flow for each.
See what Oclavex can do for your software
Tell us about your software and how you want to sell it. A person replies, and you can open a live demo while you wait.
Private preview. Short form, personal reply.