Features
Notifications and chat apps
Notifications in the panel, in the browser, by e-mail, by SMS and through chat apps; the admin decides first which event may go through which channel, then the user chooses.
On this page
Channels
Notifications are delivered inside the panel (the notification bell), as browser notifications (Web Push), by e-mail, by SMS and through chat apps. The supported chat destinations are Telegram, WhatsApp, Slack, Discord, Microsoft Teams, Google Chat, Mattermost, Rocket.Chat, Matrix, ntfy, Gotify, Pushover and a signed JSON webhook.

The bell folds consecutive notifications on the same subject into one line with a count; the line can be opened and its entries read one by one.
First the admin, then the user
Under Settings → Notification rules you decide for each event whether it is on, which channels may be used, which are on by default and whether users may change their own choice. Under My account → Notifications a user chooses only among the channels you allow. If you fix an event, users' earlier choices are ignored.
Every channel can be tried with "Send a test". Tests are limited: 6 an hour per account, for SMS also 6 an hour per number, and for a chat channel also 6 an hour per address.
A failure on one channel does not stop the others; delivery is attempted 3 times on transient errors.
E-mail and SMS providers
- E-mail: SMTP and 12 API providers: Resend, SendGrid, Mailgun, Postmark, Amazon SES, Brevo, Mailjet, SparkPost, MailerSend, SMTP2GO, Elastic Email, ZeptoMail.
- SMS: 18 providers in Turkey, plus Twilio, Vonage, Infobip, Plivo, Sinch, Telnyx, Clickatell, MessageBird and a custom HTTP API.

Only an admin can change the e-mail and SMS settings. Every setting can be tested before it is saved.
Alerts
If you have switched the monitoring stack on, Prometheus / Alertmanager alerts arrive as panel notifications.
Limits and conditions
- WhatsApp: needs the Meta Cloud API and an approved message template.
- Telegram: the bot must not have a webhook defined.
- Webhook and browser-notification addresses supplied by a user must be public HTTPS; no request can be made into the internal network.
- The inbox names operations in words; browser notifications, e-mails and chat messages still carry the operation's raw name.
- The README notes that notification e-mails were not sent for a while on Node 22 because of a date-format bug, and that this was fixed in the second security round.
Sources: docs/notifications.md, docs/settings.md (Turkish).
Install command
curl -fsSL https://lightningvm.app/install.sh | sudo shUbuntu 22.04 / 24.04 / 26.04. Requirements and options
