Deployment Models & Data Tiers
Two independent choices shape how the IDV Platform runs for a Company: where it is hosted (deployment model) and how much data it keeps (data tier). Both use the same API, so integrations do not change when a choice changes.
Deployment models
| Model | Description | Best for |
|---|---|---|
| SaaS (Innovatrics-managed) | Hosted and operated by Innovatrics. No infrastructure to run; scales automatically. Upgraded to every new release by Innovatrics. | Fast time-to-market; teams that do not want to operate biometric infrastructure. |
| Self-hosted | Deployed on the Company's own infrastructure (on-premises or private cloud) from a versioned release package, in one automated step. Same product, same API, Company-managed operations and upgrade schedule. | Banking, telco, insurance, government — where data residency, sovereignty, or internal policy requires control over where personal data is processed. |
Both models are GDPR-compliant and expose an identical API surface.
Data tiers
The data tier determines whether verification data is kept after a session ends. It maps directly to the commercial model.
| Tier | What it does | Billing model |
|---|---|---|
| Session-based (no storage) | Runs the verification and returns the result. No Customer or Digital Identity records are kept; no images are retained beyond the session. | Priced per session. |
| Stored | Persists Customer and Digital Identity records, captured images, and audit history. Unlocks the back office, record management, and fraud tooling. | Priced per stored user. |
On top of the Stored tier, Companies can add:
| Add-on | What it adds |
|---|---|
| 1:N Biometric Identification | Facial duplicity check against watchlists — detect duplicate accounts, catch repeat fraudsters, recognize returning customers. Requires the Stored tier. |
| Palm verification | Palm enrolment during onboarding and 1:1 palm authentication as a second biometric modality — see Palm Verification. Requires the Stored tier. |
Both add-ons are enabled per tenant by Innovatrics as part of the plan; when an add-on is off, its workflow steps, Trust Factors and back-office tabs are not shown.
What each tier enables
| Capability | Session-based | Stored | Stored + 1:N |
|---|---|---|---|
| Document & face verification, liveness, fraud checks | ✅ | ✅ | ✅ |
| Result returned to the integrator | ✅ | ✅ | ✅ |
| Customer & Digital Identity records | — | ✅ | ✅ |
| Back office (review, CRM, audit) | — | ✅ | ✅ |
| Document duplicity check (name / DOB / number) | — | ✅ | ✅ |
| Palm enrolment & authentication (add-on) | — | ✅ | ✅ |
| Facial duplicity check & watchlists (1:N) | — | — | ✅ |
Usage reporting
Usage is metered by the Innovatrics Transaction Counting System in both deployment models — per session on the session-based tier, per stored record on the Stored tier. The reports contain operation counts only, never personal data; self-hosted deployments can choose a count-only or an offline mode. See Usage Reporting.
Data retention and GDPR
- Session-based keeps no personal data after the session — the lightest privacy footprint.
- Stored retains data for the lifetime of the Customer relationship; the Company controls erasure through anonymization.
- Transport is always encrypted; captured media is encrypted in transit and, on the Stored tier, at rest.
See also
- Digital Identity Lifecycle
- Duplicity check
- Administration → Data Storage
- What's New — release history and versioning