Oclavex comes in four plans. Every plan includes the core licensing engine; what
changes between plans is how much you can run (products, licenses, API volume) and
which growth features are switched on. Prices are published on the Revenusion
website (the company behind Oclavex).
The monthly volume above is the allowance. These are the rates a burst is held to — each
returns 429 when exceeded, rather than counting against the month.
Capacity limits — products, licenses, entitlements, administrators, features and
environments — are hard caps. When you reach one, the platform refuses new additions
until you move to a higher plan; everything already live keeps working.
API calls are metered per calendar month. Past your plan’s included volume, the
month’s overage band is rate-limited rather than cut off (Free up to 20,000, Basic
to 100,000, Professional to 1M, Enterprise to 10M), so going over the monthly allowance
degrades gracefully instead of failing.
Request pacing is separate from the monthly allowance. The per-minute rate, the
burst and the daily ceiling in the table above are refused with 429 when exceeded,
whatever the month’s balance — a spike inside your allowance is still paced.
Meter at the granularity your product needs. Reporting consumption is built to be
cheap, and the allowances above are sized so you can meter at the granularity your
product works at — no pre-aggregating or sampling to stay under a ceiling.
Active licenses on the paid plans have an overage band above the included count —
to 200 on Basic, 2,000 on Professional, 20,000 on Enterprise. Activations keep working
through it, you’re warned, and the excess accrues at 0.01
credits per active license.
Above that band new activations are suspended (500 / 5,000 / 50,000). Free has no
overage band: it stops at its 25-license cap.
API client credentials are available on every plan so you can call your own admin
API with a client_credentials service credential instead of sharing an admin
password. On Free that client is machine-to-machine only — interactive
authorization-code and public clients need Basic or above.
New accounts start on Basic automatically, with the 14-day trial above. Upgrading
is just applying a higher plan — no migration, no downtime.
Community(Free and Basic) — start with the documentation, then ask in
public GitHub Discussions and file bugs or requests as GitHub issues (the client
SDKs are open-source). The team and other developers help on a best-effort basis — no
response-time guarantee.
Standard(Professional) — direct email support during business hours, with a
target first response within one business day.
Premium(Enterprise) — priority email plus a shared Slack or Teams channel
and a named contact, with a same-business-day first response and a custom SLA
available.