# Ahem: event inbox and phone notifications for your apps

Source: https://useahem.com

[**New** People, timelines and funnels](https://useahem.com/changelog#2026-11-15)

Event inbox for developers

# The inbox for everything your code wants to tell you.

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.

[Start free](https://app.useahem.com/sign-in) · [Read the API docs](https://app.useahem.com/docs)

Free plan: 3,000 events a month · No credit card · No SDK to install

*Picture: The Ahem web inbox across four projects, with a new subscription arriving at the top, a thread of three failed card payments and an AI agent waiting for input. Beside it, an iPhone lock screen showing the same events as notifications, stacked per project.*

The problem

## Your Telegram bot was a good idea. Until your second app.

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.

### 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.

### All or nothing.

Mute the chat and miss the outage, or keep it loud and get buzzed for every signup at 3 a.m.

### No memory you can query.

A message is a string. You can’t filter by app or severity, or ask “how much did we make this week?”

### Fragile formatting.

One unescaped dot in an email address and Telegram’s MarkdownV2 refuses the whole message.

[Compare Ahem with a Telegram bot](https://useahem.com/vs/telegram-bot)

Three steps

## How it works

1.  ### Send
    
    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.
    
2.  ### Sort
    
    Ahem files it into a channel inside its project. Name a new channel in the URL and it is created on the spot.
    
3.  ### Notify
    
    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**

```sh
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**

```js
// 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" },
  }),
});
```

**Python**

```python
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**

```php
<?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);
```

202 Accepted · Filed in Habit Pocket · #payments · your phone buzzed

Paste it with your own key and this exact request works. [Get a free key](https://app.useahem.com/sign-in)

Inbox and search

## Every event, searchable. Not just the last fifty.

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.

-   ### Filters that read like a sentence
    
    `type:payment.*` matches every payment event.
    
-   ### Threads
    
    Send a `group` and related events stack: deploy started, migrated, done.
    
-   ### Read it from code too
    
    The same search is in the API, for your scripts (`GET /v1/events`).
    

[How search works](https://app.useahem.com/docs)

*Picture: The Ahem web inbox filtered to payment errors from Pro customers, showing a thread of three failed card payments.*

Notification rules

## Buzzes with manners

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.

-   ### Errors can get through Focus
    
    On iPhone, errors use time-sensitive delivery, which Focus modes let through unless you turn that off. Everything else respects Focus.
    
-   ### The sender can insist, or whisper
    
    Mark an event `loud` to skip the level check, or `silent` for backfills and high-volume events. Off still wins over loud.
    
-   ### Notifications stack per project
    
    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).

#signups

Task Pocket · your notifications

info · success · warning · error

**Every event** · For rare, high-value events like payments.

**Warnings and errors (chosen)** · Success and info wait in the inbox.

**Errors only** · For busy channels you still want to hear about when they break.

**Off** · Still stored and searchable. Your phone stays quiet.

In the last 24 hours this rule would have sent **2 pushes instead of 38.**

*Picture: The notification rule of a signups channel set to warnings and errors, with the note that in the last 24 hours it would have sent 2 pushes instead of 38.*

People

## See everything one user did

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.

-   ### Support in one click
    
    Before you reply to an angry email, see what actually happened to that person.
    
-   ### Spot churn early
    
    A failed payment, then two errors, then a 2★ rating is a pattern you can see at a glance.
    
-   ### Debug with context
    
    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.

[How user timelines work](https://useahem.com/features/user-timeline)

*Picture: A user timeline in Ahem: one customer’s signup, upgrade, a sync error and her feedback, in time order.*

Counters and overview

## Numbers you’d otherwise build a dashboard for

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.

Signups today

42

▲ 18% vs last Monday

Revenue this week

$2,184

▲ 9% vs last week

Errors today

3

Same as last Monday

Feedback this month

27

▲ 4 vs last month

Example numbers. Up to 12 counters per project, plus a chart of events over time by level, your top types and channels, and funnels on Maker. Export everything as JSON whenever you like.

Phone, widgets, browser

## On your phone, your lock screen, your 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.

-   iPhone app · (Beta)
-   Android app · (Beta)
-   Home and lock-screen widgets · (Beta)
-   Browser push · (Live)

Push goes straight to Apple and Google. No third service in between.

*Picture: An iPhone lock screen with Ahem notifications grouped by project, and widgets showing today’s signups and the latest events.*

Use cases

## What people send to Ahem

### New signups

Know who joined, from where, on which plan.

user.registered

### Payments

Feel every sale, and hear about failed renewals before the customer does.

payment.received

### Errors

The ones worth hearing about, with the link to the logs.

db.connection\_failed

### [AI agents](https://useahem.com/guides/claude-code-notifications)

Claude Code or Codex finished, or is waiting for you.

agent.task\_completed

### Deploys and CI

A failed GitHub Action reaches your phone, not your inbox tomorrow.

deploy.failed

### Cron jobs

Backups, imports and reports that report back.

cron.backup\_completed

### Feedback

Ratings and messages from inside your app.

feedback.created

### Leads

Demo requests and contact forms, while they’re warm.

lead.created

Noise calculator

## How noisy is your phone today?

Tell us roughly what your apps send in a day. We’ll show how many times each approach would buzz you.

Signups a day

Payments a day

Errors a day

Other events a day

Buzzes a day
| Approach | Buzzes a day |
| --- | --- |
| Telegram bot or Slack channel (unmuted) | 203 |
| Ahem, suggested rules  
Payments: every event. Errors: errors only. Signups and the rest: off. | 13 |
| Ahem with burst grouping (Soon) | Fewer still |

**203** events, **13** buzzes. Everything else is in your inbox when you want it.

Compare

## How Ahem compares

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](mailto:support@useahem.com).

[See all comparisons](https://useahem.com/compare)

Pricing

## Simple pricing

### Free

For your first app, or to try Ahem out.

$0forever

$0forever

No credit card.

-   2 projects
-   3,000 events a month
-   7 days of history
-   Channels, levels and notification rules
-   Search, threads, counters and export
-   People and user timelines
-   Web app and browser push
-   iPhone and Android apps (Beta)

[Start free](https://app.useahem.com/sign-in)

### Maker

For makers with a few apps that earn money.

$12a month

$120a year

That's $10 a month, or $12 billed monthly. · Or $120 a year: 2 months free.

-   Unlimited projects
-   100,000 events a month
-   1 year of history
-   Details on people (plan, country, MRR)
-   Watch a customer: hear about their events
-   Funnels on the overview
-   Everything in Free

[Start free, upgrade in the app](https://app.useahem.com/sign-in)

Over your limit? Events are still stored; only notifications pause until next month or an upgrade.

[Full pricing](https://useahem.com/pricing)

Roadmap

## Coming next

Ahem is new and moving fast. Here is what’s being built, in order. No dates we can’t keep.

[Changelog](https://useahem.com/changelog)

1.  01 · Sign in with GitHub · (Soon)
2.  02 · Sign in with Apple · (Soon)
3.  03 · Burst grouping: "9 new signups" instead of 9 pushes · (Soon)
4.  04 · Quiet hours that still let errors through · (Soon)
5.  05 · Rules per event type (payment.failed loud, invoice.\* silent) · (Planned)
6.  06 · Custom sounds (cha-ching for payments) · (Planned)

From the maker

## Why I built Ahem

> “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.”
> 
> **Bohdan Stefaniuk**  
> Maker of Ahem · [About](https://useahem.com/about)

FAQ

## Questions

Something else? Write to [support@useahem.com](mailto:support@useahem.com).

**Do I need an SDK?**

No. Ahem is one HTTP request with a JSON body, so curl, fetch, requests, or any HTTP client works. The app gives you ready-made examples for curl, Node, Python and PHP, with your key filled in.

**What happens if I go over my plan’s events?**

Ahem keeps storing your events and only pauses notifications until the next month or an upgrade, so a good day never breaks your app. At ten times the quota new events are refused until then.

**Which apps are there?**

A web app with browser notifications, and native apps for iPhone and Android (in beta). On iPhone, widgets show today’s counters and your latest events on the home and lock screen.

**Can I stop my phone buzzing for every signup?**

Yes. Each channel has a rule for your devices: every event, warnings and errors, errors only, or off. Events that don’t notify still land in your inbox. Grouping bursts into one notification is coming soon.

**Can my AI coding agent notify me?**

Yes. Claude Code, Codex and any agent that can run a command can send an event when a task finishes or needs your input. See the [Claude Code guide](https://useahem.com/guides/claude-code-notifications).

**Is there a free plan?**

Yes: 2 projects, 3,000 events a month and 7 days of history, with no credit card. Maker is $12 a month or $120 a year for unlimited projects, 100,000 events a month and a year of history.

**Can I keep using Telegram or Slack?**

Not yet from inside Ahem. Forwarding chosen events to Telegram, Slack, Discord, email and webhooks is planned. Today you can keep your bot running alongside Ahem.

**Where is my data stored?**

In Canada: Ahem runs on DigitalOcean in Toronto. Event bodies and metadata are stored so you can search them; send an id rather than an email if you’d rather not store personal data. We never sell data. See the [privacy policy](https://useahem.com/privacy).

**Can I export or delete my data?**

You can export a whole project as JSON at any time, and delete single events, people, channels or projects.

**How is Ahem different from LogSnag or Pushover?**

Pushover delivers pushes but keeps no searchable history. LogSnag keeps a feed but has no severity levels or per-channel rules. Ahem does both. [Full comparison](https://useahem.com/compare).

## Send your first event in two minutes.

Sign up, copy your key, paste one curl. Your first notification arrives before your coffee cools.

[Start free](https://app.useahem.com/sign-in) · [Read the API docs](https://app.useahem.com/docs)
