Skip to Content
Pocket Notifier

Scope

What notifier v1 does, who it is for, and what is deliberately left out.

The problem

Scripts, CI jobs, cron tasks and servers need a quick way to tell a person that something happened, ideally on their phone, with enough context to act on it. Email is slow and noisy, chat apps need bots and workspaces, and hosted push services are either public or another account to manage.

notifier is a small service you own: one HTTP request sends a message, and the people subscribed to that project get a native Android notification within seconds.

Who it is for

You and a small group of people you invite Decided. Everyone shares one deployment on your Cloudflare account. There is no public sign-up, no billing and no multi-tenant isolation.

The main sender is coding agents in T3 Code Decided. They tell you when a task is done, when they need a decision, or when something broke. See Coding agents. Scripts, CI and servers use the same API.

In scope for v1

Out of scope

FeatureWhy not now
Live web viewNeeds long-lived connections, which on Workers means Durable Objects. The dashboard refreshes instead. Later
ntfy API compatibilityOur own API is simpler to keep strict. Scripts that use ntfy need a small change. Decided
Phones without Google Play servicesWould need an always-on connection and a foreground service. Later
Email, SMS or chat deliveryPush to the app is the only channel in v1.
Teams or workspacesPer-project membership covers a small group. Later
iOS appAndroid comes first; the code layout keeps iOS possible. See Mobile.

Success criteria

  1. A curl from a CI job shows up as a notification on an Android phone in under 5 seconds.
  2. Urgent messages (priority 5) pop up and can break through Do Not Disturb if the user allows it.
  3. A subscriber can acknowledge or reply from the notification without opening the app, and the publisher can read that reply through the API.
  4. Nobody can publish or read a project they are not a member of.

On this page