DISCOVER · REVIEW · REMEDIATE
Editions

Pay for a campaign, or for an estate. Never for a feature.

Two editions run the same platform, with every capability, every policy and every connector. The difference is how you consume it, and whether the platform learns from one campaign to the next.

Consumption
OneShot

For a regulatory deadline, a first certification, or an audit finding to close. You buy credits, a campaign consumes them per decision.

  • All capabilities. Every console, every policy, every connector, RITA, sealed evidence, audit trail, BEACON, API.
  • Credits per decision. One credit envelope, consumed by the decisions your reviewers actually make.
  • Buy as you go. Credits by card or invoice, in lots that expire after two years, consumed first-in first-out.
  • A cabinet's price, a platform's proof. Compare it with a consultancy quote for the same review, not with a suite.
Side by side

What differs, and what never does.

Dimension
OneShotCredit packs
Story
“I run my annual review.”
“I govern continuously.”
Commercial model
Pricing axis
Decision volume (grid per campaign)
Governed identities (tiers)
Campaigns
Debited in credits per campaign, quote in the wizard before launch
Unlimited, included
Pack discount
Degressive by pack size
Campaign types
Scheduled
Yes
Yes
Periodic
Yes — one debit per occurrence
Yes
Continuous
No — at odds with the edition
Yes
Event-drivenNext
No
Yes
Credits & RITA
Role of credits
Primary currency
Extensions only (RITA, future consumers)
Credit validity
24 months, FIFO lots
24 months, FIFO lots
RITA allowance
Reduced tier carried by the subscription, active with ≥ 1 active campaign, not multiplied by campaigns
N questions per month, non-cumulative
RITA overage
Opt-in, capped by the customer, debited in credits
Opt-in, capped by the customer, debited in credits
Understanding & integration
INSIGHTS
Showcase only
Included — series, differential, findings
Workspaces
Yes
Yes — multiple, with delegated governance
BEACON SIEM
Pull export only
Push to your SIEM — Splunk, Sentinel, Elastic, S3
Public API
No (available on request)
Included — scoped clients, managed in the Subscription Manager
Limits, incidents & switching
Identity tier
Not applicable
Declared in the contract, observed as a guard-rail (soft enforcement)
Credits exhausted
Blocks new launches only, never a running campaign
Affects extensions only
REVIEWIT technical failure
Compensation in the ledger
Compensation in the ledger
Upgrade
Unlimited: remaining credits survive as credits
Functional restrictions
Full entitlement matrix
Full entitlement matrix
available not available not applicable Every capability, policy and connector ships in both editions.

Governed identities are weighted: disabled accounts and shared mailboxes do not count. Pricing is quoted per estate. Ask us for the grid. A non-commercial Trial exists for evaluation, driven by licence mode.

Buying

Credits by card, tiers by contract.

01

Card purchase

Credit lots can be bought by card from the Subscription Manager through a payment gateway. The platform holds no card data, ever.

02

Ledger, not a counter

Credits are lots with an expiry, consumed first-in first-out. Every consumption is a ledger line you can read per workspace.

03

Term and tier

An Unlimited tier applies for a term. A change of tier is decided during the term and applied at the start of the next one. No mid-term surprise.

Deployment

Managed in your region, or on your premises.

Managed service

Operated by REVIEWIT on a regional foundation with authentication and sealing authorities per region. Continuous updates, dormant posture when a subscription is idle.

On-premise

The same consoles, jobs, vault and sealing authority deployed inside your infrastructure, for sovereignty, regulatory or isolated-network requirements.

Get a quote on your estate.

Tell us how many identities you govern and which campaign you must run first. We will propose the edition, the tier or the credit lot, and the timeline.