Assurance center
One health view for the parts of AxioRank that run in the background, your integrations, the ML lane, data residency, and the async job queue, so a silent degradation never hides.
Most of AxioRank's value sits on the hot path, where a failure is loud: a denied call, a raised alert. But the supporting machinery runs in the background, where a failure can be quiet. A Slack channel stops delivering, the ML lane runs out of quota, a webhook receiver starts timing out. The assurance center is the single view that surfaces these before they become a gap in your coverage.
Where to find it
The assurance center reads live from your workspace, summarized into a health
banner on the dashboard and inline callouts on the pages each signal affects
(channels, alerts, policies). A single needsAttention count tells you, at a
glance, whether anything wants a look.
What it checks
Integration health
Every outbound delivery path reports its current state (ok, degraded, or down):
- Notification channels: Slack and email destinations for alerts and digests.
- Log streams: SIEM forwarders (Splunk HEC, Datadog, NDJSON over HTTPS, and OpenTelemetry/OTLP).
- Webhook endpoints: your own receivers for AxioRank events.
- SOAR connections: Jira, ServiceNow, and signed-webhook response actions.
A path that has started failing is flagged so you can fix it before the next alert silently fails to land.
ML lane status
The detection-intelligence lane is optional and gated, so the assurance center reports exactly where it stands: whether your plan is entitled (Team and above), whether the workspace has opted in to model egress, and whether the endpoint is configured. When all three are true, it also reports the last 24 hours of health: how many assessments ran, completed, or came back unavailable, so a degradation (errors plus unavailable responses) is visible rather than inferred.
Data residency
If your workspace selects an EU data region, the assurance center confirms the region is actually being honored: an in-region inference endpoint must be configured, or the lane would fall back to the default region. The check makes a residency promise verifiable instead of assumed.
Dead-letter queue
Async jobs (webhook deliveries, stream forwards, assessments) that exhaust their
retries land in a dead-letter queue. The assurance center reports the pending
count so a backlog never goes unnoticed. You can inspect and replay a dead-lettered
job once the underlying cause is fixed (POST /api/dead-letter/[id]/replay).
Audit ledger integrity
The tamper-evident audit log is recomputed on a schedule, and the assurance center reports whether the last check passed. If the sealed rows no longer match their signed checkpoint, it names the failing checkpoint sequence and the reason, and links you to the integrity page to investigate.
Continuous red-team
The scheduled red-team validator scores your defenses on each run. The assurance center flags a regression when the latest score drops below its recent peak on the same corpus version, meaning a control that was catching attacks has been weakened. Available on Pro and above.
Compliance posture
From the daily compliance snapshots, the assurance center flags any framework control that dropped below its recent best, so a control you were meeting that has weakened surfaces here rather than at audit time. Available on Pro and above.
Reading the report
needsAttention sums the conditions that warrant action: an integration that is
degraded or down, a data region that is not being honored, an ML lane that is
entitled and opted in but degrading, a non-empty dead-letter queue, an audit
ledger whose tamper-evident chain failed to recompute, a continuous red-team
posture that regressed below its recent peak, or a framework compliance control
that regressed. Zero means
the background machinery is healthy. A non-zero count points you straight at the
signal that needs attention.
Next steps
- Detection intelligence: the ML lane this monitors.
- Audit export: the log streams this monitors.
- Response engine: the SOAR and webhook paths this monitors.
- Data residency: the residency promise this verifies.
Claims and verification
Every "first" or "only" claim AxioRank makes, stated precisely, with how to verify it yourself.
Detection benchmark methodology
How the competitive detection benchmark works. The normalized case schema, the adapter contract, the tools we run and the ones we cannot, the corpora and how benign controls are built, the catch-rate-at-a-false-positive-budget metric, and the pre-registered gate. Everything you need to reproduce every number.