01 / Alerts without a messenger
Your alerts,
without Telegram or a VPN.
Acktide is on-call alerting software for engineering teams. It sends monitoring alerts to a dedicated app on your phone, without Telegram, bots or work chats. Your on-call schedule determines who gets notified. Everyone can see who acknowledged the alert. If nobody responds, Acktide notifies the next engineer.
Try Acktide Cloud30 days free · No card required · Then from RUB 10,000/month
Download Free for your server · See the delivery test
Android: APK available · iOS: coming soon
Add a phone call or SMS for critical alerts.
Alerts
02 / Easy Alertmanager integration
Connect with
a few lines
of configuration.
Create an Alertmanager source in Acktide and add its webhook to your monitoring configuration. Alerts arrive with their labels. You can keep your existing notifications running alongside Acktide.
Alertmanager setup guideSave the URL to a file Alertmanager can read, and configure the route for the receiver acktide.
# Add to your Alertmanager configuration
receivers:
- name: acktide
webhook_configs:
- url_file: /etc/alertmanager/acktide.url
send_resolved: trueacktide.url. send_resolved also sends recovery notifications.03 / Fewer alert chats
No more
separate chats
for every team.
A chat for Kafka, another for databases, another for the night shift. Each needs members, a bot and an agreement about who responds.
In Acktide, you assign responsibilities to teams and set their schedules. The engineer on call gets the alert. When someone is away, add an override to the schedule. No need to reorganize your chats.
How on-call worksA separate chat for each group
- Kafka · alerts
- Databases
- Night shift
Each with its own bot, members and rules.
With Acktide
A problem with Kafka?Anna gets the alert.
She is on call for the Kafka team today.
04 / On-call routing
Alerts go to whoever
is on call now.
Schedules, rotations and overrides determine who gets notified. The rule team: payments routes the alert to the payments team. When the next shift starts, the next engineer receives the alerts.
How recipients are selected- Which service?team: payments
The label comes from your monitoring system.
- Who owns it?Payments team
The routing rule links the alert to a team.
- Who is on call?Anna Volkova
The alert goes to the engineer on the schedule.
05 / On-call scheduling
Set up your
on-call schedule.
Choose the engineers and their rotation order. Set a start time, shift length and time zone. Acktide calculates who is on call from that schedule.
A vacation or a shift swap? Assign an override for the hours you need. Preview coverage for the coming week.
Create an on-call scheduleOn-call and services → Schedules
Engineers in rotation order
- Mon, 10:00 — Thu, 19:00Anna
- Thu, 19:00 — Fri, 09:00Ilya override
- Fri, 09:00 — Mon, 10:00Anna
06 / Alert acknowledgment
Everyone knows
who took the alert.
The engineer taps ACK in the notification. Their name and acknowledgment time appear in the history. The team can see someone has responded. Delivery to the device and a human response are recorded separately.
See a real delivery test- Received from Alertmanager
- Delivered to Anna’s phone
- Notification displayed
- ACK: Anna Volkova acknowledged the alert
07 / Backup engineer
Built-in
escalation.
If the engineer on call does not acknowledge an alert, the next escalation step runs. You define the wait time, backup engineers and repeats. Acktide follows these rules automatically.
Set up escalation rules08 / Phone notifications
No response?
Make it a call.
Configure a call or SMS through a phone gateway for critical alerts. Engineers add their phone number, choose a channel and set a delay. If the alert is still unacknowledged after that delay, Acktide sends a phone notification.
Set up phone notificationsIncoming call
Acktide mobile09 / Independent projects
All your clients’
alerts in
one app.
If your team supports several separate projects, connect their Acktide servers to one app. Each project keeps its own data and access controls. ACK goes back to the server that sent the alert. This works for internal projects and separate clients alike.
Connect multiple projectsYour organizations
Alerts arrive from all enabled connections at the same time.
10 / Your infrastructure
Deliver alerts
from your server,
without Google FCM.
Run Acktide on your own infrastructure. Direct Android delivery works without Google FCM. Free has no license limits on users or events. Enterprise licenses are verified offline, without contacting our servers.
Download and install FreeIngestion, delivery, ACK and escalation keep working. Corporate OIDC sign-in is disabled, so keep a local administrator login available.
11 / A second site
Your alerting
has a backup
site too.
Two Acktide installations work as one system. If one site is unavailable, the other keeps receiving events and Android selects an available address. Peering is included in Free.
How peering worksMoscow
Saint Petersburg
12 / Built-in analytics
Find delays.
Work on your MTTR.
Built-in dashboards and reports show how quickly your team acknowledges alerts and resolves incidents. Compare services, teams and engineers, find delays and check whether changes help. Reports include median and p95 acknowledgment and resolution times.
Explore incident reportsData is available through the JSON APIs /v1/metrics and /v1/reports. You can export reports as CSV.
| Service | Total | ACK, median | ACK p95 |
|---|---|---|---|
| storage | 22 | 8 min | 19 min |
| payments-api | 14 | 2 min | 6 min |
| postgres | 9 | 3 min | 11 min |
| kafka | 6 | 1 min | 3 min |
Start with one service
Connect your monitoring system, install the app and send a test alert. Check the full path through to ACK alongside your existing notifications.
Try Acktide Cloud30 days in the cloud, no card required · Then from RUB 10,000/month · Free self-hosted edition