A signing appliance that stores no keys.
Every time Roost powers on, its keys are regenerated from the chips themselves, and they vanish again when the power goes. It signs only when two of three chips from different manufacturers agree.
What is Roost?
Traditional HSMs guard keys inside a vault. Roost has no key to guard.
Roost draws its keys out of a silicon fingerprint (PUF) that differs from chip to chip, uses them, and lets them vanish at power-off. A separate monitor watches every request, and every record is bound into a hash chain. For approvals, only passkeys unlocked by a person enter the chain.
Explore
Everything that makes a signature trustworthy.
How it works
Three voters, one monitor and a chain of records. Read more
Hardware
Three chips from AMD, Lattice and Microchip in a sealed enclosure. Read more
Tamper response
Opened means erased, even with the power off. Read more
Management console
Keys, approvals, devices and records in one place. Read more
Management console
One console for keys, approvals, devices and records.
Each product has a tile with live counts. Every sensitive action waits in one approvals inbox for passkey seals. Every refusal says why.
See the consoleProducts
Why security teams trust it
Claims you can check, not promises.
Verifiable by anyone
Signatures meant for third parties are public-key signatures. Anyone with the public key verifies them, without trusting Axowl or the box. Internal seals are confirmed by the chips themselves.
No vendor door
Axowl holds no key, no PIN and no way to sign on your behalf. Nothing on a box changes without your owners' passkeys, and every such action is a sealed record.
No outbound connection
Roost runs on your network and never calls home. Air-gapped sites run on signed files alone.
Refuses by default
No quorum, no approval, a wrong purpose, a clock outside policy or an opened enclosure: Roost refuses, says why, and records it.
Replay cannot happen
Every seal includes a counter that only moves forward, so an old signature cannot be presented as a new one.
Secrets never in logs
Records carry who, what and when with correlation ids. Key material and credentials never appear in a log, a report or an error.
What Roost never does
Seven things that are not configurable.
- Never exports a private or secret key, in any format, to anyone.
- Never signs without two of three chips agreeing.
- Never signs a sensitive key's request without the approval the policy demands.
- Never offers a weak algorithm or an unauthenticated mode.
- Never writes a secret to a log, a report or an error message.
- Never opens an outbound connection on its own.
- Never gives Axowl a way in on its own: no master PIN, no support key, no unlock without your owners' passkeys.
Deployment
Where Roost runs.
In your rack
Roost runs inside your network with no outbound connection: your server room, your plant, your vault floor.
Air-gapped
A box that never talks to the server runs the same steps as files carried by USB or QR. Status, usage and enrollment all travel as signed files.
As a pair
Roost is sold in pairs. The second box holds pieces of the same keys, so a failed box is replaced without a service break and never repaired on site.
Cloud-managed or not
Manage boxes from the Axowl console, or keep everything on site. The box signs its own status reports either way.
Standards
Built to the requirements auditors ask about.
Roost is designed to the requirements of FIPS 140-3, KCMVP and the EU Cyber Resilience Act: a sealed sensing enclosure, erasure on intrusion, environmental monitoring, role separation, a tamper-evident record chain and signed status reports.
- Key material is never exported and never stored in plaintext
- Administrator, operator, auditor and AI agent roles are separated; auditors verify the chain themselves
- Every signature, refusal, approval and tamper event is a sealed record
- Evidence reports are produced by the appliance and signed for your auditors
See Roost refuse an unapproved signature.
A 30-minute live demo with our engineers.