The console
Roost boxes are managed in the Axowl console. The left menu groups everything by what you want to do; the pages in this section describe each group and its API.
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
Menu groups
- Products: one tile per product (code signing, documents, certificate authority, data encryption, TLS keys, AI agents, sealed receipts, app connections, cloud keys, CI/CD) with live counts.
- Access: roles, auditors, application identities and AI agents. Roles.
- Keys, Partitions and Policies: keys by purpose with versions, partitions for teams and environments, rules with approval and limits. Approvals and policies.
- Approvals: the inbox of actions waiting for passkey seals.
- Alerts and Records: thresholds and recipients, the sealed audit chain, syslog and SNMP export, evidence reports. Status and alerts, Auditor, export, time and attestation.
- Devices and Diagnostics: boxes, pairs, enrollment, identity and attestation, firmware, maintenance, time policy, air-gapped sites, re-arm, licenses, and roost check results. Device ledger, roost check.
Who can open it
The organization Owner and members holding the Roost Admin role open the console. Auditors see the records pages. Seal actions, such as binding a box, appointing an auditor or approving a release, need a passkey seal bound to that exact action.