Verify the right citizen. Where connectivity does not reach.
Cryptographic proof of citizen identity and authorization for regulated public-sector actions. Produced fully offline, on-device, at the field point of service. Portable to the central system when connectivity returns. No biometric transmission. No cloud dependency in the authorization path.
Legacy identity programs assume connectivity. They fail at exactly the points where identity assurance matters most. Border posts with intermittent links. Field health and humanitarian operations. Remote benefit disbursement. Disaster zones. Rural customs. Conditional cash-transfer program delivery.
Cloud-only authentication is not a technical preference. It is a capability gap that forces offline workflows to fall back on manual processes, paper receipts, and post-hoc reconciliation that no regulator would accept for sensitive actions in a connected context.
The political and regulatory surface is also moving. European eIDAS 2.0 and national wallet programs are pushing toward citizen-held cryptographic identity. The question for a national authority is no longer whether citizen-side hardware-bound identity is coming. The question is whether the authority produces the infrastructure or inherits an imposed one.
Identity proved in the field. Verifiable anywhere. Portable to the central system.
Yuthent verifies the right citizen end-to-end on the device held by the field officer or by the citizen. The result is a cryptographically non-repudiable proof, signed by a hardware-bound key, that can be verified against a published public key by the central authority, by a regulator, or by a court, regardless of whether the verifier is online at the moment of verification.
No biometric material leaves the device. Matching, liveness, and signing all execute locally in the device secure element. The proof carries a hash of the biometric binding, never the biometric itself. The authority receives evidence, not raw citizen data.
In-person and remote link-enrollment flows enable supervised device issuance, family re-linking, humanitarian registration, and the full range of workflows where a trusted operator must co-sign the citizen's initial enrollment. Every grant is time-boxed, scoped, signed, and revocable from the control plane.
Field capabilities shipped in the SDK today.
Fully offline enrollment and signing
No network required for enrollment, biometric verification, or action signing. Proofs hold in a durable on-device queue. Central system reconciliation occurs on sync, not in the critical path.
In-person link enrollment
A supervised operator with a provisioning tablet can issue a time-boxed, signed grant to a citizen's personal device, in the field, with cryptographic evidence of the operator's identity and the issuance moment.
Remote video link enrollment
For distributed populations where in-person is impractical, a video-remote link-enrollment grant flow produces the same cryptographic evidence, with the operator's video identity verification step signed into the grant.
Portable, verifier-agnostic proofs
Each action produces a signed proof verifiable against the authority's published public key. A regulator, auditor, or partnering ministry can verify without a live connection to Yuthent, against the canonical bytes of the original signing.
Privacy-preserving biometric binding
Face, liveness, and identity-document extraction execute on-device. Biometric data is never transmitted. The proof carries a hash anchored to the citizen's enrollment, not the raw biometric.
Sovereign-hosted control plane
The control plane and audit-export pipeline can deploy into a sovereign cloud or a ministry-operated environment. BigQuery export lands in a ministry-owned storage bucket with ministry-held keys.
The evidence each framework demands.
Border and customs
Intermittent-network verification with audit-grade cryptographic evidence that travels back to central on reconnection. Offline evidence floor matches online evidence floor.
Humanitarian and field operations
Citizen verification and authorization in disaster zones, remote clinics, and refugee registration. Supervised link-enrollment grants enable operator-accountable field onboarding.
Regulated benefit disbursement
Conditional cash-transfer programs and field benefit delivery with non-repudiable proof of receipt at the point of delivery, portable back to the central reconciliation system.
National ID re-verification and wallet alignment
Low-connectivity regional re-verification with central reconciliation on sync. Architecture aligned with the direction of citizen-held hardware-bound identity under eIDAS 2.0 and comparable national frameworks.
Yuthent does not replace a national ID registry. It is the field-edge authorization and evidence layer that the registry does not produce today. Integration is a signed service contract with the central system, with BigQuery or sovereign-cloud export for audit.
A first engagement typically scopes one field workflow: border verification, benefit disbursement, or humanitarian registration. Android is the primary deployment target given the field handheld fleet. iOS parity available.
Start an enterprise pilot.
Tell us the flow you want to protect. We will come back with a working integration proposal. Founder reads every request. First call within five business days.