Observability and incidents, on the same platform as the fix
Spotting a problem and responding to it shouldn't mean jumping between tools. Avoryx pulls in your metrics and health checks, pages whoever's on call, keeps an audited timeline of the incident and drafts the postmortem. The board item and the pull request that fixed it are linked right there.
A native pull-based metrics engine — you don't buy monitoring separately.
PagerDuty pages people but doesn't watch your systems — you bolt on a metrics vendor. Avoryx has a poll engine that scrapes each registered service's health and metrics endpoints into live dashboards and a per-metric log. Regions self-monitor by exposing a Prometheus-text endpoint; an optional push route exists too. Pull was chosen deliberately so a misbehaving source can't overwhelm the platform.
- Poll engine → service_health_checks + metric snapshots + an unpivoted live-metrics log
- Regions self-monitor via a /self-metrics Prometheus-text endpoint
- Optional push ingest for sources that prefer to send
- DORA metrics (deploy freq, lead time, change-fail, MTTR) computed from real runs & incidents
Built with precision — every part of it.
Not a thin feature bolted onto a suite. Here's the real surface area, grouped.
Metrics & health
- Pull-based poll engine scrapes each service's health + metrics URLs on a schedule
- Live dashboards from real snapshots — no Math.random, no fake series
- Prometheus-text parsing; regions expose a self-metrics endpoint to self-monitor
Alerting & on-call
- An alert engine evaluates thresholds against ingested metrics
- On-call schedules, escalation and paging
- Slack + email delivery on breach, wired through the same notification path as SLAs
Incidents
- Incident records with a real, audited timeline — every action carries a real actor
- Severity, status and links to the board item and PR that resolve it
- High-confidence critical support tickets can auto-open a Sev1 incident
Postmortems & DORA
- AI-drafted postmortems, linked to the resolving work item and pull request
- DORA rollups from real pipeline_runs + incidents
- One bill for monitoring and paging instead of two subscriptions
Everything PagerDuty does — plus what only one platform can.
Avoryx is licensed at the platform level — every module is included in one seat, not billed per module. See pricing. Competitor capabilities vary by plan; verified June 2026. Avoryx's Merchant-of-Record and payouts are on the roadmap; SOC 2 Type II is in progress, not certified.
Why one platform wins here.
One bill, not two
Monitoring and paging usually mean two subscriptions and a glue integration. Avoryx bundles the metrics engine and the incident/on-call flow.
Incident → fix, connected
An incident links to the board item and the pull request that resolves it, so the postmortem writes itself against real artifacts.
Regions self-monitor
A service exposes a Prometheus-text metrics endpoint and the poll engine ingests it — no agent sprawl, and a bad source can't flood the platform.
Common questions
Yes — it covers on-call scheduling, alerting, audited incident timelines and AI postmortems, and adds a native pull-based metrics engine so you don't pay a separate monitoring vendor.
The rest of the platform
See it on your real numbers.
15 minutes, your stack, your per-seat math, the revenue back-office live.
