Revenusion
The product

Your terms live in Oclavex. Your software asks.

Tiers, seats, quotas, credits, trials, add-ons, the special deal one customer negotiated: they live here as configuration. Your application asks whether something is allowed, and reports what is used.

Request early accessOpen a live demo

Private preview. Short form, personal reply.

Oclavex · Acme Robotics · terms

Try it — change a term

Plan
Seats
10
Advanced reports add-on

SavedEvery installed copy picks this up the next time it checks its license.

  • SaaS backend
    Plan
    Professional
    Seats
    10
    Advanced reports
    —
    License current
  • Desktop install
    Plan
    Professional
    Seats
    10
    Advanced reports
    —
    License current
  • Air-gapped device
    Plan
    Professional
    Seats
    10
    Advanced reports
    —
    Signed file current

The same version of the software on all three picks up the change by itself.

Where it fits

Between what you sell, what you ship and what you bill

Oclavex sits in the middle. Your commercial model goes in once. Your application gets a signed license and reports what is used. Billing, CRM and email get every change as a signed event.

What you sell

Grow how you sell

Ten steps, from one switched-on feature up to metered licensing tied to a person. Each one writes a line on the license, and says what it holds the customer to.

Read moreWho buys it

Grow who buys

Nine steps, from a try with no account up to revenue credited to the campaign that brought it. Each one lights a number on your dashboard.

Read moreWhat you ship

Put it in your software

Open-source SDKs and a public API. Your application asks whether something is allowed, and reports what is used.

Read moreWhat you bill

Your billing provider takes it from here

Renewals, expiring trials and usage over a limit reach billing, your CRM and your operations as signed events.

Read more
How it works

One loop, closed in one platform

Seven steps that follow each other round, so packaging keeps up with what customers do.

  1. Package & entitleProducts, features, plans, add-ons, suites, offers — granted to each customer as an entitlement.
  2. License & enforceSigned licenses the application verifies on the device — online or offline.
  3. MeterCount what each customer consumes against quotas, tiers and credits.
  4. AnalyzeActivations, usage and trial conversion.
  5. PromoteCampaigns with signup links, offers, plan overrides and add-on grants — every touch attributed.
  6. ListenIn-app feature ratings and feedback from the people who use it.
  7. ImproveRepackage plans, adjust limits, add or retire add-ons — new grants and renewals carry it.
  8. …and round again. Existing entitlements keep what was sold; new grants and renewals carry the new packaging.
Building blocks

Nine pieces, one line

You model products and features, put them into plans and grant them to customers as entitlements. A customer activates one, and you meter what they use.

  1. 01Products & versions — What you ship, and which release a grant applies to.
  2. 02Features & feature catalog — Boolean, Numeric, Text, Enumeration, Metered and JsonField — the capabilities a license grants.
  3. 03Plans & plan sets — Named bundles of features and limits. A plan set is the ladder a customer moves along.
  4. 04Entitlements & offers — The grant to one customer; an offer is a grant template you reuse.
  5. 05Activation & sessions — A device or user redeems the grant; a session holds the live license.
  6. 06Metering, quotas & credits — What consumption counts against, with tiers, policies and balances.
  7. 07Suites — Sell several products as one grant.
  8. 08Add-ons — Extra features on top of a plan, sold separately (what other platforms call bundles).
  9. 09Campaigns & attribution — A named, time-boxed promotion, with the sales it brought credited to it.
Two portals

One for your team, one for your customers’ users

You and your team

Provision Portal

Catalog, entitlements, activation codes, the dashboard, usage reports, the audit log and GDPR tooling. Roles: Administrator, Sales, Support, Viewer.

In the docs
Your customers’ users

End-user portal

Redeem a code, see the licenses they hold, live usage and credit balances. Served at your tenant’s address. Professional and above.

In the docs

Portal screenshots with example data arrive with the public release. The mocks use the same layout and real field names.

Integrations

Events out, changes in

Your billing provider charges cards and sends invoices. Oclavex tells it, your CRM and your operations exactly what happened, signed, and takes changes back.

  • Webhooks

    CloudEvents envelope, HMAC-SHA256 signatures, retries with backoff, replay.

  • Zapier

    Route events into the tools your team already runs. Professional and Enterprise plans.

  • Stripe

    A documented relay pattern: entitlement events in, subscription state out.

  • REST API v1

    One versioned path, OAuth 2.0 client credentials, additive evolution.

Security

Built so every secret stays on the server

Every claim below is architecture you can check.

  • RSA-signed JWT licenses; the device holds the public key, the private key stays on the server
  • Activation is anonymous or authenticated by the license token, and every API secret stays server-side
  • Encrypted on-disk license cache
  • Live signing-key rotation: publish, pin both, promote, retire
  • HMAC-SHA256 signed webhooks with a rotation overlap window
  • Audit log of every change in the portal and the API
  • GDPR data-subject-request tooling and an Article 30 register
  • Data processing agreement on request; you are the controller, Oclavex the processor
  • Hosted service by default; self-hosted or dedicated deployment on request

Sandbox and Staging environments on Professional (2) and Enterprise (5). Catalog export, compare and import are API calls, so promotion runs in your CI/CD.

Credentials & secrets Legal & data residency
Good to know

Before you ask

Who bills my customers?

Your billing provider charges cards, sends invoices and follows up on failed payments. Oclavex handles licensing, entitlements and usage metering. Webhooks, Zapier (Professional and Enterprise) and the Stripe pattern keep the two in sync.

How does Oclavex bind a license to hardware?

With a device fingerprint, or with a YubiKey. A YubiKey keeps its key inside the chip, so the license travels with the key from one computer to the next. Hardware keys are in Evaluation, Professional and Enterprise.

Which languages can integrate?

The primary SDK is .NET (netstandard2.0: .NET Framework, .NET 8+, MAUI, Unity). A C/C++ library covers native applications. The REST API covers every language with an HTTP client and a JWT library.

How does a license move to a new machine?

A support action in the portal. The old seat frees when its lease runs out, and re-activation on the new device issues a fresh signed license.

See what Oclavex can do for your software

Tell us about your software and how you want to sell it. A person replies, and you can open a live demo while you wait.

Request early accessOpen a live demo

Private preview. Short form, personal reply.