Skip to content

Private notifications for every screen

Send notifications to any device: Mac, iPhone, Android, Windows, or Linux.

Publish private notifications from scripts, servers, CI pipelines, and monitoring tools. Bells delivers them to native mobile and desktop browsers with clear delivery status.

Private channelsNo SDK requiredNo credit card
BellsProduction is livenow
bells.sh
curl --request POST https://api.bells.sh/notify \
  --header "Authorization: Bearer $BELLS_TOKEN" \
  --data '{
    "channel": "deployments",
    "title": "Production is live",
    "body": "Deployment complete"
  }'
Request examples for curl, Python, Node.js, Go, Java, and the Bells CLI publish a deployment notification.

Available across mobile & desktop browsers

iOSAndroidWindowsmacOSLinuxWeb

Core capabilities

One API for native mobile & Web Push

Connect any HTTP client, manage private channels, and inspect every delivery attempt from one dashboard.

Publish over HTTP
Send notifications with curl, fetch, or any existing HTTP client. No SDK is required.
Deliver to every device
Use one private channel to reach native mobile apps and supported desktop browsers through Web Push.
Inspect delivery status
Track API acceptance and provider or push-service submission as separate states.

Integrations

Connect the tools you already use

Send alerts from popular monitoring, automation, CI, and homelab tools. If it can make an HTTP request, it can notify Bells.

  • Home Assistant
  • Uptime Kuma
  • Grafana
  • n8n
  • GitHub Actions
  • Prometheus
  • Zapier
  • IFTTT
  • Docker
  • Sentry
  • GitLab CI/CD
  • Jenkins
  • Homelab
  • Healthchecks.io
  • Cron jobs
  • Any webhook

Don't see your tool? Use the HTTP API or any webhook-capable workflow.

Quick start

Send your first notification in minutes

Create a private channel, connect your devices, and publish with a standard HTTP request.

Private channels.
Every channel is authenticated and never anonymously discoverable.
Safe retries.
Idempotency prevents duplicate events when a request must be retried.
Clear delivery states.
API acceptance, provider submission, and device acknowledgement stay distinct.
bells.sh

# Tell every device the deploy is done

curl-X POSThttps://api.bells.sh/v1/notify\

  -H"Authorization: Bearer $BELLS_KEY"\

  -d'{"channel":"deploys","title":"Production is live"}'

✓ 202 Accepted evt_01JZ9P7K2M

Delivery & automation

Controls for routing, privacy & diagnostics

Intelligent routing

Route by content & priority

Match structured fields and send each notification to the appropriate devices and actions.

WHEN

priority == "high"

THEN

Mobile + desktop browsers

Delivery surfaces

Native mobile apps & desktop Web Push

Receive notifications through native mobile apps and supported desktop browsers through Web Push.

iOSAndroidWinmacOSLinux

Private by default

Use authenticated private channels and scoped publishing credentials. Public topics are not supported.

Delivery history

Review notifications, delivery attempts, and provider responses without searching raw logs.

Separate delivery states

Distinguish durable API acceptance from provider submission and reported notification opens.

Plans & pricing

Choose a plan for your usage

Every plan includes private channels, mobile and desktop delivery, and the HTTP API.

Free

The complete core loop for personal alerts.

$0/month

Billed monthly

$0/month

Always free · No credit cards required

  • 3 private channels
  • 3 connected devices
  • 100 notifications per day
  • 2,500 notifications per month
  • 2-day notification history & retry window
  • Native mobile + desktop Web Push
  • No attachments
Get Started

Plus

Most popular

Richer payloads for everyday automation.

$5/month

Billed monthly

$3.75/month

Save 25%

$45 billed yearly

  • 10 private channels
  • 6 connected devices
  • 2,000 notifications per day
  • 50,000 notifications per month
  • 7-day notification history & retry window
  • 25 MB per attachment
  • 5 GB of attachment uploads per month
  • 7-day attachment retention
Get Started

Pro

More automation and longer retention.

$10/month

Billed monthly

$7.50/month

Save 25%

$90 billed yearly

  • 30 private channels
  • 20 connected devices
  • 5,000 notifications per day
  • 120,000 notifications per month
  • 15-day notification history & retry window
  • 512 MB per attachment
  • 10 GB of attachment uploads per month
  • 15-day attachment retention
  • Email actions
  • Advanced routing workflows
Get Started

Daily and monthly notification limits both apply. Attachment upload allowances reset each billing month. During the retention period, notifications remain visible in the web dashboard and are retried when a device reconnects.

Frequently asked questions

Have a different question? Send us an email.

Is Bells another public topic service?
No. Every channel is private and authenticated. Public and anonymously discoverable channels are intentionally not part of Bells.
Do I need an SDK?
No. Use curl, fetch, your existing HTTP client, or any tool that can call a webhook.
Which devices are supported?
Bells is designed for native iOS and Android apps plus Web Push in supported browsers on Windows, macOS, and Linux.
What does 202 Accepted mean?
It means the notification and its delivery work are durably stored. It does not overstate what an end device has displayed.
Can I start for free?
Yes. The free plan covers the complete core loop: create a channel, publish an event, and receive it in a mobile app or supported desktop browser.
Can Bells route by notification content?
Yes. Rules can evaluate structured fields such as priority and content to select devices and supported actions.

Get started

Send your first notification for free

Create a private channel, connect a device, and publish over HTTP. No credit card required.