Show HN: Eventkiwi – Scheduled reports for your app's events Eventkiwi launched as a hosted event-reporting service that ingests events through a single HTTP GET or POST request, aggregates counts per event and tag, and delivers scheduled reports by email or Telegram, each opening with an AI-generated summary built on the counted figures. The service requires no SDK or hosting, supports hourly, daily, weekly or monthly schedules in the user's timezone, and claims each schedule before sending so overlapping runs cannot deliver the same report twice; failed deliveries carry the period's events into the next report. Eventkiwi offers a free 100-event trial and plans of 10,000 events per month (about 330 a day) and 50,000 events per month (about 1,650 a day), with every feature included on all plans. Send events from any service through one API. Eventkiwi aggregates them, compares each period with the ones before and delivers a scheduled report by email or Telegram, opening with an AI summary built on exact numbers. No credit card. Every feature included. If your code can make an HTTP request, it can use Eventkiwi. There is no SDK to install and nothing to host. Step 1 One GET or POST from your backend, app or no-code tool. Extra parameters become tags, like the plan someone bought. curl "https://app.eventkiwi.com/api/event\ ? id=AGGREGATOR ID& apikey=API KEY\ &name=order paid&plan-pro" Step 2 Each aggregator collects one project’s events and keeps a running count per event and tag, with a dashboard and event log if you want to look. My shop Daily at 08:00 · Europe/Berlin Step 3 Hourly, daily, weekly or monthly, in your timezone. By email, to a Telegram chat, or both. No dashboard to remember to open. See what a report looks like reports . The report is the product. It is written to be read in thirty seconds, not explored. Daily report · My shop Orders up 12% on Monday, two thirds of them on the Pro plan. Signups are flat. Failed payments halved, down to 9. | Event | Count | Change | |---|---|---| | order paid | 184 | +20 +12% | | user signup | 212 | +3 +1% | | payment failed | 9 | −10 −53% | | refund requested | 8 | +1 +14% | Total: 413 events Daily report — My shop Illustration with sample data. Every report opens with a sentence or two on what moved and what didn’t, so you can read it on your phone and move on. A quiet Sunday or a public holiday is called what it is, and compared with the same weekday a week earlier rather than with Friday. Each event shows its count, the change since the last report, and a small trend line. Telegram gets a grid of trend charts. Add tags like plan-pro or source-google to an event and the report splits the count by them. Hourly, daily, weekly or monthly, sent at the local time you pick. Send each report to one or several channels, and test-send to check a channel before relying on it. Not page views or stack traces: those belong in your analytics and error tracker. Send the handful of business events you care about and let the report tell you when they move. order paid cart abandoned refund requested “Orders down 9% on last Saturday, all of it on mobile checkout. Refunds unchanged.” user signup trial converted subscription cancelled “Signups up 18% after the launch post; trial conversions steady at 31. Two cancellations, both on the Starter plan.” lead form sent booking made “Client sites sent 42 leads this week, 11 of them from the new landing page.” import finished sync failed invoice sent “Nightly import finished as usual. Sync failures jumped to 14, all from the same supplier feed.” Every plan includes every feature. Only the number of events differs. Try it with 100 events, on the house. 100 events, one time Enough to see your first real reports Enough to wire up an aggregator and see a real report land in your inbox. 10,000 events / month About 330 events a day For a product in production that you actually watch. 50,000 events / month About 1,650 events a day For teams running several services at once. If you stop opening dashboards, the report has to show up, on time, with the right numbers. A schedule is claimed before it is sent, so overlapping runs cannot send you the same report twice. If a delivery fails, the period’s events are kept for the next report instead of being dropped. You get one email when your event allowance is used up, rather than finding a gap in your reports later. Send a sample report to an inbox or chat to check it arrives before you depend on it. Create an aggregator, send one request, pick a schedule. Short on time? We’ll wire it up for you.