Reach your users' phones and desktops, with no app to build.
A message sent to a topic reaches every device subscribed to it. Your user installs a free notifications app and subscribes with the QR code on your page. You send from a function, the API, the CLI or MCP.
What you get
Topics
A topic is a name in a project, such as orders or news. A message sent to it reaches every device subscribed to it.
env.NOTIFY in a function
With one line in the project file, a function sends to the project's topics with env.NOTIFY.publish. A topic created after the deploy is there with no new deploy.
The API, the CLI and MCP
Send from anywhere with the API, from a terminal with the CLI, or from your coding assistant with MCP. The dashboard has a test send too.
A full message
A title, text, a priority from 1 to 5, tags, and a link that opens when the notification is tapped. Up to three buttons, each opening a link or calling your address.
Scheduled delivery
Send a message for a set time or after a number of seconds, such as a reminder for an appointment.
Subscribe with a QR code
Your page shows the subscribe QR code or link. The user scans it with the notifications app and gets the messages on a phone or desktop from then on.
Private topics
A device subscribes only with that topic's token, until it expires. Make a token with the API, or sign one in your function with the project's NOTIFICATIONS_KEY secret. Revoke one token, or all of a topic's.
Messages for offline devices
A device that was offline gets the messages it missed when it reconnects. See the kept messages in the dashboard.
Previews get their own topics
Each preview and development environment has its own topics. A message sent from a preview never reaches production's devices.
Inside Iran
Android phones receive straight from our servers inside Iran, with no foreign push service, so messages arrive during an international cut too.
Sends, deliveries and devices
See each topic's subscribed devices, messages sent and deliveries in the last 24 hours, and the daily usage of each project.
Your own alerts on your phone
In your account's notification settings, pick your phone beside email and SMS. Alerts, a low wallet, a failed deploy and a new sign-in reach your phone.
One topic, one line to send
Create a topic, show the subscribe QR code on your page, and send from a function or the API.
cloudhost notifications create orders --project shop
cloudhost notifications publish shop/orders "سفارش ۱۰۴۲ آماده است" \
--title "فروشگاه" --priority 4 --click https://shop.example.com/orders/1042
# a subscribe token and the link a QR code carries
cloudhost notifications token shop/orders --ttl 86400Per message and per delivery
Each message you send and each delivery to a device is counted. It is charged from the month's credit first, then from the wallet. Your users pay nothing for the app.
Questions
No. Your users install a free notifications app from the store, and the setup page in the dashboard says which one and where to get it. You only show the subscribe QR code on your page.
Android receives straight from our servers inside Iran, so a cut abroad does not affect it. iPhone accepts instant notifications only through Apple's service, so during a cut they may arrive late. For urgent messages to iPhones, send an SMS too.
Topics are private: a device subscribes only with that topic's token. Your function makes a token with an expiry for a user after they sign in. Revoke a token whenever you like; the device gets nothing from the next minute.
Alerts are rules on your app's metrics and logs that tell your team. Notifications are messages your app sends to its own users. You can get your own alerts on your phone too.
Create your first topic
One command for the topic, one line to send.
Sign-up is by invite for now. If you have a code, create your account.
Sign up withEmail codeSMS code