EventSend is an event tracking and routing tool for indie developers and SaaS teams, positioned between analytics tools and notification tools. The core problem it solves is this: products generate a large number of noteworthy events, such as someone signing up, a card being declined, a spike in errors, or a deployment being released or failing. Each event needs two things to happen at the same time - being recorded so it can be reviewed later, and the important ones being delivered immediately to the relevant people. EventSend does both at the same time.
Main capabilities
Event ingestion: To capture events, you only need to send a single HTTP POST from any language, with no SDK installation required. You can also avoid writing code entirely: paste a URL into Stripe, GitHub, or Vercel, and every payment, push, merged PR, failed CI run, or deployment arrives formatted, deduplicated, and retried.
Event viewing and analytics: Every event enters a searchable, filterable real-time feed, with filtering by name, level, source, customer, status, and date. On top of the feed, operational analytics are provided: event volume, level, error rate, delivery health for each destination, and event volume statistics by topic and source. All plans, including the free plan, provide twelve months of history.
Customer timeline: Filter to a single customer to view their timeline, showing in order the trajectory of that customer's behavior before churn.
Event routing: Rules determine where each event is sent based on name, level, and source, so a failed payment can wake up your phone while signup events go to an unattended channel. Native destinations include Slack, Discord, and Telegram, and it also supports sending to your own HTTPS endpoint with HMAC-SHA256 signing, as well as Pushover or browser push. Threshold alerts, digests, quiet hours, and summaries help keep high-frequency event streams readable.
Delivery verification: Delivery is verifiable rather than merely hoped for. Retries with backoff, a circuit breaker that isolates failing destinations, idempotent ingestion, and logging of every delivery attempt and its response.
MCP queries: Because the read side is an MCP server, Claude or ChatGPT can answer questions about real events, such as "Did any checkouts fail today?" or "What did user cus_Xs42qAs do before churning?"
How to use
Ingest events: Send an HTTP POST from any language, or paste the URL provided by EventSend into platforms such as Stripe, GitHub, and Vercel.
View and search: InSearch and filter events in a real-time feed, using operational analytics and customer timelines for troubleshooting.
Configure routing: write rules by name, level, and source to dispatch events to Slack, Discord, Telegram, Pushover, browser push, or your own HTTPS endpoint.
Alerts and summaries: set threshold alerts, rollups, quiet hours, and summaries.
Query: let Claude or ChatGPT answer questions based on real events through the MCP server.
Use cases
EventSend is aimed at indie developers and small SaaS teams, especially those who do not want to build a heavy analytics stack, want to quickly get payment failure alerts and customer behavior timelines, and want a unified view of event pipelines across multiple products.
Limitations and notes
Regarding the retry duration for failed webhooks, the official response says it depends on the error type: 401 or 403 will deactivate the destination and notify you to fix it; other errors are retried for up to 15 minutes (this is being made configurable), and can be manually replayed from the dashboard.
Pricing: the free plan includes 2,500 events per month and is free forever; paid plans start at $12 per month with unlimited seats. Detailed limits for other features are not yet provided.
