ROOSTby Axowl

Docs

Roost documentation

Roost is a signing appliance with three voting chips from three manufacturers and a monitor. Applications reach it through a gateway; organizations manage their boxes in the Axowl console and through the API below.

Everything in these docs runs on the simulator as well as on the appliance, with the same policy code. The wire protocol, the receipt format and the error reasons are published here so that you can verify Roost's behaviour yourself.

The console at a glance

axowl.com/dashboard/acme/roost
AxowlacmeRoostM

Products

Code signing12 signed today · 1 awaiting approval
Documents38 signed today
Certificate authority2 issued this week
Data encryption1,204 unwraps today
TLS keys3 keys · pair OK
AI agents4 agents · 2 limits hit
Sealed receipts89,261 total
App connectionsPKCS#11 · Java · gateway
Cloud keys3 clouds · 11 keys
CI/CD2 runs active · 0 keys left behind
ROOST-26-0001 · ROOST-26-0002 · pair OK · 3/3 voters · armed
Console home: one tile per product, with live counts.

Where things are

MenuWhat you do thereDocs
ProductsOne tile per product with live countsThe console
AccessRoles, auditors, application and agent identitiesRoles · Auditors
Keys · Partitions · PoliciesPurpose templates, versions, rules and record-only modeApprovals and policies
ApprovalsEvery sensitive action waiting for passkey sealsApprovals and policies
Alerts · RecordsThresholds, sealed audit chain, syslog and SNMP export, evidence reportsAlerts · Export
Devices · DiagnosticsBoxes, pairs, enrollment, identity, firmware, maintenance, time policy, air-gap, re-arm; roost check resultsDevice ledger · roost check
Cloud keys · CI/CDKeys held for cloud services; CI runs with temporary partitionsCloud keys · CI/CD