Why Oclavex

The established licensing platforms were built thirty years ago to answer a question most vendors no longer lead with: how do we stop someone copying a perpetual license onto a second machine?

Those platforms answered it with hardware keys, licenses locked to a single machine, license servers inside the customer’s network, and yearly audits. All of that assumes software is sold once, installed on one known machine, and settled once a year. The established suites still carry those assumptions — and they are what vendors find frustrating today.

The question that matters now is different: is the software being used according to the terms each customer licensed? Enforcing modern terms — tiers, seats, metered quotas, credits — is a different job from stopping copies.

What changed

Pricing has become more dynamic. Seats and perpetual licenses didn’t disappear, but consumption, credits and tiered usage now sit alongside them — measured in events per minute, not licenses per year.
AI products sell usage directly. When what you sell is tokens, runs or agent actions, metering is the commercial model, not a reporting feature.
One product ships in many forms. The same product now ships as SaaS, as a desktop install, into a customer’s datacentre, and onto devices with no route to the internet — often for the same customer in the same contract.
Buyers expect to try the product first. Developers evaluate infrastructure by using it — not through sales calls and procurement cycles.

A platform designed around annual reconciliation can be extended to cover this. Being designed for it from the start is a different thing.

What Oclavex does differently

You can start without talking to anyone

Starting is free and you onboard yourself. No demo call before you can see the product, no scoping engagement before your first license is issued, no quote that arrives days later and differs from the one another buyer received. Plans, limits and what’s in each tier are written down on a page you can read right now.

When you do outgrow a tier, capacity limits refuse new additions rather than breaking what’s already live, and API volume is rate-limited past your plan’s allowance rather than cut off — a spike degrades, it doesn’t fail.

Meter at the granularity your product needs

Usage reporting is built to be cheap: ingestion is batched and compressed on its way to storage, so volume isn’t the expensive part — and the plan allowances reflect that.

That matters because when your pricing is usage-based, a platform that charges heavily for usage events penalizes the thing your business runs on. You shouldn’t have to pre-aggregate or sample your own telemetry to stay under someone’s ceiling.

The must-have capabilities are in every plan

This is the one to check against any alternative you’re evaluating. In every Oclavex plan — including the free one — you get:

Offline and air-gapped activation with signed-license validation
Device fingerprinting, node-locking and floating licenses
Trials, add-ons and entitlement offers
The Provision Portal, with its dashboard and reports
The REST API and .NET client SDK, with at least one API client credential
The audit log, email notifications and GDPR data-subject tooling

Offline activation and a complete audit trail are the capabilities regulated and enterprise buyers can’t proceed without. Holding them back for a higher tier would mean charging most for the thing that decides whether you can ship at all, so Oclavex does not.

Licensing, metering and analytics in one platform

Licensing tells you what a customer is allowed to do, not what that customer actually did. To see both, licensing, metering and analytics have to share one source of truth for each customer.

Oclavex closes the loop in one platform: entitlements and enforcement, usage metering with credit balances, an analytics dashboard, in-app feature ratings, and outbound webhooks and connectors to carry the result into billing and CRM.

You can be running today

Four complete applications are live and clickable right now — Mirage (metered SaaS), Overdrive (connected cars, offline licensing), Atelier (desktop seats and modules) and Bastion (air-gapped, licensed entirely by file). Not screenshots or a guided tour: working software exercising the same platform you’d be buying.

From there the quickstart issues a real license against your own product. Integration is a client SDK or the REST API, authenticated with standard OAuth 2.0 / OIDC — no proprietary auth scheme to learn, and separate Sandbox and Staging environments, on the plans that include them, so you can test without touching live customers.

Oclavex runs on Oclavex

Your Oclavex account is itself licensed by Oclavex. The 14-day trial, the plan limits and the upgrade prompts you meet in the portal are the same entitlement engine you would ship, enforcing Oclavex’s own catalog exactly as it will enforce yours — through the same public admin and provisioning API you integrate against. Evaluating the portal is already watching the product work.

Where the established platforms still win

Decades of accumulated edge cases. Thirty years of shipping into every licensing situation imaginable leaves a depth of handled corner cases that a newer platform hasn’t encountered yet.
Hardware keys. If your model depends on physical dongles, the established vendors support them; Oclavex does not.
Breadth beyond licensing. Several established vendors sell licensing as one module of a much wider software asset management and compliance suite. If you need the rest of that suite, buying it together is a legitimate reason to choose it.
Procurement familiarity. In large organisations, a vendor your legal and security teams have already approved carries real weight. That’s not a technical argument, but it’s a real one.
SDK language coverage. The primary client SDK is .NET, with the REST API available to everything else. If you need a deeply idiomatic SDK in another language today, check Develop before committing.

Oclavex is the right choice when your pricing is moving toward usage, when you ship to more than one kind of deployment, and when you’d rather evaluate infrastructure by running it than by scheduling a call. When those aren’t your constraints, the older platforms are there for good reasons.