Skip to content
Oclavex is in private preview, available to selected users. Public signup is blocked. Request access at [email protected].

Release notes & support

The first public release of Oclavex. What it does:

  • The full licensing lifecycle — products and versions, a feature catalog, plans and plan sets, add-ons, entitlements and offers, node-locked and floating activation, metered usage with quotas and credits.
  • Admin portal for provisioning, catalog authoring, customer and user management, usage dashboards, and offline activation.
  • .NET SDK for license consumers: activation, session management, usage reporting, offline/air-gapped operation with signed receipts.
  • Outbound webhooks — signed, CloudEvents-formatted deliveries for entitlement, metered-usage, and privacy/data-subject-request lifecycle events, with subscriptions you manage yourself in the portal.
  • Feedback from your users — feature requests, problem reports and comments sent from your application, with the page and version they came from and an optional security label, read and answered in the portal’s Feedback inbox. Emailing the sender when you decide is a setting, off until you switch it on.
  • Privacy / GDPR — admin-filed data-subject requests executed across every data store.
  • Account isolation — your account’s data is never visible to other accounts.
  • Salesforce connector (Evaluation and Enterprise) — two-way sync: accounts, contacts and orders flow in via Change Data Capture; entitlement lifecycle state is projected back onto LicenseGrant__c records.
  • No end-user privacy endpoints by design (filing is an admin operation — see Privacy & DSR).

The public API is frozen at v1 and evolves additively — see API versioning for what that guarantees and what would constitute a breaking change. SDK packages follow semantic versioning.

For integration help, security reports, and licensing inquiries: [email protected]. In the admin portal, the feedback button in the app bar sends a feature request, a problem report or a comment straight to Oclavex. Security-sensitive reports are handled privately — please don’t file them in a public channel.