EventSend

EventSend

Event tracking and routing for solo builders and SaaS teams.

mytinyrocket
@mytinyrocket
Published on Sep 25, 2026
Visit site
41 PeerPush
🔥
Awarded
Trending Now
PeerPush
MCP server https://eventsend.io/mcp
API docs eventsend.io

Details

Follow on
@event_send
Pricing
Freemium from $12
Platforms
APIWebMCP

Discovery signals

How AI and people discover EventSend on PeerPush

AI-readyAI-readyWhether this product carries the structured data - use cases, audiences, platforms - that lets AI match it to the right questions.
Structured

Described for AI to match

Described for AI with use cases, audiences, platforms and pricing so assistants can match it to the right questions.
Discoverable nowDiscoverable nowWhether this product is queryable through the PeerPush API and MCP right now.
Live

Via the PeerPush API and MCP

Queryable through the PeerPush API, MCP and semantic search from day one.

About EventSend

EventSend is event tracking and routing for solo builders and SaaS teams. 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. 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?" or "what did user cus_Xs42qAs did before it churned?" against your real events. Free forever for 2,500 events a month; paid plans start at $12 flat, with unlimited seats.

Product Video

Watch a video demo of EventSend.

Screenshots

Screenshot 1 of EventSend
Screenshot 2 of EventSend
Screenshot 3 of EventSend
Screenshot 4 of EventSend
Screenshot 5 of EventSend
Screenshot 6 of EventSend
Screenshot 7 of EventSend
Screenshot 8 of EventSend

Reviews (2)

Average 5.0 out of 5

5.0

Based on 2 reviews

5
2
4
0
3
0
2
0
1
0
nckbrz

The event routing focus is clear, and the single HTTP endpoint plus searchable history sounds practical for small teams.

Comments (3)

omribenshoham
@omribenshoham

Event tracking infrastructure that's instantly useful - live HTTP webhooks, searchable history, and clean JSON formatting remove the friction of debugging payment failures and customer flows without vendor lock-in

nckbrz
@nckbrz

The no-SDK HTTP setup is approachable; customer timelines and verifiable delivery should make debugging failed payments much less stressful.

mytinyrocket
@mytinyrocket

Hi, the reason behind EventSend is that I hated learning about failed payments from customers and not from my apps, so I built a reliable system that tracks all important events and alert when needed.