Skip to content
OclavexOclavex Docs

The need

You decide the terms your software is sold on: which features each tier includes, how many seats a customer gets, how long a trial runs, how much usage is allowed per month, which add-ons can be bought, and the special deal one customer negotiated. Your software has to follow those terms for every customer, from the day the agreement starts to the day it ends, counting what the customer uses along the way. Entitlement management is that job. The goal is that the software is used according to the terms each customer licensed.

What entitlement management means

Section titled “What entitlement management means”
  • Plans that change without a software release. Plans and prices change far more often than your codebase should. Which features and limits each tier includes has to live in configuration, so a new tier can go on sale without waiting for a release.
  • Licenses that work offline. Desktop, embedded and air-gapped software can’t contact the licensing service on every launch. Licenses have to be signed, validate without a network, and still be renewable and revocable.
  • Accurate usage limits. Consumption has to be counted correctly, quotas enforced, and prepaid credits and overages settled across the whole customer base.
  • Device and seat enforcement. A license has to bind to a machine or a user, with activations tracked across devices, so seats and installs stay within what the customer licensed.
  • The signals your business runs on. Renewals coming due, trials expiring, customers in overage — these have to reach billing, CRM and email reliably.

When all five are met, the terms you decided are the terms your customers get: a new tier goes on sale without a release, licenses keep working offline, usage is counted and settled without anyone reconciling it afterwards, and renewals reach billing before they come due. Oclavex meets all five. The solution shows how.

Section titled “Read next”