How it works
Oclavex sits between three things you already have: your commercial model (what you sell), your application (what you ship), and your back-office systems (billing, CRM, email). It turns your commercial model into rules your application can enforce, and emits the events your back office needs.
How an integration fits together
Section titled “How an integration fits together”- You model your offering — in the Provision Portal (or via the API), you define products and features, package them into plans, and grant them to customers as entitlements.
- Your application asks and reports — through a client SDK or the REST API directly, your app activates a license, checks entitlements at runtime, and records usage.
- Oclavex enforces and measures — it validates licenses (online or offline), evaluates entitlements, and counts usage against quotas and balances.
- Your other systems stay in sync — Oclavex emits webhook events (activated, renewal due, trial expiring, limit crossed) that you route to billing, CRM or automation tools.
What runs where
Section titled “What runs where”- Your application and your customers’ devices run a client SDK or call the API — including fully offline: the license itself is a signed license token the device verifies locally, so it validates without a network.
- Oclavex holds the catalog, entitlements, licenses and usage, and exposes one secured API plus the Provision Portal.
- Your back office receives webhooks — Zapier and other tools are reachable the same way. A Salesforce connector (Enterprise) syncs CRM accounts and orders in and writes entitlement state back to CRM records.