NVRtxt & EmailToTxt
SaaSThe major US carriers shut down their free email-to-text gateways, breaking every alert workflow that depended on them. These two products restore it: a machine emails a unique address, the service cleans the alert into a short SMS and forwards it to the phones that need it.
Overview
For years, security installers relied on carrier email-to-SMS gateways to get NVR motion alerts onto a phone. When the carriers retired those gateways, an enormous amount of deployed equipment lost its notification path overnight — the recorders can only send email, and there was nothing left to receive it.
NVRtxt closes that gap. Each customer gets unique inbound addresses; alerts arrive through SendGrid Inbound Parse, hit a decisioning engine that matches the endpoint, applies rate limits and throttling, parses the vendor-specific payload, and dispatches an SMS through Telnyx to every recipient on the endpoint. Everything is logged to an activity feed the customer can audit.
EmailToTxt is the same engine under a second brand, positioned for the general case — any machine, alarm panel, monitoring tool, or legacy system that can only speak email. One codebase, brand resolution handled server-side, two distinct market positions.
Key Features
- Unique per-endpoint inbound email addresses
- Vendor-aware parsers (Uniview, LTS, Dahua, Hikvision) with a generic fallback
- Rate limiting and throttling to prevent alert storms from burning SMS credit
- Multi-recipient dispatch per endpoint
- Full activity log and usage tracking in the customer dashboard
- STOP/HELP inbound SMS compliance handling
- Row-level security so tenants can only ever read their own rows
- Provider abstractions — SMS and inbound email are swappable interfaces
- Two brands served from one deployment, resolved server-side
Tech Stack
Architecture Highlights
Need a legacy workflow rescued?
When a vendor retires the integration your operation depends on, I can rebuild the path — often better than the original.
Start a Conversation