Flowalert.io — Case Study
Operational alert routing — if it can send an HTTP request, it can push a notification
We built the full Flowalert product from the ground up: a web app and mobile app that route operational alerts as push notifications to the right person or team. Any system that can fire an HTTP request — monitoring tools, IoT sensors, payment gateways, webhooks — can trigger instant push notifications directly to staff. Built with Next.js for the web dashboard, Expo React Native for iOS and Android, PostgreSQL as the primary database, Redis for queue management and real-time delivery, and a scalable API layer tying it all together.
3
Platforms
Web, iOS & Android
Any
Trigger Sources
HTTP webhook support
Real-time
Delivery
Push notification routing
The challenge
Operations teams live and die by response time, but the alerts that matter are scattered across systems that don't talk to each other — monitoring tools, IoT sensors, payment gateways, internal scripts. Email alerts get buried, group chats get noisy, and the person who could fix an issue often hears about it last.
Flowalert needed to exist as a complete product: a way for any system capable of firing an HTTP request to reach the right person's pocket as a push notification, within seconds, with routing rules teams could manage themselves. That meant building three surfaces at once — a web dashboard, an iOS app, and an Android app — on infrastructure that treats delivery speed as the core feature.
What we built
One API to catch everything
The heart of Flowalert is a webhook-first API layer: any tool that can send an HTTP request can trigger an alert. We designed the ingestion API around that promise — simple to integrate in minutes, strict about validation, and built to accept bursts of traffic without dropping events.
Real-time delivery on PostgreSQL + Redis
Alerts are only useful if they arrive now. We used PostgreSQL as the system of record and Redis for queue management and real-time delivery, so notifications route to the right person or team the moment an event lands — with delivery states tracked end to end.
A dashboard teams can actually operate
The Next.js web app is where teams create alert sources, define routing rules, and manage who gets woken up for what. We kept the mental model simple — sources, routes, people — so a new team can go from signup to their first routed alert without reading documentation.
Native-feeling mobile apps from one codebase
iOS and Android apps built with Expo and React Native share a codebase while keeping push notifications first-class on both platforms. The apps are deliberately focused: receive, acknowledge, and act on alerts — no clutter between an incident and the person handling it.
The outcome
Flowalert shipped as a complete three-platform product: web dashboard, iOS app, and Android app, backed by real-time routing infrastructure. Because the ingestion layer speaks plain HTTP, it integrates with effectively any modern system — monitoring stacks, IoT fleets, payment providers, or a five-line script.
The product is live at flowalert.io. For CreateSwift, it's also the clearest demonstration of what we mean by full-product delivery: architecture, backend, web, and both mobile apps designed and built as one coherent system.