Contact

Let’s talk about your on-call.

Ask about a pilot, pricing and licence terms, a demo call or a partnership. AckNexa runs on your infrastructure, and pricing, licence terms and support are arranged directly with the team.

Send an enquiry

All fields are required unless marked optional.

People who respond to incidents or go on call.

For example Prometheus Alertmanager, Icinga or Nagios.

Interested in (optional)

What would you like to discuss? A line about your current setup helps.

Or email [email protected].

Why AckNexa

Why teams choose AckNexa.

Each point is a capability the product guide describes, with the chapter to check it against.

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.

Capabilities and limitations

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.

Notification channels

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.

Routing and deduplication

Runs where your systems already run

Docker Compose or Helm on your own servers or Kubernetes, with your PostgreSQL, NATS, identity provider and certificates. No vendor-hosted control plane is required.

Deploy on your infrastructure

One view across teams

An operations team can follow and act on every team’s incidents, linked incidents show what caused what, and stakeholder updates and status pages go out from the incident itself.

Link related incidents

Your data stays in your network

Incidents, alert payloads, contact details and the audit log live in your PostgreSQL, and the audit log can stream to your SIEM. Nothing leaves unless you add an optional adapter such as push, chat or Twilio.

Security and identity

Where the savings come from

Spend less on tools, messages and lost hours.

We don’t publish savings figures, because they depend on what you use today. These are the places AckNexa can make a difference.

  1. Fewer tools to buy and connect

    With paging, schedules, status pages, postmortems, call routing and reports in one product, there are fewer separate subscriptions to pay for, fewer integrations to build and keep working, and one tool for responders to learn.

  2. Infrastructure you already run

    AckNexa runs on your servers or Kubernetes, next to your monitoring, rather than as a hosted subscription. Pricing and licence terms are arranged directly, so ask us to compare them with what you pay today.

  3. Your own channels for everyday pages

    Send pages by email through your own SMTP server, by push through your own Apple and Firebase accounts, and by phone through your own PBX or Cisco CUCM. You pay a messaging provider per SMS or call only where you choose to.

  4. Fewer wasted pages and on-call hours

    Deduplication, grouping, routing rules and maintenance windows keep repeats, planned work and misrouted alerts from paging people. Fewer needless pages mean fewer interrupted nights and less time lost the next day.

  5. Less time coordinating

    An operations team sees every team’s incidents, linked incidents show the cause, and stakeholder updates, status page posts and Jira or Halo tickets go out from the incident instead of by hand.

  6. Measure the difference

    Reports show time to acknowledge and time to resolve per service and team, and pages per person per week, so you can see whether a change cut response times and on-call load. See the Reports view in the demo.

Tell us about your on-call. We’ll take it from there.

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.