Identity Infrastructure Suite
Parta Tag
Any badge. Cryptographic access control.
Scroll
Access control
Badge reads.
Server forgets.
NTAG424 DNA. Onboard AES-128. Non-exportable keys. Dynamic CMAC per read. Every access event is an Ed25519 challenge/response cycle. No database of badge holders. No central revocation list. Revoke a key relationship, not a record.
Identity Tag / Identity IoT
Binding modes
STD or HS.
Your choice.
STD mode: the badge works on any authorised reader in your fleet. HS mode: the badge is cryptographically bound to a specific terminal. The DEK derivation incorporates a hash of the reader public key. Invalid on any other device. One provisioning step. Permanent binding.
Identity Tag / Parta Keys
Multi-tenant
Your fleet.
Your badges.
Each tenant has an isolated namespace. Its own reader fleet, badge registry, group tree, and entitlement table. A badge from Tenant A cannot be verified by a reader belonging to Tenant B. Isolation enforced at the cryptographic layer, not just the application layer.
Identity Tag / Identity HS
The app
Provisioning in your pocket.
This app manages both badges and IoT nodes. Request access below, or sign in at identity.parta.app.
Request access.
Cloud. NTAG424 DNA. 7-day trial.
Request received.
We will contact you within 2 business days.
Login for latest pricing · Enterprise: identity.aeonianengineering.com