Today we shipped one of the biggest upgrades to PulseBoard.

    Md_haseeb
    Md_haseeb22d ago

    PulseBoard now understands deployments across:
    ✅ Vercel
    ✅ Render
    ✅ Railway

    When an incident happens, AI shouldn't just tell you that your website is down.

    It should understand what changed.

    Now PulseBoard can correlate deployment activity with incidents to help answer questions like:

    • Was there a deployment just before the outage?
    • Which platform deployed it?
    • What changed around the incident?
    • Is the deployment likely related to the failure?

    This is another step toward the vision behind PulseBoard:

    Less guessing. More evidence-based incident investigation.

    💬42

    Comments (4)

    Sergey Kargopolov
    Sergey Kargopolov21d ago

    Sounds like PulseBoard is becoming better and better every week 👍🏻 Someone is on fire to make it a very successful project! 🙂

    Md_haseeb
    Md_haseeb20d agoReply

    Thank you, Sergey! That really means a lot coming from you.

    I'm trying to make every release solve a real problem for engineering teams instead of just adding features. Still a lot to build, but it's exciting to see the vision coming together. Thanks for all your encouragement!

    Sergey Kargopolov
    Sergey Kargopolov20d agoReply

    ↳ Replying to Md_haseeb

    Yes! That's one of the most exciting feeling when after lots of hours of hard work you see that your "vision coming together". Almost there! :) Three feet away from gold :)

    Stacy Wycoff
    Stacy Wycoff19d ago

    Correlating deployment activity with incidents closes a real gap. The question "was there a deployment right before this" is usually the first thing anyone asks when something breaks, and it is normally scattered across three dashboards. Do you see teams using this mostly to confirm a suspicion they already had, or does it actually surface deployments they had forgotten about?

    Sign in to comment or upvote.