Skip to content
OclavexOclavex Docs

The solution

Oclavex lets a software vendor decide what a customer may use, enforce it inside their own application (online or offline), measure what they actually use, and feed that back into better plans and features — so entitlement management is, day to day, configuration rather than code.

The point isn’t any single feature; it’s the loop — Oclavex ties how you package your software to how it’s really used, and closes the gap between them.

The loop it closes

Section titled “The loop it closes”
Entitle model & grant License & enforce activate & validate Meter count usage & credits Analyze dashboard & reports Listen in-app feedback Improve repackage & reprice package it → see how it's used → package it better
  1. Entitle — model products and features, package them into plans, and grant them to customers as entitlements.
  2. License & enforce — issue and activate licenses, bind them to devices or users, and validate them at runtime (including air-gapped and offline). Your application asks “is this allowed?”; Oclavex answers.
  3. Meter — count what customers consume (API calls, seats, exports…) against quotas, and draw down prepaid credit balances for usage-based pricing. Oclavex tracks consumption and credit value; the charge itself stays with your billing provider (e.g. Stripe).
  4. Analyze — read the results on the dashboard: usage by plan and product, top consumers, the trial funnel and a world map of your customers, plus exportable usage reports.
  5. Listen — capture customer feedback as in-app feature ratings, and see features ranked by how users rate them.
  6. Improve — feed analytics and feedback back into packaging and roadmap: repackage plans, adjust limits, promote or retire features — then go round again.

How you work with it

Section titled “How you work with it”
  • The Provision Portal — model and run your catalog, and read the dashboard and feature rankings.
  • A REST API — the same capabilities, for automation and integration.
  • Client SDK — a convenience wrapper over the API for activating licenses, enforcing entitlements and reporting usage from inside your application.
  • Webhooks — outbound events when something changes.

Automate and connect

Section titled “Automate and connect”

Outbound webhooks and the Zapier integration (Enterprise) keep billing, CRM and operations in sync. A Salesforce connector (Enterprise) syncs accounts, contacts and orders in and projects license state back — see Integrations.

Oclavex owns entitlement and usage; your billing provider owns charging — they stay in sync through webhooks.

Compliance built in

Section titled “Compliance built in”

Because Oclavex is the single source of truth for what each customer is entitled to and what they actually use, license compliance comes built in. Expiring, expired, revoked, suspended and over-quota licenses surface on one dashboard, and the rules enforce themselves: a lapsed or over-used license stops granting access on its own, with every change recorded in an audit log. The same source of truth carries the privacy obligations on that data — data-subject requests and a register of processing activities are built in.

Section titled “Read next”