Md_haseeb1mo ago

What's New in PulseBoard?

We've been shipping hard and just added three major features to PulseBoard — an AI-powered uptime monitoring platform that explains why your website or API broke.

🆕 New Features:

💬 Slack Integration

Send incident alerts directly to your Slack channels
Recovery notifications when services come back online
Configurable reminders at 15, 30, or 60-minute intervals
Multiple channels per workspace
Toggle integrations on/off with one click

👥 Team Collaboration & Organizations

Multi-tenant organizations with role-based access
Invite team members as Admins or Members
Admins manage integrations, invite members, and configure workspace settings
Members can view incidents and collaborate

⏰ Incident Reminders

Never lose track of ongoing incidents
Configurable at 15, 30, or 60-minute intervals
Reminders stop automatically when the incident resolves
No manual intervention needed

💬4△1

Clarity AI

AI analytics that doesn't wait for you to ask the right question.

Free

★★★★★0.00.0 (0)

PromotedPromoted as part of the Growth package

Comments (4)

Olga Kargopolova1mo ago

As someone dealing with an automation incident right now that went unnoticed for 2 days before I caught it yesterday, I really see the value of what PulseBoard is building. Slack notifications and incident reminders would have saved me a lot of stress this week. Keep shipping, Haseeb!

Md_haseeb1mo agoReply

thank you, this really means a lot.

Hearing that you caught something 2days late hits home that's the exact scenario I wanted to fix. 2day old incidents shouldn't be a discovery they should be a notification you can't miss.

The Slack + Reminders combo came from that exact frustration. One ping in Slack when it happens, then a gentle reminder every 15/30/60min until it's resolved — so it's not forgotten, but also not screaming at you every 2 minutes.

Would love to hear what would make this actually useful for your workflow. Feature requests are always open!

Stacy Wycoff24d ago

The role-based access piece is easy to undersell, but it is probably the most requested feature nobody asks for by name. Once more than one person needs to see incidents, someone always ends up as the unofficial single point of failure who has to relay everything by hand. Olga's two day gap is the exact failure mode reminders are built for, the alert did fire once, it just got lost in the noise before anyone looked twice. A ping that repeats until someone acknowledges it is a different guarantee than a ping that only tries once.

Md_haseeb24d agoReply

Exactly,. I think that distinction between “the alert was sent” and “someone actually acknowledged the incident” is really important.

Right now PulseBoard focuses on making sure an ongoing incident doesn't disappear after the first notification. But the natural next step is to make the reminder flow more acknowledgment-aware — once someone takes ownership, the reminders should adapt instead of continuing blindly.

And you're right about role-based access too. It seems like one of those features that becomes essential as soon as a team grows beyond one person, even if nobody initially asks for it by name.