EventSend is an event tracking and routing tool for solo founders and SaaS teams. Its goal is not to be traditional product analytics or a mere notifier, but to do two things at once: record events that happen in your product so they can be looked up later, and deliver the important ones in real time to the people who should know about them.
Purpose
EventSend fits scenarios where you need to know your product's operating status promptly. Official examples include: user sign-ups, declined cards, error spikes, and deployments that ship or fail. These events both need a paper trail and need to reach the responsible person at the critical moment, avoiding the passivity of, say, learning about a failed charge from the customer rather than from your own system.
Main Capabilities
- Event ingestion: Supports sending events from any language via a single HTTP POST, with no SDK to install; it is also possible to write no code at all and paste a URL into Stripe, GitHub, or Vercel, so payment, push, merged PR, CI failure, or deployment events arrive automatically, formatted, deduplicated, and retried.
- Real-time feed and search: Every event enters a real-time feed that can be searched and filtered by name, level, source, customer, status, and date.
- Operational analytics: Provides event volume, level distribution, error rate, delivery health per destination, and event volume by topic and source. All plans, including the free one, retain twelve months of history.
- Customer timeline: Filter to a single customer to see their timeline and understand what they did, in order, before churning.
- Event routing: Rules based on name, level, and source determine where events go. For example, failed payments can wake your phone, while ordinary sign-ups can go to a channel that needs no human monitoring.
- Native destinations: Slack, Discord, Telegram; plus your own HTTPS endpoint signed with HMAC-SHA256, Pushover, or browser push.
- Noise control: Supports threshold alerts, rollups, do-not-disturb hours, and digests, keeping high-frequency event streams readable.
- Verifiable delivery: Retries and backoff, a circuit breaker that isolates failing destinations, idempotent ingestion, and a record of every delivery attempt and its response.
- MCP read side: The read side is an MCP server, so Claude or ChatGPT can answer questions like "Did anything fail at checkout today?" against your real events.
How to Use
Sending an event requires only one HTTP POST; if you use platforms such as Stripe, GitHub, or Vercel, you can also complete integration by pasting the URL directly. Once events arrive, you can search and filter them in the feed and route them to different destinations through rule configuration.
Use Cases
- Notify users when key product milestones are reached or features become available to them;
- Send reactivation messages to inactive users based on their last login date;
- Trigger an onboarding flow after new users complete registration;
- Remind users in real time about usage limits or account status changes;
- Route important system events (such as failed payments, deployment results, or error spikes) to the appropriate owner.
Limitations
EventSend explicitly does not do funnels or user journey analysis. The material does not provide other limitation details.
Pricing
The free plan is available forever, with 2,500 events per month. Paid plans start at $12/month; if paid annually, it is $10/month, corresponding to 50,000 events. Paid plans include unlimited seats.
Background Information
EventSend is an Instant Launch listed project on Launch Llama, founded by My Tiny Rocket (the founder joined in September 2026), with a total of 96 upvotes, from 88 founder supporters, and compared with 6 alternatives. The material mentions that it is in the Analytics, SaaS, and Developer Tools categories, but the complete features, billing details, and more limitations are not yet provided.
