A SaaS product
Your backend holds the license; end users never see codes. Each customer has one entitlement, with seats for their users and meters for what they consume.
Oclavex
Your time and creativity should go into your software —
not the monetization systems that package, license and meter it.
not the monetization systems that package, license and meter it.
You built software your current and future customers love, and now you want to charge for it. Charging for software is a job of its own: issuing licenses, enforcing them in your application, and counting what customers use — all according to the terms each customer licensed.
Getting that job wrong costs real money. A license lapses and nobody notices; usage drifts past what was sold and nobody bills it. What leaks is the income that should be funding new development and a healthy, sustainable business.
Oclavex does that job. You decide what each customer may use; your app enforces it, online or offline; you meter what they consume. A built-in dashboard and in-app customer feedback show you how your packaging is received. Outbound webhooks, a Zapier integration (Enterprise) and a two-way Salesforce connector keep billing, CRM and operations in sync.
Start from what you ship
Section titled “Start from what you ship”Every kind of product runs on the same building blocks. These pages show how the pieces map to yours, point to the demo that runs it live, and end at the right first step.
A desktop application
Sold perpetual or by subscription, activated with a code, locked to the machine, and expected to keep working on a plane.
On-premises & air-gapped software
The license is a signed artifact the software verifies by itself. Connectivity decides only how the artifact travels: over the network, or on a USB stick.
Connected devices
Each device activates itself against its own entitlement, keyed to a hardware fingerprint. No user logs in; the device is the licensee.
Why Oclavex — four jobs the platform does
Section titled “Why Oclavex — four jobs the platform does”Each of these jobs needs infrastructure, security and regulatory upkeep that never stops. Oclavex runs them once, for every vendor on the platform, so you pay a fraction of what carrying them alone would cost.
License management, end to end
Issue, activate, renew, suspend and revoke licenses from one source of truth — no spreadsheets, no hand-cut license files. Enforcement is automatic: a lapsed or over-quota license stops granting access on its own, and every change lands in the audit log. What customers use is what they paid for — no reconciliation afterwards.
Learning what customers want
Oclavex tells you what’s working: usage metering, in-app rating campaigns, and customer feedback collected right where people use the product. Packaging and pricing decisions then follow what customers do, not guesswork.
Staying available day and night
Your paying customers should never be locked out by a license check, so Oclavex keeps that path open: signed licenses validate on the device, offline and air-gapped installs run with no network at all, and keeping the service up is Oclavex’s job, not yours — backups, secret rotation and the GDPR paperwork included.
Replacing the system you outgrew
Already built something? You don’t have to keep it. The whole back office is scriptable — catalog, entitlements and activation codes sit behind one REST API — so switching is a migration script, not a project. Even the codes you issued elsewhere carry over: import them, preview what a run would change first, and they keep working exactly as issued.
Fits the way you already build
Section titled “Fits the way you already build”Your catalog is part of your product, so it moves the way your code does. Try a change in a sandbox. When it looks right, promote it to production.
Promotion is API-first: export, compare and import are all API calls, so it can run in the same CI/CD pipeline that ships your releases — with no manual steps. The API sits under a single versioned path where new fields and endpoints are additive, so the pipeline you wire up today still works next year.
Run more than one environment →
Built for how software sells now
Section titled “Built for how software sells now”The established licensing suites were built for software that was sold once and installed on a known machine; with most of them, prices are not published — you book a sales call to learn one. Oclavex starts free and self-serve, and every plan includes offline activation, node-locking, the audit log and GDPR tooling.
The same engine carries a startup on the free plan and an enterprise running fifty products; plans change how much you can run and which features are switched on.
The full case for Oclavex → · Oclavex Plans →
Pick your path
Section titled “Pick your path”I run the business side
You’re an administrator or product owner. Define products, features, plans and entitlements, then run them day to day from the portal.
I integrate the SDK / API
You’re a developer. Activate licenses, enforce entitlements and report usage from your app, via a client SDK or the REST API.
I’m deciding whether to adopt
You’re comparing options. Read the case for Oclavex: what changed in how software sells, where it wins, and where the established suites still do.
I review security and compliance
You’re answering security and privacy questions: how credentials and webhook secrets are issued and rotated, how data-subject requests are handled, where data lives, and how the API evolves.