<- all tokdocs

Boop: A Self-Hosted Developer Notification Inbox and Its Limits

By , founder of Mavric and Apso

View on TikTok ->

Boop is a small self-hosted Go server that takes events your code sends it and pushes them to an iPhone through Apple's push service. It works for alerts like failed jobs and new signups. It cannot tell you a server went down, and the only phone client is an iOS app you build and sign yourself with a paid Apple Developer account.

What is Boop?

A TikTok from @howtowebdev pitches Boop as a way to get notified "when your background jobs fail, a new user signs up, or a server goes down", straight to your phone, with a simple web request. The project lives at github.com/chrisgreg/boop and is built by Chris Gregori, who lists London as his location.

The README tagline is "A tiny, self-hosted notification inbox for developers." It describes the flow this way: "Your apps POST events with a project API key. The Go server redacts and stores them in SQLite, then pushes straight to Apple's APNs." You send events with a curl call to /api/v1/events and a Bearer key. The README's examples include "Backup complete", "Deploy complete", "Payment received", a KeyError with a stack trace, a shell function that wraps pg_dump, and a GitHub Actions step with if: always().

Can Boop alert you when a server goes down?

No. Boop only receives events. A failing job or a signup handler can call POST /api/v1/events, but a server that has stopped running sends nothing.

The README has no heartbeat, uptime, polling, monitoring or dead-man's-switch feature. Its only health endpoints, GET /health and GET /api/v1/status, report on the Boop server itself. To get a "server down" alert you need a separate watchdog that notices the silence and posts the event. The video does not mention this.

Does Boop work on Android?

No. The only phone client is a SwiftUI app for iOS 26. The README says "you build and sign it", and ios/README.md opens with "You build and sign it yourself with your own Apple Developer account; nothing is distributed through Boop infrastructure."

Issue #3, opened 2026-08-30, asks for Android via FCM and for Web Push. It is still open with no comments. A Web Push pull request (#2) and an outbound webhooks pull request (#4) are also unmerged. If you skip Apple's push service entirely, events "are stored and shown in the UI but pushes are skipped", which leaves you with a web inbox only.

What do you need to run the iOS app?

You need Xcode 26, iOS 26 and a physical iPhone, because "Push notifications do not work in the simulator."

You also need a paid Apple account. Apple's supported capabilities table lists push notifications only for Apple Developer Program and Enterprise Program members, both paid. The free tier cannot use them. The Apple Developer Program costs "$99 annual membership."

On the server side, the README's setup asks for an APNs .p8 key, a Team ID, a Key ID and your bundle ID.

Is Boop really dependency free?

The binary is. The README describes "a static, dependency-free binary for Linux, macOS and Windows (amd64 and arm64)", and the v1.3.0 release ships six archives plus checksums.txt. The Go module declares go 1.27.0 with two direct requirements: modernc.org/sqlite v1.57.0, a pure Go SQLite driver that lets CGO_ENABLED=0 builds work everywhere, and github.com/modelcontextprotocol/go-sdk v1.7.0.

The notification path still runs through Apple's APNs, a third-party service with its own credentials, so the phrase covers less than the video implies.

Is Boop private?

Yes, as far as the README describes it: "There is no hosted relay, account system, or telemetry." The push carries only the title, body and event ID, and the iOS app fetches the full event from your server. Credentials are stored only as SHA-256 hashes, and eleven key names such as password, token, api_key and authorization are replaced with [REDACTED] before storage.

One caveat: admin login is off until you set BOOP_ADMIN_USER and BOOP_ADMIN_PASSWORD. The README says to run it without them "only behind your own proxy, Tailscale, or VPN."

Features the video skips

Since v1.3.0, Boop accepts Sentry SDK envelopes at /api/{id}/envelope/. Any server-side Sentry SDK can report to Boop by changing its DSN to https://boop_proj_...@your-host/1, with no code changes.

Since v1.2.0, it exposes a read-only Model Context Protocol endpoint at /mcp with five tools (list_projects, list_events, search_events, get_event, get_event_group), gated by BOOP_MCP_TOKEN. An AI agent can use it to ask what failed overnight. The README also covers fingerprint grouping, per-rule silences, up to three action buttons per push, and 90-day default retention.

Is Boop maintained?

It was built fast and has been quiet since. The changelog dates v1.0.0 to 2026-08-23, v1.1.0 to 2026-08-28, v1.2.0 to 2026-08-29 and v1.3.0 to 2026-08-30. GitHub shows the repo created 2026-08-28 and last pushed 2026-08-30, with 1,063 stars and 54 forks as of 2026-10-19. No commit has landed since, including PR #5, an iOS fix opened 2026-09-08.

The README badge in the video read "license invalid", which was a temporary badge error. The LICENSE file reads "MIT License, Copyright (c) 2026 Chris Gregori", and GitHub reports MIT. The four client libraries the README links (boop_ex, boop_error_tracker, boop-node, and the community laravel-boop from Solution Forest) all exist and are MIT licensed.

Bottom line

Boop is a clean, private way to push your own app events to an iPhone. It cannot detect a dead server without a separate watchdog, it has no Android or web push client, and the iOS app requires a $99 per year Apple Developer membership. Development stopped after one week of releases in late August 2026.

Sources

Published October 17, 2026. Based on a TikTok by @howtowebdev. Full video notes (markdown)