EventSend is event tracking and alert routing for a small SaaS team.
Your product emits things worth knowing: someone signed up, a card was declined, an error spiked, a deploy went out, or broke. Two things have to happen to each one: it has to be recorded somewhere you can go back and look, and the ones that matter have to reach a person now. EventSend does both, which is why it is not quite an analytics tool and not quite a notifier.
Getting events in takes one HTTP POST from any language, with no SDK to install - or no code at all: paste one URL into Stripe, GitHub or Vercel and every payment, push, merged PR, failed CI run or deploy arrives formatted, deduplicated and retried.
Every event then lands in a live feed you can search and filter - by name, level, source, customer, status and date - with operational analytics over the top: volume, levels, error rate, delivery health per destination, and volume by topic and source, with twelve months of history on every plan including Free. Filter to a single customer and you have their timeline: what they did, in order, before they churned. EventSend does not do funnels or user journeys, and does not pretend to.
Routing is the other half. Rules decide where each event goes by name, level and source, so a failed payment wakes your phone while a signup drops into a channel nobody has to watch. Destinations are Slack, Discord and Telegram natively, your own HTTPS endpoint signed with HMAC-SHA256, and Pushover or browser push. Threshold alerts, rollups, quiet hours and digests keep a loud stream readable.
Delivery is verifiable rather than hopeful: retries with backoff, circuit breakers isolating a failing destination, idempotent ingestion, and every attempt recorded with its response.
And because the read side is an MCP server, Claude or ChatGPT can answer "did anything fail in checkout today?" against your real events.
Free forever for 2,500 events a month; paid plans start at $12 flat, with unlimited seats.