EventSend is an event tracking and routing tool, aimed primarily at developers and product teams who need to stay on top of how their product is running at all times.
In terms of use, the system lets you send important events you want to track to EventSend, such as signups, failed payments, new subscriptions, deployments, new purchases, and more. These events enter a searchable, filterable feed that helps you quickly understand what is currently happening in your product.
For event routing, for important events you need to know about immediately, EventSend can route them via signed Webhooks to your phone, Slack, Discord, Telegram, or other systems and services, so you do not have to wait until they reach Grafana Loki logs to check. You can configure rules, alerts, do-not-disturb periods, or smart digests to get the signal you want.
For reliability, all events are retried with a reasonable backoff strategy, and circuit breakers and rate limiters are used to keep providers and the system stable. When a 401 or 403 is received, the target is not retried; instead it is disabled, and you are notified to update the configuration.
For the tech stack, it mainly uses distributed Elixir, Phoenix, and Postgres, with other technologies supporting the event queue. The author states they have about ten years of software engineering experience, and distributed systems experience is put into practice in this project, making it a reliable system.
For additional capabilities, EventSend provides an MCP connector that can be used to ask questions such as "Were there any failures overnight?" or "What did user cus_Qw3Sx do before churning?" to retrieve user timelines or any insight you are interested in. The author also says they plan to add Microsoft Teams integration next.
For pricing, a permanently free plan is available, and you can try it out.
Use cases include: tracking key product events and retrieving them quickly, routing important events in real time to commonly used notification channels, managing alerts with rules and do-not-disturb settings, and querying events and user timelines in natural language through the MCP connector.
In terms of limitations, the material does not provide specific pricing details, a complete list of supported platforms, API documentation, or concrete steps for integration; this information is not currently available.
