1.0.0-rc.1A release candidate for pilot deployments

Own the alert. Own the response.

Connect your monitoring, reach whoever is on call, and keep the whole response on infrastructure you control.

The AckNexa Overview with fictional data: three triggered and four acknowledged incidents, incidents that need attention, open incidents by service, who is on call now for each schedule, and an active maintenance window.
The Overview in the AckNexa Web application. Every screen on this page shows fictional data.

Start with the signals you already have

  • Prometheus Alertmanager
  • Icinga
  • Alerta
  • PagerDuty-compatible senders
  • Generic webhooks
  • Heartbeat monitors
Connect your monitoring

From alert to resolution

One incident. Every step on the record.

Monitoring tells you something is wrong. AckNexa connects that signal to the people, policies and context needed to act, and keeps the history together.

  1. 1Detect

    Every alert finds its owner.

    Authenticated integrations receive your monitoring events. AckNexa normalizes them, recognizes repeated observations of the same condition, maps severity to P1 through P5 and routes each condition to a service and its owning team.

    Routing and deduplication
    The Incidents list with fictional data: seven open incidents from P1 to P4 on services such as Checkout, Payments API, Search and Identity, each with its alert count, state, assignee, age and an Ack or Resolve button.
  2. 2Page

    The right person hears about it.

    The service’s escalation policy finds who is on call and pages them, step by step, on the channels you chose. Every attempt is recorded, and an acknowledgement cancels the pages still waiting.

    Escalation policies
    An incident's escalation and notification history with fictional data: step 1 paged Priya N. by push, SMS and email, each handed to the provider, step 2 was cancelled, and the timeline shows a stakeholder update, a status page update, a note, a Jira ticket and the acknowledgement.
  3. 3Respond

    Coordinate in one place.

    Acknowledge, add notes, reassign or escalate. Send an update to stakeholders, publish to a status page and open a Jira or Halo ticket from the same incident.

    Respond to an incident
    The incident drawer for fictional P1 incident 1284, Checkout error rate above 5%, acknowledged: Acknowledge, Resolve, Reassign, Escalate and Snooze actions, a note box with Send to stakeholders, a linked Jira Cloud ticket, a status page update panel, the owning team and responder, and six grouped alerts.
  4. 4Review

    Learn from every incident.

    By default, resolved P1 and P2 incidents get a blameless postmortem draft, prefilled from the timeline, with action items, owners and due dates. Owners are reminded when a review is overdue.

    Postmortems
    The postmortem editor for fictional P2 incident 1279, order emails delayed, in review: title, owner, due date, summary, impact and root cause, with the incident timeline alongside and an Export Markdown action.

Around the response

Everything the response needs.

Schedules, channels, a hotline, status pages, reviews, tickets, identity and audit, in one self-hosted product.

On-call schedules and escalation

Know who is on call. Reach them in order.

Rotation layers with priorities, primary and secondary tiers and temporary overrides. Escalation policies choose who is paged, how and when, and maintenance windows hold pages during planned work.

The on-call calendar for one week with fictional data: Payments primary and secondary, Platform primary and Search primary schedules with rotation shifts, two overrides and a line marking the current time.

Notification channels

Push, SMS, voice and email.

Pick the channels that work in your network, from internal SMTP and your own voice bridge to Twilio and team chat with Acknowledge links.

Live call routing

A hotline that rings whoever is on call.

Every call opens an incident and rings the on-call responders in order. Use a Twilio number, your own PBX, or Cisco CUCM through the bundled SIP gateway.

Postmortems

Blameless reviews, already started.

One review per incident, prefilled from its timeline, with action items, owners and due dates. Export it as Markdown.

Ticketing

Jira and Halo, in step.

Open a ticket from the incident, mirror the response as comments, and optionally resolve the incident when the ticket closes.

Identity

SSO, LDAP and SCIM.

Single sign-on with OpenID Connect, LDAP and Active Directory sign-in, SCIM 2.0 provisioning, and break-glass accounts your identity provider cannot change.

Audit

Every action, streamed to your SIEM.

Export the audit log as JSON Lines or CSV, or stream it as signed JSON batches over HTTPS or as syslog over TLS. Passwords, tokens and keys never appear in an export or a stream.

Architecture

Every event is committed before it is accepted.

The API writes each raw event and its outbox row to PostgreSQL in one transaction, then answers. Workers carry committed work over NATS JetStream to route, escalate and notify.

  • PostgreSQL is the system of record. Configuration, raw events, incidents, jobs, notification history and audit.
  • Restarts keep pending work. Escalation jobs live in PostgreSQL and are claimed by workers.
  • Optional pieces stay optional. Identity providers, push, SaaS channels and the CUCM gateway connect only when you add them.
Architecture and reliability
Diagram of the AckNexa components. Monitoring sources (Prometheus Alertmanager, Icinga, Alerta, generic webhooks and heartbeat pings) send authenticated HTTPS requests to the API, which contains the integration gateway. The API commits each raw event and its outbox row to PostgreSQL, the system of record, in one transaction. Workers publish committed outbox events to NATS JetStream and consume them to normalize, deduplicate and route alerts. Workers also run escalation, notifications, status pages, stakeholder updates, chat channels, outbound webhooks, ticketing, audit streaming, heartbeats, postmortems, retention and reconciliation. They deliver through SMTP email, APNs, FCM or the push relay, Twilio SMS and voice, a voice bridge to your PBX, Slack, Teams and Mattermost, signed webhooks, Jira and Halo, and a SIEM. Responders are paged and act in the Web UI or the iOS and Android apps, which talk to the API. An identity provider (OIDC, LDAP, SCIM) and the CUCM gateway for live call routing are optional and connect to the API.
Dark boxes are AckNexa components, light boxes are your systems or providers, and dashed boxes are optional.

Customer-controlled by design

On premises. Not on someone else’s control plane.

Run the core on your PostgreSQL, NATS, compute and network, with your DNS, your certificate authority and your identity provider.

No vendor control plane

Ingest incidents, coordinate the response and use the Web UI without a vendor-hosted AckNexa control plane, a public cloud account or an external notification API.

Ready for private networks

Once images and configuration are in place, the core can run in an isolated network with internal SMTP, a customer voice gateway and private identity, DNS and PKI.

Docker Compose or Helm

A single-host Compose profile for small installations, or a Helm chart for a production topology on your own Kubernetes.

Your network

  • Web UI
  • API and gateway
  • Workers
  • PostgreSQL
  • NATS JetStream
  • Local observability
  • Private DNS and TLS
  • Internal OIDC
  • Customer backups

Internal SMTP and customer voice gateways can stay private. APNs, FCM and SaaS providers are optional adapters with their own connectivity requirements. See the channel connectivity matrix.

Web and mobile

Respond from wherever you are.

The Web app, at any size

Responders sign in, review, acknowledge and resolve in the browser, on your deployment’s own HTTPS address. Browser response needs no APNs, FCM or public cloud service.

Native iOS and Android apps

List incidents with live updates, acknowledge and resolve, see your on-call shifts and cover requests, and open the incident when you tap a page. On Android, P1 pages use a separate alarm channel.

For release 1.0.0-rc.1 the operator builds both apps from source. Neither app is in the App Store or Google Play yet.

Web and mobile access
The AckNexa Web application on a phone-sized screen with fictional data: incident cards with severity, number, title, service, alert count, state and an Ack or Resolve button, above a bottom tab bar.
The Web application on a phone-sized screen, with fictional data.

Why teams choose AckNexa

One product. Your infrastructure, your channels.

Fewer tools to buy and connect, pages through channels you already run, and less noise for whoever is on call.

One product for the whole response

Paging, on-call schedules, escalation, status pages, postmortems, live call routing, Jira and Halo tickets, reports and audit streaming work together in one product.

Pages through channels you already run

Email through your internal SMTP server, calls through your own PBX or Cisco CUCM, and push through your own Apple and Firebase accounts. Twilio, Slack and Microsoft Teams are there when you want them.

Less noise for whoever is on call

Deduplication and grouping turn repeats into one incident, routing rules send each alert to the team that owns it, and maintenance windows hold pages during planned work.

Release status

Release 1.0.0-rc.1 is a release candidate.

It is intended for pilot deployments and is not yet generally available. Its CI suite passes. A real-world pilot, an external penetration test, SCIM against a live identity-provider tenant, app-store distribution of the mobile apps and a real CUCM cluster test remain before general availability.

Read the release status

One signal. The right people. A shared next step.

AckNexa runs on your infrastructure. Pricing, licence terms and support are arranged directly with the team.

Find your next step.

Search runs locally. Nothing is sent to a search service.