go-notificationgo-notification
Channels

Channel Overview

All 24 drivers at a glance — pricing, free tiers, and when to use each.

go-notification ships with seven channel families. Every family has multiple driver choices so you can match cost, deliverability, and compliance needs.

Quick Comparison

ChannelDriversFree OptionsPaid OptionsBest For
Email7SMTP, Mailgun (100/day), SES (3k/mo)SendGrid, PostmarkTransactional email
WhatsApp5WAHA Core (self-hosted)Fonnte, Twilio, MetaCustomer comms (ID)
SMS4Twilio trial, SNS (100/mo)Twilio, ZenzivaOTP, alerts
Chat5All freeInternal team notifs
Push1FCM (unlimited)Mobile app notifs
Database1Built-inIn-app notifications
Webhook1Built-inCustom integrations

By family

Email (7 drivers)

SMTP, Mailgun, SendGrid, AWS SES, Resend, Postmark, Mailtrap. Start with the Email Overview for driver comparison and cloud port-blocking warnings.

WhatsApp (5 drivers)

WAHA, Fonnte, Wablas, Twilio WhatsApp, Meta Cloud API. See the WhatsApp Overview for official vs. unofficial API tradeoffs.

SMS (4 drivers)

Twilio, Zenziva, Vonage (Nexmo), AWS SNS.

Chat (5 drivers)

Slack, Telegram, Discord, Microsoft Teams.

Push (1 driver)

Firebase Cloud Messaging (FCM) — iOS, Android, and Web.

Database (1 driver — 3 backends)

Database channel — in-app notifications stored in Postgres, MySQL, or SQLite.

Webhook (1 driver)

Generic HTTP POST for any custom integration.

Decision guides

Picking the right provider matters more than the code you write around it. Dedicated guides: