BuzzKit
POST /messages
{
"title": "Leg day",
"body": "Let’s go.",
"topic": "gym-reminders"
}
One clear request.
A compact API story, presented with a real, editable code example.
The Open Source Notification
Orchestration Layer.
Overview
Subscribers, deliveries, events and runs over time.
Subscribers13,460 ↗ 11%
Delivered35,285 ↗ 24%
Events143,380 ↗ 18%
Deliveries
Sent and failed deliveries per day.
Aug 20Aug 22Aug 24Aug 26Aug 28Aug 30Sep 1
‹ Workflows
Trial nudge Active
Once per subscriber, when trial.started fires.
Steps
Steps Runs Code
Runs Once at a time per subscriber
ϟ Triggeron trial.started
⌘ Branchopened-the-app-sinceyes · no
yes
⌛ Waitgive-it-a-dayWait 1 day
no
➤ Sendfirst-class-waitingYour first class is waiting.
‹ Segments
Active pro members
Pro subscribers who trained this week and opened the app this month.
Conditions
Builder JSONSubscribers matching all ⌄ of these conditions
♟ Attributeplanispro
ϟ Did eventworkout.completedat least 3last 7 days
◷ Activityactive in the last30 days
＋ Add condition
Matching now
1,284 subscribers| Subscriber | Country | Channel | Last seen |
|---|---|---|---|
| MMaya Lindqvist | Sweden | iOS | 2m ago |
| TTomás Ferreira | Portugal | iOS | 26m ago |
| AAlex Chen | Canada | iOS | 1h ago |
| SSam Parker | Australia | iOS | 3h ago |
‹ Messages
Leg day Completed
Sent to the gym-reminders topic 12 minutes ago.
Overview
- Title
- Leg day
- Body
- Let’s go. 6:00 with Maya.
- Channel
- Push
- Sent to
- ◆ gym-reminders
Delivery
- Reachable
- 2,418
- Sent
- 2,412
- Pending
- 0
- Failed
- 6
Deliveries
All Sent Failed| Subscriber | Status | Sent |
|---|---|---|
| user_42 | Sent | 12m ago |
| user_311 | Sent | 12m ago |
| user_178 | Sent | 12m ago |
Payload
{
"title": "Leg day",
"body": "Let’s go.",
"topic": "gym-reminders"
}
Illustrative dashboard. Nothing is sent.
Notifications made easy.
One place to connect your events, your audience, and your next message.
Workspace
◈ Orbit ✓
◉ Gymly
▧ Nook
◇ Harbor
Room for every project.
Separate workspaces help keep each product and its audience together.
◐ Apple Push Notification service
◈ Firebase Cloud Messaging
▣ Identity secret
Your keys. Your data.
A place to explain the trust boundary and how you protect customer data.
Everything you need, built in.
Choose who to reach, automate the follow-up, and give people control.
Workflows
Give every event a next step. Build a clear path from a trigger to a wait, a branch, and a message.
Explore workflows →
ϟ trial.started◷ Wait 1 day➤ Send a reminder
Segments
Group your audience by the things they do, then keep those groups up to date.
Explore segments →plan is pro
workout.completed at least 3 ×
active in the last 30 days
↳ 1,284 matching subscribersScheduling
A useful message, at a useful time. Show how your product handles quiet hours and local delivery.
Explore scheduling →| Auckland | UTC+12 | Sent |
| Tokyo | UTC+9 | Sent |
| Berlin | UTC+2 | Sent |
| New York | UTC−4 | 09:00 local |
Topics & preferences
Give people control over what reaches them. Try the local preference switches below.
Explore topics & preferences →
Notifications
Preferences are local to this preview.
Sources
Connect the events your product already creates to the messages your audience needs.
Explore sources →
◈ Stripesubscription.started
◉ RevenueCatsubscription.renewed
▧ Custom eventorder.shipped
Live Activities
Keep progress visible at a glance. Use a compact, ongoing update for the things happening now.
Explore live activities →
Out for delivery
6 stops away · 24 min
Almost there
2 stops away · 6 min
| Attempt | Outcome | Latency |
|---|---|---|
| 1 | Retrying | 412 ms |
| 2 | Retrying | 5,000 ms |
| 3 | Sent | 142 ms |
See what happened to every push.
Turn a delivery log into a clear story: what happened, when it happened, and what comes next.
- Automatic retries
- Delivery and open receipts
- Actionable failure context
Add the SDK. Skip the token management.
Use this space to make setup concrete, with a short example and a link to your real documentation.
Read the original docs →
// Illustrative setup snippet
const client = createClient();
await client.registerDevice();
await client.track('workout.completed');
Open source, top to bottom.
The original BuzzKit project is open source. Explore its code, documentation, and self-hosting guide.
Explore the original project →git clone github.com/buzzkit-dev/buzzkit cd buzzkit # Follow the project's setup guide.
Frequently asked questions
Does this template send real notifications?
No. The dashboard, charts and notification cards are illustrative local demos. No credentials, network requests or messaging services are connected.
What can I interact with?
Choose any of the four dashboard views, pause the presentation, change the local preference switches, open these FAQs, and copy the example snippet.
Can I use this without a framework?
Yes. Open the HTML directly or serve this folder with a static server. The fonts, CSS, JavaScript and artwork are included.
Where are the real BuzzKit docs?
The documentation links point to the original BuzzKit project. This independent reconstruction is a design template, not the BuzzKit application.
How do I make it my own?
Edit the brand and copy in index.html, change the color tokens in style.css, then replace external links with your own destinations. All four dashboard views are editable HTML.
What happens with motion disabled?
The page stays on its initial dashboard view and the notification cards stay still. All manual controls continue to work.
Make the next message count.
Start with the design. Build your own product.