Deploy finished
main → production in 3m 51s. Nobody panicked.
Push notificationsiPhone · iPad · Mac
Push notifications to your iPhone, iPad and Mac from anything that can make an HTTP request. No account, no dashboard, nothing kept on a server.
Deploy finished
main → production in 3m 51s. Nobody panicked.
Backup complete
nas-01 copied 214 GB overnight. You slept through it, as intended.
Claude Code
Refactor done. Waiting on you to say "looks good".
Front door
Package dropped off. Statistically, it is more cables.
Deploy finished
main → production in 3m 51s. Nobody panicked.
Backup complete
nas-01 copied 214 GB overnight. You slept through it, as intended.
Claude Code
Refactor done. Waiting on you to say "looks good".
Front door
Package dropped off. Statistically, it is more cables.
Coffee machine
Brew ready. Morale restored to acceptable levels.
Uptime
api.example.com is back after 42 seconds of drama.
New order
Someone bought the thing. Act casual.
nightly-report.sh
Exited 0. A rare and beautiful sight.
How it works
Grab brrr for iPhone, iPad or Mac. Your webhooks are already inside: one that reaches every device you own, and one for each device on its own. No email, no password, no "verify your account".
POST some text to it. A notification shows up. That is genuinely the whole product.
curl -X POST https://api.brrr.now/v1/YOUR_SECRET \
-d 'The build is green. Go outside.'The secret is the last part of the URL, so treat the link like a password. Leaked it? Rotate it in the app. Prefer GET? Pass message and title as query parameters.
Why brrr
01No sign-up
You already have more accounts than you can remember passwords for. brrr skips the whole ritual: install, copy your webhook, done.
02Not stored
Notifications pass through on their way to Apple’s push service and are not stored server-side. Recent history lives on your device, for as long as you tell it to.
03No dashboard
No console, no charts, no team settings. There is a URL, and you call it. Titles, sounds, images, custom icons and Focus-aware alerts are all just fields in the request.
Integrations
No logo wall. If it can send a request (a shell script, a CI job, a home server, an AI coding agent), it can make your phone buzz.
curl -X POST https://api.brrr.now/v1/YOUR_SECRET \
-H 'Content-Type: application/json' \
-d '{
"title": "Backup complete",
"message": "214 GB, zero drama.",
"thread_id": "backups",
"sound": "bubbly_success_ding"
}'- name: Tell my phone how it went
if: always()
run: |
curl -X POST https://api.brrr.now/v1/send \
-H "Authorization: Bearer ${{ secrets.BRRR_SECRET }}" \
-H "Content-Type: application/json" \
-d '{"title": "${{ github.workflow }}",
"message": "${{ job.status }} on ${{ github.ref_name }}",
"thread_id": "ci"}'import json, os, urllib.request
req = urllib.request.Request(
f"https://api.brrr.now/v1/{os.environ['BRRR_SECRET']}",
data=json.dumps({
"title": "Training run",
"message": "Epoch 40/40. The loss looks smug.",
}).encode(),
headers={"Content-Type": "application/json"},
)
urllib.request.urlopen(req)await fetch(`https://api.brrr.now/v1/${process.env.BRRR_SECRET}`, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
title: "New signup",
message: "Someone actually clicked the button.",
open_url: "https://example.com/admin",
}),
});Also plays nice with
FAQ
Really. Install the app and your webhook links are already there, secret included. That link is the only credential.
From your request, through brrr, to Apple’s push notification service, to your device. They are not stored on the backend. The app keeps recent notifications on-device, and you choose how long each device holds on to them.
Anyone holding it can send you notifications, so rotate the secret in the app and the old link stops working. If your requests pass through systems that log URLs, use the /v1/send endpoint and send the key in an Authorization: Bearer header instead.
Send JSON instead of plain text to set a title, subtitle, sound, thread for grouping, an image, a custom icon, a link to open on tap, an expiration date, Focus filter criteria, and the interruption level, from passive up to time-sensitive and critical alerts.
iPhone, iPad and Mac. You get one webhook that fans out to all of them, plus one per device for when only your Mac needs to know.
Honestly, maybe you shouldn’t. If you need teams, delivery analytics, a web dashboard or Android support, other tools will serve you better. brrr is for people who want one URL that makes their Apple devices buzz and would rather not think about it again.
# One URL. Your devices go brrr.
Push notifications to your iPhone, iPad and Mac from anything that can make an HTTP request. No account, no dashboard, nothing kept on a server.
- [Get it on the App Store](https://apps.apple.com/us/app/brrr-just-push-notifications/id6755617665)
- [Read the docs](https://brrr.now/docs)
Available for: iPhone, iPad, Mac.
## How it works: Two steps. We double-checked.
1. **Install the app.** Grab brrr for iPhone, iPad or Mac. Your webhooks are already inside: one that reaches every device you own, and one for each device on its own. No email, no password, no "verify your account".
2. **Call the webhook.** POST some text to it. A notification shows up. That is genuinely the whole product.
```bash
curl -X POST https://api.brrr.now/v1/YOUR_SECRET \
-d 'The build is green. Go outside.'
```
The secret is the last part of the URL, so treat the link like a password. Leaked it? Rotate it in the app. Prefer GET? Pass message and title as query parameters.
## Why brrr: Less, on purpose.
### No sign-up
**It does not want your email.** You already have more accounts than you can remember passwords for. brrr skips the whole ritual: install, copy your webhook, done.
### Not stored
**Your messages are not kept on the backend.** Notifications pass through on their way to Apple’s push service and are not stored server-side. Recent history lives on your device, for as long as you tell it to.
### No dashboard
**There is nothing to log in to.** No console, no charts, no team settings. There is a URL, and you call it. Titles, sounds, images, custom icons and Focus-aware alerts are all just fields in the request.
## Integrations: Works with anything that speaks HTTP.
No logo wall. If it can send a request (a shell script, a CI job, a home server, an AI coding agent), it can make your phone buzz.
### cURL
```bash
curl -X POST https://api.brrr.now/v1/YOUR_SECRET \
-H 'Content-Type: application/json' \
-d '{
"title": "Backup complete",
"message": "214 GB, zero drama.",
"thread_id": "backups",
"sound": "bubbly_success_ding"
}'
```
### GitHub Actions
```yaml
- name: Tell my phone how it went
if: always()
run: |
curl -X POST https://api.brrr.now/v1/send \
-H "Authorization: Bearer ${{ secrets.BRRR_SECRET }}" \
-H "Content-Type: application/json" \
-d '{"title": "${{ github.workflow }}",
"message": "${{ job.status }} on ${{ github.ref_name }}",
"thread_id": "ci"}'
```
### Python
```python
import json, os, urllib.request
req = urllib.request.Request(
f"https://api.brrr.now/v1/{os.environ['BRRR_SECRET']}",
data=json.dumps({
"title": "Training run",
"message": "Epoch 40/40. The loss looks smug.",
}).encode(),
headers={"Content-Type": "application/json"},
)
urllib.request.urlopen(req)
```
### JavaScript
```js
await fetch(`https://api.brrr.now/v1/${process.env.BRRR_SECRET}`, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
title: "New signup",
message: "Someone actually clicked the button.",
open_url: "https://example.com/admin",
}),
});
```
Also: Claude Code, Codex, Copilot CLI, Home Assistant, n8n, Shortcuts, Uptime Kuma, Zapier. [All guides on Learn](https://brrr.now/learn)
## FAQ
### Do I really not need an account?
Really. Install the app and your webhook links are already there, secret included. That link is the only credential.
### Where do my messages go?
From your request, through brrr, to Apple’s push notification service, to your device. They are not stored on the backend. The app keeps recent notifications on-device, and you choose how long each device holds on to them.
### What if my webhook URL leaks?
Anyone holding it can send you notifications, so rotate the secret in the app and the old link stops working. If your requests pass through systems that log URLs, use the /v1/send endpoint and send the key in an Authorization: Bearer header instead.
### How much can I customize?
Send JSON instead of plain text to set a title, subtitle, sound, thread for grouping, an image, a custom icon, a link to open on tap, an expiration date, Focus filter criteria, and the interruption level, from passive up to time-sensitive and critical alerts.
### Which devices does it work on?
iPhone, iPad and Mac. You get one webhook that fans out to all of them, plus one per device for when only your Mac needs to know.
### Why should I use brrr over something else?
Honestly, maybe you shouldn’t. If you need teams, delivery analytics, a web dashboard or Android support, other tools will serve you better. brrr is for people who want one URL that makes their Apple devices buzz and would rather not think about it again.
---
[Docs](https://brrr.now/docs) · [Learn](https://brrr.now/learn) · [App Store](https://apps.apple.com/us/app/brrr-just-push-notifications/id6755617665) · [Privacy](https://brrr.now/privacy-policy) · [Contact](https://brrr.now/contact) · [llms.txt](/llms.txt)