Finb/Bark
Bark
Bark is a self-hosted push notification system for iOS devices that bridges HTTP requests to Apple's Push Notification service. It provides a complete pipeline for sending custom alerts from scripts, cron jobs, or CI pipelines directly to an iPhone, with the server component designed for Docker-based deployment on personal infrastructure.
The system distinguishes itself through automated notification handling capabilities. When a push arrives, Bark can automatically copy the notification body or a custom value to the iOS clipboard, open a specified URL when the user taps the notification, and archive received messages in a local history for later review. These actions are controlled through configurable payload parsing that extracts title, body, and optional parameters from incoming HTTP requests.
The project includes an iOS client app that receives and displays notifications, a notification service extension that processes payloads on the device before display, and a server component that translates HTTP GET or POST requests into APNs payloads. The entire stack is designed for self-hosting, giving users full control over their notification infrastructure without relying on third-party services.
Documentation covers server deployment via Docker, the HTTP API for sending notifications, and configuration of the iOS client's automated actions.
Features
- iOS Push Notification Deliveries - Sends custom messages to an iPhone via HTTP requests, with support for titles, bodies, and automated actions.
- Push Notifications - Provides an HTTP API to send custom push notifications to iOS devices.
- Notification-Triggered - Automatically copies notification content to the iOS clipboard on receipt for quick reuse.
- Notification-Triggered Clipboard Copies - Automatically copies notification content to the iOS clipboard on push receipt for quick reuse.
- Push Notification HTTP APIs - Accepts notification delivery via simple GET or POST requests with query parameters or JSON body.
- Notification Service Extensions - Runs app code on the device to intercept and process incoming push payloads before display.
- Script-Triggered Push Notifications - Triggers notifications from scripts, cron jobs, or CI pipelines to deliver real-time alerts to a mobile device.
- Self-Hosted Deployments - Deploys the notification backend on user-owned infrastructure using Docker for full control.
- iOS Push Notification Clients - An iOS app that receives and displays custom push notifications from a self-hosted or third-party server.
- APNs Bridge Services - Translates standard HTTP POST or GET requests into Apple Push Notification service (APNs) payloads for delivery.
- Self-Hosted - Runs a push notification backend on Docker to send alerts to iOS devices without relying on third-party services.
- Self-Hosted iOS - A server that receives HTTP requests and forwards them as push notifications to iOS devices, designed for self-hosting.
- Push Notification Payload Parsers - Parses incoming HTTP requests to extract title, body, and optional parameters for push notification delivery.
- History Archivers - Ships a local history feature that archives received push notifications for later review.
- Local Persistence - Stores received notifications in a local database on the iOS device for later review.
- URL-Launching Notification Dispatchers - Opens a specified URL in Safari or another app when the user taps the push notification.
- URL Launchers - Opens a specified URL when the user taps a received push notification.
- URL-Launching Notification Handlers - Opens a specified web address when a user taps a received push notification on their iPhone.
- Notification History Centers - Stores received push notifications in a local history log for later review or retrieval.
- Docker Deployments - Packages the notification backend as a Docker container for one-command self-hosted deployment.
