ToughKey in your hand. Managed Enrolment beside it.
ToughKey is the physical key. Managed Enrolment is the software that sits with it. PrimiDS keeps the root cryptographic secret in that key rather than in a cloud-recoverable credential. Recovery, permissions, and audit run as live systems.
ToughKey and Managed Enrolment, one system
ToughKey holds the root cryptographic secret in hardware — the physical key you keep in hand. Managed Enrolment, also called ToughBox in public materials, is the software layer that works beside it. PrimiDS is the platform both components sit on, designed as a single system rather than separate products. ToughKey is powered by LokBlok technology; that ingredient relationship does not transfer LokBlok certifications to Primi. The pairing of hardware custody and managed software is the PrimiDS product: the key anchors the custody model, and the software manages enrolment, permissions, and audit. Early access is via the waitlist.
physical key
software platform
The root secret stays in the key you hold
The sequence starts with enrolment: ToughKey is registered to you through Managed Enrolment and paired with your approved devices. Once enrolled, you use PrimiDS for encrypted storage and secure communications, with the root cryptographic secret anchored in ToughKey rather than in a cloud-recoverable credential. That custody model means the cloud does not hold the root secret; recovery, permissions and audit are handled as live system functions. Managed Enrolment coordinates the enrolment steps, the permission changes, and the audit trail, while ToughKey remains the hardware anchor you hold. This is the same custody model across the product: the physical key stays with you, and the operations that depend on it are explicit and recorded. The key you hold is the root of the model, so possession of a password or a laptop is not enough to open what the key protects. Key generation, sharing, supported devices and the rest of the product flow continue to be refined as early access opens, and the detail may change before final release.
The cloud does not hold the root secret
Hardware-backed key custody anchors the root cryptographic secret in ToughKey, which reduces reliance on a credential recoverable from the cloud. Encrypted storage on PrimiDS uses that key-bound secret to protect files and data at rest, and secure communications apply the same custody model to sensitive messages. It does not make the system offline, and it does not protect against endpoint compromise, phishing, user error or implementation defects. The design boundary is explicit: encrypted storage and secure communications are the designed scope, while protocols, endpoints, and supported devices are refined as early access opens. Compare key-custody approaches or review the security and assurance boundaries.
ToughKey is not a passkey
- HSM
- An HSM is a hardware security module — here it describes ToughKey’s role in holding a root cryptographic secret, not a certification.
- Authentication key or passkey
- An authentication key or passkey proves sign-in identity; ToughKey is neither. Passkeys and cloud-recoverable credentials can be convenient for account sign-in, but they are not designed to replace hardware custody of a root secret.
- ToughKey
- ToughKey is the physical key paired with Managed Enrolment on PrimiDS.
The glossary terms above clarify what ToughKey is and is not; they are not an offer to purchase or deploy today.
Designed for storage and communications
PrimiDS is designed for encrypted storage and secure communications — protecting files, documents and sensitive messages under ToughKey custody rather than a cloud-recoverable root credential. Use cases include personal document protection, business file handling and brokerage transaction files. Protocols, device and operating-system support, and integrations are refined as early access opens. Communications features, wallet signing and third-party integrations are described for a later release. The scope is storage and communications; it is not a wallet product or a general file platform. For the commercial picture, see hardware and subscription terms.
Design is not proof
Evidence status
An architecture describes what a system is meant to do. It does not prove the final implementation, an independent security review, or a certification. Primi is not currently FIPS 140-2/140-3 or Common Criteria certified, and publishing a design diagram does not transfer LokBlok ingredient credentials to Primi either. This page explains intent; it is not evidence that every described control is built, tested or operating in production. A finished product would still need its own implementation review and assurance work. Questions about testing, provider access, hosting and residual risk belong on Security & Trust.
Recovery is in the live system
A physical key can be lost, damaged, or stolen. Recovery, permissions and audit are part of the live PrimiDS system: a lost key is revoked, authority is verified, a replacement is enrolled through Managed Enrolment, and legitimate access is restored and recorded. Supported devices and the rest of the product flow continue to be refined as early access opens. Read the PrimiDS and ToughKey definitions, or send a security question if the published material does not answer yours.
See it in the work you already do
Choose the route that matches your context. Individuals — protecting important documents under ToughKey custody. Small businesses — sensitive files and communications for teams. Real-estate brokerages — transaction files and the reseller route.
Join the waitlist. Recovery is already in the system.
PrimiDS is in early access. Join the waitlist for updates and an invitation as access opens.