Features

Oclavex covers the whole monetization job: model what you sell, grant it to customers, activate and enforce it inside your application, meter what’s used, and see the results. All but seven capabilities are included in every plan — those seven are tagged inline below and collected in What depends on your plan.

For prices, capacity limits and support tiers, see Oclavex Plans. For how the pieces fit together conceptually, see Building blocks.

Model what you sell


Products & versions	Define each product by code and version. Duplicate a product as a new version when the offering changes, and move versions through their lifecycle.
Feature catalog	Define each capability once, with a data type — `Boolean`, `Numeric`, `Text`, `Enumeration`, `Metered` or `JsonField` — and reuse it across every version in the product family. Entries move from draft to published to archived.
Product features	Set what a specific product version offers, feature by feature.
Plans & plan sets	Package features into tiers; each feature carries a value, a limit or quota tiers. Plan sets are versioned, so a new revision doesn’t disturb what’s already granted.
Suites	Sell several products as one subscription. A tier decides, product by product, what’s included — so a product in the suite can ship locked and unlock on an upgrade.
Add-ons	A named set of feature adjustments, scoped to a suite, granted on top of a customer’s existing plan. Add-ons are drafted, published and archived; editing a published add-on creates a draft copy so live grants aren’t affected.

Grant it to customers

Entitlements — the record of what one customer may use. Features are snapshotted at grant time, so later catalog edits don’t silently change a live customer.
Entitlement offers — turn a worked-out entitlement into a reusable definition and create new customers from it.
Activation codes — issue codes per entitlement with an expiry, an activation count, an optional required fingerprint, and a choice of whether redeeming one requires sign-in.
Key formats and batches — give codes a format of your own (a prefix, a running number, the issue date, a check character), cut them in batches for a campaign or reseller order, or import codes you generated elsewhere.
Subscriptions and renewals — see everything expiring before a date you choose, then renew a subscription, extend a license or restart a trial.
Plan change requests — customers ask to move plan; you approve or reject with a note, and approval applies the new plan immediately.
Operational actions — pause and resume an entitlement, enable or disable activation, revoke and reinstate, adjust seats, and apply a temporary plan override with an end date.

Choose a licensing model

One entitlement carries whichever policies you attach, so these combine rather than compete.

Model	What it gives you
Perpetual	No expiry — the default when no time-based policy is set.
Subscription	Renews on an interval you set, for a number of periods.
Trial	A time-boxed license, optionally starting on first activation, and optionally running on its own plan. Trials can be restarted.
Time-restricted	Valid only between a start and end timestamp, or for a fixed activation window.
Node-locked	Bound to a device fingerprint, with a matching strategy that decides how much of the machine may change before the binding breaks.
Floating	A pool of concurrent seats, allocated on activation and returned on release.
Leased	The license is valid for a lease period with a grace window on top, so the application keeps working between check-ins.

See Licensing models for how these map onto real offerings.

Activate and enforce

Activation — your application exchanges an activation code for a session and a signed license. A code can be redeemed on its own, or bound to a signed-in user or a machine identity.
Enforcement in your application — check entitlements and feature values against the signed license the .NET SDK holds locally, so a check doesn’t depend on a round trip.
Check-in and release — sessions check in to renew their lease and release the seat when the customer is done.
Offline and air-gapped activation — the customer exports a request file, you issue a signed response from the portal, and usage collected offline comes back as an archive you ingest and answer with a signed receipt. No connectivity needed on the customer’s side.
Activation records — every issued license is listed with its principal, fingerprint, status, lease and expiry, and can be released from the portal.

Meter usage, quotas and credits

(Professional and up)

Metered features — count what customers consume against the feature that represents it. Usage is reported from your application through the SDK and can be sent with an idempotency key so retries don’t double-count.
Quotas with tiers — set thresholds per plan and choose what happens at each one: notify only, allow with overage, allow within a grace amount, rate-limit, deny, or suspend.
Prepaid credit balances — draw usage down against a credit balance, top it up, and allow a negative balance where that’s what you sell.

See what’s happening

Dashboard — your licensing position on one screen: the entitlement mix, quota health, licenses that are expiring or at risk, and where your customers are.
Usage metrics — pick a metric and a period and see its total or average, peak, low, latest value and change against the previous period.
Usage report — filter by metric, period and date range, group by product, customer or plan, and export the result to CSV.
In-app feature ratings (Professional and up) — ask users to rate a feature from inside your application through the SDK, and see features ranked by how users rate them.

Serve your customers’ users

Organizations and users — a directory of your customers’ organizations and the people in them, with billing details, memberships and the activations belonging to each.
End-user portal (Professional and up) — a portal your customers’ own users sign in to, where they redeem an activation code and see the licenses assigned to them, with their usage, limits and included capabilities.
Self-service signup — new accounts sign up with an email address and a company name, confirm by email, and land on a working account.

Control who can do what

Roles — Administrator, Sales, Support and Viewer. The four roles are fixed; there’s no custom-role builder.
Role-based permissions (Professional and up) — without it, everyone with portal access is an Administrator.
External login providers — turn the available sign-in providers on or off for your account.
Administrator seats are capped by plan; the portal shows your current seat usage.

Build it into your application

.NET SDK — activation, entitlement checks, fingerprinting, offline handling and usage reporting.
REST API — the same capabilities for automation and for languages the SDK doesn’t cover.
API credentials — OAuth 2.0 clients, confidential with a secret or public with PKCE, with secret rotation from the portal. The number of clients is capped by plan; interactive sign-in clients need Basic or above (Free is machine-to-machine only).
Webhooks (Professional and up) — outbound events signed with HMAC-SHA256 and retried with backoff. Every attempt is listed and any event can be replayed; deliveries that ran out of retries can be retried or dismissed.
Connector credentials (Enterprise) — credentials for Zapier and other integrators, issued, rotated, disabled and revoked from the portal. A Salesforce connector is an early preview.

Run more than one environment

Sandbox — create a sandbox alongside production from Settings → Environments and try changes there first. Two non-production environments on Professional, five on Enterprise; each is a Sandbox or a Staging environment, and you can have several of either (Oclavex Plans).
Catalog transfer — export your catalog to a file and import it into another environment: products, feature definitions, monitored assets, plans, add-ons, entitlement offers and rating campaigns. Export whole sections, or a single item from its row — anything it depends on travels with it. Compare a file against an environment first to see, field by field, what it would change.

Meet your obligations

Audit log — every change, filterable by severity, source and date, with the identity that made it.
Data-subject requests — file and track access, portability and erasure requests. Access and portability produce a downloadable export; erasure anonymises the subject. Requests past the 30-day deadline are flagged for follow-up.
Processing activities — the record of processing activities required by GDPR Article 30, kept per service with its lawful basis, retention and recipients.

What depends on your plan

Everything above is in every plan except these eight.

Capability	Free	Basic	Professional	Enterprise
Role-based permissions (Sales, Support and Viewer roles)	—	—	✓	✓
Usage metering, quotas and prepaid credits	—	—	✓	✓
In-app feature ratings	—	—	✓	✓
Outbound webhooks	—	—	✓	✓
End-user portal	—	—	✓	✓
Interactive sign-in clients	—	✓	✓	✓
Anonymous try	—	✓	✓	✓
Connector credentials	—	—	—	✓

Capacity — products, licenses, entitlements, catalog features, administrator seats and API clients — scales with the plan too. Those numbers are on Oclavex Plans. Monthly API volume scales with the plan as well; those numbers are on the same page.

Your first 14 days

A new account starts on Basic with a 14-day trial that switches on the end-user portal, webhooks, usage metering, role-based permissions and in-app feature ratings, and raises the API client limit. Nothing to opt into and no card required.

When the trial ends the account carries on as Basic and those capabilities switch off. Your products, plans and entitlements are untouched; API clients above the Basic limit are deactivated until you upgrade.