🚀 Why I built my own push notification tool for CI/CD and Home Assistant

Yubal Torres — Mon, 22 Jun 2026 16:17:08 +0000

Nowadays, we all need push notifications. Whether it's for home automation, CI/CD deployments, application monitoring, UniFi Protect, or more.

But, you'll eventually realize that most of those services don't feature push notifications, or those that do, don't offer a permanent history or tray at all (such as Home Assistant).

So, I created Pulsetray

The problem

The idea was simple: I needed an Android app that could receive push notifications with an API request. I wanted to send alerts from my Home Assistant instance, my deployments, database monitoring, and Unifi Protect into one place.

Most importantly, I wanted a persistent history, a way to organize my notifications by origin or category, and the ability to attach rich media like video footage or screenshots.

Research

Naturally, my immediate approach was to do a quick Google search and download the first app that popped up. To my surprise, I found two things:

Chat apps: Most people use chat apps for this purpose, such as Telegram or WhatsApp. It works, but it's clunky, you're mixing notifications from all places and you have limited filtering and storage.
Outdated alternatives: There are some services out there, but they either look really outdated, lack features, or have a local-only approach. Uninstall the app, upgrade your phone or sign in from a different device and your notifications are gone for good.

Building the solution

At this point, I knew I had a problem that I needed to solve myself, and I wanted to build it as a SaaS for others facing the same friction.
Instead of writing a massive technical deep-dive (I'll save this for a future post), here's a high-level overview of the products I created over the last 8 months:

The app: I built the Android app using Kotlin and Kotlin Compose. (Compose is amazing!). This is available in the Play Store.
The web dashboard: Soon after releasing the initial MVP, I figured that forcing users to download the app to use the service was an important activation problem. I would either have traffic with no interaction, or users downloading the app without using it. I recently deployed a Web dashboard that lets users sign up, configure profiles/devices, send test notifications, setup webhooks, and more. This was deployed to Vercel, and is available on Pulsetray.
The backend: This is a monolith (handles both the internal API for the app and dashboard, and the public API for users to trigger notifications) created with Node.js, Express, and TypeScript. For notifications I'm using FCM, of course. This was deployed to Render (and PlanetScale for the MySQL database).

The features

What started as a simple POST request endpoint and an Android app has grown into a much more mature platform. I recently deployed a Web Dashboard and Incoming Webhooks.

Here's what Pulsetray can do right now:

Simple API: Trigger notifications with a standard POST request.
Profiles and devices: You can add more people to your account, and devices. You can onboard devices using a unique token. Notifications can be sent to the entire account, or specific profiles and devices.
In-app notifications tray: Have persistent and searchable history of notifications.
Rich media support: You can attach an image, video or GIF when sending a notification.
Highly customizable: Each notification can have title, body, rich media, and more. They can also be assigned a source (e.g. Home Assistant, GitHub, Unifi, etc.) and a category (e.g. Deployment, Camera, Log, etc.) for easy filtering.
Webhooks: You can trigger notifications with incoming webhooks by just pasting a URL into services like GitHub, Vercel or Sentry. You can configure the title, body, image, targets, and even extract specific information from the JSON body using dot notation to format your notification.
Free plan: I designed the Free plan to be as generous as possible, offering enough notification limits for most people, no bank details required. Paid plans are available for users needing higher limits to help sustain the service.

The code

Code is worth more than a thousand words, so here's how simple it is to send a notification:

curl -X POST https://api.pulsetray.com/v1/notifications \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
  "title": "Script finished running",
  "body": "Production DB backup finished running"
}'

That's it!

Feedback!

My goal is to keep improving the project, so your feedback will be more than welcome! Right now the very next step I have in sight is creating the iOS counterpart, but please, give me your thoughts, suggestions, or questions you may have.

DEV Community: Yubal Torres