Skip to content
Identiwise is in final development. Public launch planned for January 2027 — nothing on this site can be purchased yet.

Simple plans. Launching January 2027.

The pricing below is indicative. Join the waitlist and we will tell you when accounts open.

Core

For a first integration and low verification volume.

$79 /mo

Indicative — final pricing at launch

Join the waitlist
  • Monthly API request quota
  • Hosted verification UI with camera capture and desktop-to-phone QR hand-off
  • Admin console: review queue, submissions, subject messages
  • Capability-scoped ephemeral tokens per subject
  • Reusable token presets and multi-step workflows
  • Strict assurance flow — require a face match before approval
  • Two-factor authentication (TOTP) for staff
  • Hosted in Frankfurt, Germany — data stays in the EU
  • Email support
COMING SOON

Pro

For platforms running verification in production.

$349 /mo

Indicative — final pricing at launch

Join the waitlist
  • Everything in Core
  • Higher monthly API request quota
  • Per-tenant IP allow-list (IPv4 and CIDR)
  • Raw data export (JSON or CSV) for superusers

Enterprise

For higher volume and teams with a formal review process.

Custom

Indicative — final pricing at launch

Contact us
  • Everything in Pro
  • Custom monthly API request quota
  • Volume pricing — contact us to discuss
  • Security review support: questionnaires and an architecture walkthrough
  • Data processing agreement reviewed with your legal team
  • Additional document types and regions (roadmap)

Each plan will include a monthly API request allowance; the figures will be confirmed at launch. There is no overage billing — requests above the allowance are refused with an HTTP 429 response until the next monthly period begins or you move to a larger plan.

Prices are in USD, per tenant, per month. The plan contents above describe what each plan is intended to include at launch. Today the platform enforces exactly three plan-level settings: the monthly API request quota, the per-tenant IP allow-list and the flag that gates the raw data export. Plans are indicative and may change before launch; nothing is on sale and no payment can be taken today.

Included on every plan

Security and data-protection properties of the platform, not upsells.

Access control

Three staff roles (superuser, admin, view-only) checked at the router; TOTP two-factor authentication with recovery codes, which a tenant can enforce for all staff; per-user 2FA lockout and per-IP login rate limiting; a password policy on every human-chosen password.

Tenant isolation

Each tenant is assigned to one of several database shards in the EU. Tenant scoping is enforced in every query and mechanically linted in CI. Database identities are least-privilege.

Image handling

Documents and selfies are stored in private, S3-compatible object storage. Files are never served publicly; administrators receive 15-minute pre-signed URLs, and every view is recorded.

Audit trail

An append-only audit log records document views, raw exports, review decisions, erasures, logins, authorisation refusals, 2FA changes, token issuance, role and staff changes, password changes and subject record changes.

Subject rights

Administrators can lodge an erasure request on a subject's behalf, and the API exposes a subject-side erasure route your own client can call; an erasure removes the stored images and the rows together. Subjects can view and correct their own details in the hosted UI when the token allows it.

EU processing

All hosting and processing runs on IONOS Cloud in Frankfurt, Germany, and sub-processors are EU-based. Identiwise acts as processor; you remain the controller.

Frequently Asked Questions

Plans will be monthly subscriptions priced in USD. Billing will be handled by a third-party payment provider acting as Merchant of Record; the provider's name, its buyer terms and its tax handling will be published before launch. Each plan includes a monthly API request allowance; when it is exhausted, further requests are refused with an HTTP 429 response until the next period begins or you move to a larger plan. There is no overage billing. Nothing is billed today.

All hosting and processing runs on IONOS Cloud in Frankfurt, Germany, and sub-processors are EU-based. Identiwise acts as a processor and the customer remains the controller. Documents and selfies are held in private object storage and are never served publicly. See the Privacy Policy for the detail.

Your backend creates a subject and mints a short-lived, capability-scoped ephemeral token. The subject submits a document and a selfie — through the hosted verification UI or your own client — and the checks run synchronously, so the result comes back in the HTTP response: document detection (a custom-trained document-detection model, today trained on US Texas driver's licences), face detection and matching against an approved reference image where one is on file (the response states which assurance level an approval carries, and a token can require a face match before approval), OCR scored against the details the subject gave you, and optional age estimation. The outcome is auto-approved, pending admin review with a stated reason, or rejected. There are no webhooks: read results from the response, or poll the review and submissions endpoints. The documentation has the full contract.

There is nothing to cancel yet — no subscription can be started today. Once Identiwise is live, a monthly plan will be cancellable at any time from the account portal and access will continue to the end of the period you have paid for. The draft Refund Policy sets out the intended terms; they will be finalised before any account can be opened.