SaaS · Notifications · 2024
ALERTFLEET
A notification relay that lets legacy and IoT systems — which can only send a plain e-mail — reach modern channels like SMS, WhatsApp, and webhooks, with full delivery visibility.
Older alarm systems, home-automation controllers, and other legacy hardware often can only trigger a notification by sending a basic e-mail — and many cannot even do that over a modern, secure connection. This platform relays that single trigger (an e-mail or an API call) out to SMS, WhatsApp, e-mail, and webhook recipients simultaneously, with a legacy-compatible inbound mailbox for systems that predate SSL/TLS support. A “source e-mail builder” tool generates the exact trigger format for a given set of recipients and channels, so connecting a new source system takes configuration, not custom integration work. An alerts-log dashboard shows, per notification, whether delivery succeeded, partially succeeded, or failed — filterable by user, source, status, and date range — and the whole thing runs as a self-service, subscription-billed product with its own user and role management.
- Country
- Italy
- Timeline
- 9 weeks
- Year
- 2024
- Services
- Backend EngineeringIntegrationsFrontendBilling
The challenge
- Legacy systems could send an e-mail but had no path to reach SMS, WhatsApp, or webhook-integrated tools.
- Some source systems used outdated SMTP without SSL/TLS, which most modern services simply reject.
- Operators had no way to confirm whether an alert had actually reached every intended recipient across channels.
- Connecting a new alert source should not require custom integration work every time.
- The product needed to support both non-technical setup (a trigger e-mail) and technical setup (an API call), and needed real subscription billing to be sustainable.
The solution
- A relay layer that fans one inbound trigger (e-mail or API call) out to SMS, WhatsApp, e-mail, and webhook recipients.
- A source e-mail builder that generates the exact trigger e-mail/address format for a given alert's recipients and channels, removing manual integration work.
- An alerts-log dashboard showing per-notification delivery status (pending, success, partial success, error), filterable by user, source type, status, and date range.
- A legacy-compatible inbound mailbox for systems without modern SSL/TLS support.
- Role-based dashboards and user management for teams monitoring alerts.
- Subscription and pricing plans with self-serve billing.
- Bot-protected public signup and contact flows, plus a full auth flow including e-mail verification and password reset.
The results
- Operators get a single dashboard confirming, per channel and per recipient, whether an alert actually delivered — instead of guessing.
- Any legacy system able to send an e-mail can now reach SMS, WhatsApp, and webhook-connected tools without changes on its own end.
- Self-service configuration through the e-mail builder removes the need for engineering support when onboarding a new alert source.
- Subscription billing turns the relay into a sustainable, self-service product rather than a one-off integration job.
A closer look
