Skip to main content
Every plan runs the same engine: real-time document capture and real-time face biometrics with anti-spoofing. What changes is how many verifications you get, how long the data lives, and how much of the product you can shape — starting with whether you can call the API at all.

Basic

0.00 USD
  • 10 (monthly) · Number of verifications
  • Real time Biometric verification
  • Real time ID verification
  • 30 minutes · Customer link expiration time
  • 30 minutes · Customer data expiration time
  • Name only · Customization (Name - Logo - Color)
  • IP only · Customer location precision
  • SaaS · Hosting
Get started →

Premium

USD 49.99 / mo
  • 100 (monthly) · Number of verifications
  • Real time Biometric verification
  • Real time ID verification
  • 2 months (max) · Customer link expiration time
  • 1 week · Customer data expiration time
  • Full · Customization (Name - Logo - Color)
  • Yes · API access
  • Configurable · Customer location precision
  • SaaS · Hosting
Get started →

Pro

Custom
  • Whatever you need · Number of verifications
  • Real time Biometric verification
  • Real time ID verification
  • Custom · Customer link expiration time
  • Custom · Customer data expiration time
  • Full · Customization (Name - Logo - Color)
  • Yes · API access
  • Configurable · Customer location precision
  • Custom options · Hosting
Contact us! →

Side by side

API access is the dividing line. On Basic, POST /oauth/token answers 401 invalid_client with the message “User must have Premium or Pro plan”. Every page in this section assumes Premium or Pro.

Which plan fits

The verification counter

The counter is checked before a link is created, so a full quota stops the link, not the person mid-flow. When the quota is full, POST /links answers 409 with reason maxReached and no link is created. On Premium and Pro, a plan whose end date has passed answers 409 planExpired instead — a distinct case worth handling separately in your code.
Pro counts against the whole contracted period, not per month. A 12-month Pro contract for 12,000 verifications lets you spend them at any pace.

The two clocks

This is the part the pricing table cannot show. Each verification carries a single expiresAt, stamped once, when the verification is created. It is the sum of both settings:
Read those two rows of the pricing table as one sum. A Basic link is unusable after 30 minutes, but its verification data stays readable for 60 minutes from creation. A Premium account on the longest settings reaches 60 + 7 = 67 days.

When the window closes

Expiry governs access. You never wait for a cleanup job for the data to stop being served. Afterwards a daily job anonymizes the record: the personal fields become SHA-256 hashes and the images are deleted. From that point the verification answers 404, exactly as if it had never existed. The row itself is removed later, on a schedule that depends on your plan:

Branding

Downgrading resets branding at the source: the color returns to #666666, the logo is cleared, and both windows drop back to 30 minutes.

Customer location precision

Every verification records the precision of whatever location was available. The plan decides whether you may ask the customer’s browser for a precise one. The policy actually applied is recorded on each verification, so a result is always evidence of what the person was subjected to.

Beyond the table

Two behaviors are shaped by your plan even though the pricing grid does not list them.
Hand-off lets a session that started on a desktop continue on the customer’s phone. The mode — never, suggest or require — can only be changed on Premium and Pro. A Basic account keeps whatever mode it already had, read-only.
Adaptive flow lets a returning customer verify with a selfie instead of a second document scan. The previous verification qualifies only while it is successful, not anonymized, and still inside its own expiresAt.That makes the reuse window your data window. On Basic, a customer is only “returning” for 60 minutes, so adaptive flow is of little practical use there. On Premium at the longest settings the window reaches 67 days, and on Pro it is whatever VU configured.

Changing plan

Basic to Premium

Self-serve, from the Plans screen inside the app. It is a monthly subscription; your quota and windows apply from the moment the subscription starts.

Premium to Pro

Arranged with VU. Support provisions the account with your agreed quota, your link window, your data window, and the start and end dates of the contract.
What support can tune on Pro, in minutes rather than fixed options: the customer link expiration time, the customer data expiration time, the verification quota, and the contract window. Hosting is agreed separately — Pro is the only plan that can run somewhere other than the shared SaaS.
Upgrading from Basic or Premium to Pro carries your unused verifications across: they are added to the new quota rather than discarded.
In the API, the three plans are the values free, premium and commercial. The product calls them Basic, Premium and Pro — same three tiers, different vocabulary.

(*) The data will be kept as long as the contractual relationship exists or as long as the legal retention periods require it.
Last modified on August 30, 2026