Release status#
What has been checked for this release:
- Continuous integration passes: Go unit tests and PostgreSQL/NATS integration tests with the race detector, govulncheck, npm audit, a gitleaks secret scan, the Web build and UI tests, deployment contract tests and the container image builds. Release builds run the full suite first.
- An upgrade check runs before migrations in both Helm and Compose and stops an upgrade that would silently stop paging people. See the upgrade check gate.
What remains before general availability:
- A real-world pilot deployment.
- An external penetration test.
- SCIM validation against a live Okta or Microsoft Entra ID tenant; so far it has been tested with SCIM test clients only.
- Store distribution of the mobile apps; for this release the operator builds the Android and iOS apps from source, and neither is in the App Store or Google Play.
- Validation of the CUCM gateway against a real CUCM cluster; so far it has been tested against an Asterisk-based CUCM stand-in.
Implemented core#
- Authenticated Alertmanager, Icinga, Alerta, PagerDuty Events API v2 compatible and generic event ingestion, plus heartbeat monitors.
- Normalization, severity mapping, routing history, duplicate protection and incident lifecycles.
- Teams, services, users, schedule layers/overrides, escalation policies and maintenance windows.
- Web incident response, acknowledgement, resolution, notes, audit and Delivery Health.
- Status pages with public titles and email subscribers, stakeholder updates, and postmortems with action items.
- Organization administration, provider configuration/testing, API keys and service accounts, reports and guided onboarding.
- Local passwords, SSO (OpenID Connect), LDAP / Active Directory sign-in, SCIM 2.0 provisioning and break-glass accounts.
- Audit export (JSON Lines or CSV) and audit streaming to HTTPS collectors or TLS syslog.
- Several organizations per deployment.
- Self-hosted Compose and Helm deployment paths, customer CA and private registry configuration, file-backed secrets and the upgrade check.
Optional adapters#
| Capability | Boundary |
|---|---|
| Email / APNs / FCM / Slack / Microsoft Teams / Mattermost / Twilio SMS and voice | Implemented adapters; real delivery and site configuration must be verified. |
| Push relay | Implemented relay with credentials pinned to each deployment's server address; only an incident reference leaves the site. |
| Internal voice (paging calls) | Implemented HTTPS adapter and signed callback contract; customer PBX bridge required. |
| Live call routing | Twilio numbers, a generic PBX gateway API, and a bundled CUCM gateway (Asterisk image plus the voicegateway service on a SIP trunk). |
| Ticketing | Jira Cloud, Jira Server / Data Center and Halo, with comment mirroring and optional ticket-closure sync. |
| iOS and Android apps | Repository clients built from source by the operator; signing, distribution, network and real-device acceptance are operator work. |
| Prometheus / Grafana / OTel | Self-hosted metrics/log integration and deployment examples; native app distributed tracing is not implemented. |
Known limitations#
- No WhatsApp adapter, email intake or SNMP trap intake.
- Additional organizations are created by the operator with the bootstrap command; there is no API or Web screen to add one, and no organization delete.
- Incident numbers are shared across all organizations of a deployment, so each organization sees gaps in its numbering.
- The mobile apps keep one account per server address, so a phone can be signed in to only one organization of a deployment at a time.
- Notification and subscriber emails are minimal plain-text messages; there are no branded templates.
- No Web-based OIDC identity unlinking/rebinding.
- No exhaustive minute-by-minute future on-call coverage timeline.
- No full organization-admin configuration screens for every team-admin workflow.
- No unbounded UI exports, complete analytics/reporting product, or turnkey retention/compliance suite.
Verification is not certification#
CI runs the backend race/integration tests, the Web UI tests and the deployment contract tests, and database backup/restore has been exercised. AckNexa also comes with an end-to-end lab with real Prometheus, Alertmanager and Icinga 2, the mobile apps and a CUCM stand-in, for operators to repeat these checks. None of this certifies production failover, point-in-time recovery targets, capacity, private registry interoperability, real SMTP/IdP/PBX installations, or end-user mobile delivery at your site.
Commercial and legal information#
AckNexa is self-hosted on your infrastructure; it is not offered as a hosted subscription, and it is not open source. Pricing, licence terms and support are arranged directly: write to hello@acknexa.com.