No keys.
Nothing to steal.
Roost is a hardware security module that signs only what was approved. Three chips from three manufacturers must agree, and the root key is never stored anywhere.
Why Roost
Built so that a stolen box, a rogue server or a single bad chip cannot sign for you.
No approval, no signature
Sensitive keys sign only when the request carries a passkey approval from the right people, bound to the exact content.
Nothing to steal
Each chip rebuilds its root from its own physical fingerprint at power-up. Keys exist only as pieces that are useless outside their chip.
Two of three must agree
Every signature needs two chips from different manufacturers to agree. One compromised or failed chip cannot sign alone.
AI agents, governed
Agents get their own identity, short-lived credentials, usage limits and human approval for risky actions. Every action is recorded.
In practice
Your build server is compromised. Your code signing key is still safe.
A conventional HSM protects the key but signs whatever an authenticated server sends. Roost checks who approved the release before it signs.
Use cases
One box for the keys that matter most.
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.
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.
Developers
Standard interfaces. Nothing heavy to install.
Use Roost from Java, from any PKCS#11 client, or with a plain HTTPS call. Try everything first on the simulator, which runs the same policy code as the device.
// Java: sign through Roost
var provider = new RoostProvider(gateway);
var sig = Signature.getInstance(
RoostProvider.ALGORITHM, provider);
sig.initSign(provider.signingKey("release-ledger"));
sig.update(message);
byte[] receipt = sig.sign();
Compare
Roost and a conventional HSM
| Conventional HSM | Roost | |
|---|---|---|
| Before signing | Checks that the client is logged in | Checks who approved this exact content |
| Root key | Stored in protected memory | Rebuilt from the chip's physical fingerprint, never stored |
| Who signs | One device | 2 of 3 chips from different manufacturers |
| Backup domain | A domain secret carried by people | Pieces held by chips, shared only with multi-person approval |
| AI agents | Use an application's credentials | Own identity, limits and approvals |
| Audit evidence | Logs you export and assemble | Sealed records and signed reports, ready for auditors |
See Roost refuse an unapproved signature.
A 30-minute live demo with our engineers.