pingground

pingground is an inbox for the notifications your own scripts, servers, and services send you — and the only one that can ask you a question back. INBOX Every notification lands in an inbox named after, and pictured with, the application that sent it. Read the full text, see the image, and open a labeled link. Search everything, filter to unread or to questions still waiting on you, and mark all as read. Time-sensitive messages keep their tint and symbol. Read markers stay on this device and are never reported to the sender as delivery receipts. QUESTIONS A notification can ask you something and wait for the answer. Two to four choices, a plain No/Yes, or a typed reply. Answer in the app, straight from the notification's actions, or on the web: the first answer the server accepts is final everywhere, on every device. Questions expire on a deadline the sender chooses, thirty minutes by default and anywhere from one minute to twenty-four hours. Senders poll for the result or receive a signed webhook. Opening, reading, dismissing, or letting a question expire is never counted as an answer. PLAYGROUND Compose an alert once, try it locally on the spot, then send the same draft through the real Apple Push Notification service. Before anything is sent you see the canonical JSON the server will actually transmit, the provider headers, and the exact UTF-8 payload byte count against the 4096-byte ceiling. Invalid payloads are rejected before APNs is contacted, naming the exact field to fix. Save drafts you keep reaching for as templates. HONEST SEMANTICS Most push tooling tells you a send "succeeded." pingground refuses to overstate. A local test says the device accepted a local request. A remote test says APNs accepted the provider request. Neither is reported as proof that a notification was presented on a screen, because an APNs 200 does not mean that. Every send is kept with its request time, target, APNs identifier, HTTP status, rejection reason, and whether the device token was invalidated. A NOTIFICATION SERVICE FOR YOUR SCRIPTS Create an application, issue an API credential, and let your cron jobs, CI runs, deploy scripts, and webhooks notify your phone over a simple HTTP API. The credential is shown once and never again. A retried request can opt into a 24-hour idempotency contract so an uncertain send is never duplicated. Uptime Kuma works through one dedicated preset adapter. CONSENT IS THE ONLY ADDRESS Notifications can never be addressed by device token, installation, or user ID — only through a consent edge the recipient created. You subscribe yourself to an application from your own signed-in surface. That grant carries your own hourly and daily caps and a mute switch, and one tap revokes it. Connected Applications in Settings lists every application allowed to notify you, when each last sent, and the limits you set. WEB DASHBOARD The same account signs in on the web for application, credential, subscription, inbox, device, and account management, plus the public API reference. PRIVACY Sign in with Apple is the only sign-in. There is no advertising, tracking, or analytics SDK. Sent and received history is retained for 30 days. pingground keeps the provider facts needed to debug a send and does not log credentials, raw device tokens, or payload data it does not need. Sign out, unregister a device, or delete your account and its server data outright from inside the app.