One endless scroll.
Signups, payments and stack traces arrive in the same chat with the same weight. The sale you care about is buried under forty “user logged in” messages.
Event inbox for developers
Send an event with one HTTP request. Ahem files it into the right channel, keeps it searchable, and buzzes your phone only for the channels and levels you chose.
Free plan: 3,000 events a monthNo credit cardNo SDK to install
The problem
A bot that posts to a chat is free and takes ten minutes. That’s why so many of us start there. Then the chat fills up.
Signups, payments and stack traces arrive in the same chat with the same weight. The sale you care about is buried under forty “user logged in” messages.
Mute the chat and miss the outage, or keep it loud and get buzzed for every signup at 3 a.m.
A message is a string. You can’t filter by app or severity, or ask “how much did we make this week?”
One unescaped dot in an email address and Telegram’s MarkdownV2 refuses the whole message.
Three steps
POST an event from anywhere: a signup handler, a webhook, a cron job, a GitHub Action, an AI agent. Title, level, type, and any metadata you like.
Ahem files it into a channel inside its project. Name a new channel in the URL and it is created on the spot.
Each channel has a rule for your devices: every event, warnings and errors, errors only, or nothing. Everything else waits quietly in your inbox.
Works from any language that can make an HTTP request. Retries are safe with an Idempotency-Key.
curl https://api.useahem.com/v1/channels/habit-pocket/payments \
-H "Authorization: Bearer ak_live_…" \
-H "Content-Type: application/json" \
-d '{
"title": "New subscription · $12/mo",
"level": "success",
"type": "payment.received",
"user": { "id": "u_381", "name": "Anna K." },
"metadata": { "amount": 12, "plan": "pro" }
}'// Node 18+, no SDK needed
await fetch("https://api.useahem.com/v1/channels/habit-pocket/payments", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.AHEM_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
title: "New subscription · $12/mo",
level: "success",
type: "payment.received",
user: { id: "u_381", name: "Anna K." },
metadata: { amount: 12, plan: "pro" },
}),
});import os, requests
requests.post(
"https://api.useahem.com/v1/channels/habit-pocket/payments",
headers={"Authorization": f"Bearer {os.environ['AHEM_KEY']}"},
json={
"title": "New subscription · $12/mo",
"level": "success",
"type": "payment.received",
"user": {"id": "u_381", "name": "Anna K."},
"metadata": {"amount": 12, "plan": "pro"},
},
timeout=5,
)<?php
$ch = curl_init('https://api.useahem.com/v1/channels/habit-pocket/payments');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 5,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('AHEM_KEY'),
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => json_encode([
'title' => 'New subscription · $12/mo',
'level' => 'success',
'type' => 'payment.received',
'user' => ['id' => 'u_381', 'name' => 'Anna K.'],
'metadata' => ['amount' => 12, 'plan' => 'pro'],
]),
]);
curl_exec($ch);Paste it with your own key and this exact request works. Get a free key
Inbox and search
Ahem keeps every event for 7 days on Free and a year on Maker. Search titles and bodies, then narrow by project, channel, level, type, user or any metadata value. Events that share a group thread together, so twenty retries of one failure are one row, not twenty.
type:payment.* matches every payment event.
Send a group and related events stack: deploy started, migrated, done.
The same search is in the API, for your scripts (GET /v1/events).
Notification rules
The question Ahem is built around: did your phone buzz for the right things? Every channel has its own rule, and every person on a project sets their own.
On iPhone, errors use time-sensitive delivery, which Focus modes let through unless you turn that off. Everything else respects Focus.
Mark an event loud to skip the level check, or silent for backfills and high-volume events. Off still wins over loud.
On iPhone, each project’s notifications group together, so a busy morning reads as a few piles, not forty banners.
Coming soon: burst grouping (“9 new signups” in one push) Soon and quiet hours that still let errors through Soon.
In the last 24 hours this rule would have sent 2 pushes instead of 38.
People
Add a user to the events you already send, and Ahem gives every customer a timeline: signed up, started a trial, upgraded, hit an error, left feedback, in order. No analytics SDK and no extra setup.
Before you reply to an angry email, see what actually happened to that person.
A failed payment, then two errors, then a 2★ rating is a pattern you can see at a glance.
The error, and the five events before it, for the person who hit it.
"user": { "id": "u_381", "name": "Marta P." }Send an id instead of an email if you prefer not to store personal data.
Counters and overview
Turn events into numbers without writing a query. A counter counts events, or sums a number from their metadata, for today, this week or this month, and compares it with the same point last period.
Phone, widgets, browser
A native app for iPhone and Android, with notifications that stack per project. Widgets show today’s counters and the latest events without unlocking. On a laptop, the web app sends browser notifications.
Push goes straight to Apple and Google. No third service in between.
Use cases
Know who joined, from where, on which plan.
user.registeredFeel every sale, and hear about failed renewals before the customer does.
payment.receivedThe ones worth hearing about, with the link to the logs.
db.connection_failedClaude Code or Codex finished, or is waiting for you.
agent.task_completedA failed GitHub Action reaches your phone, not your inbox tomorrow.
deploy.failedBackups, imports and reports that report back.
cron.backup_completedRatings and messages from inside your app.
feedback.createdDemo requests and contact forms, while they’re warm.
lead.createdNoise calculator
Tell us roughly what your apps send in a day. We’ll show how many times each approach would buzz you.
Compare
The short version. The full tables, with sources and dates, are on the comparison pages.
| Ahem | Telegram bot | Pushover | LogSnag | |
|---|---|---|---|---|
| Native phone app | ✓ iOS and Android Beta | ✓ (Telegram) | ✓ iOS, Android, desktop | ✓ |
| Searchable history | ✓ 7 days free, 1 year on Maker | Text search in the chat | — | ✓ |
| Severity levels | ✓ 4 levels | — | Priorities −2 to 2 | — |
| Rule per channel | ✓ per channel, per person | Mute or not | Quiet hours on the device | Sender sets notify per event |
| User timeline | ✓ | — | — | ✓ journeys |
| Price to start | Free | Free | 30-day trial, then $4.99 once per platform | Free |
Checked 15 November 2026. Prices and features change; tell us if something is out of date: support@useahem.com.
Pricing
For your first app, or to try Ahem out.
No credit card.
For makers with a few apps that earn money.
That's $10 a month, or $12 billed monthly.Or $120 a year: 2 months free.
Over your limit? Events are still stored; only notifications pause until next month or an upgrade.
Roadmap
Ahem is new and moving fast. Here is what’s being built, in order. No dates we can’t keep.
From the maker
“I run a handful of small apps, Habit Pocket and Task Pocket among them. For years their signups, payments and crashes went to one Telegram chat. I muted it within a week, and then missed a payment outage for a whole morning. Ahem is the tool I wanted: every event kept and searchable, and my phone only buzzing for the things I’d actually get up for. I use it every day for my own apps.”
Sign up, copy your key, paste one curl. Your first notification arrives before your coffee cools.