Hey everyone,
I’m the solo founder of ClockingPulse, and I’m a little terrified to be hitting publish today, but here we go.
Over the last year, I found myself dealing with a massive headache that I'm sure a lot of you have experienced: my observability stack was a total mess. I was using one tool to ping my uptime, another tool for cron jobs, logging into the AWS console directly (and praying) to check my billing, and dealing with PagerDuty for alerts.
It was fragmented, expensive, and stressful. I just wanted a single, clean dashboard that told me:
Is my site up?
Did my scheduled database backup run?
Is my AWS bill suddenly spiking because I left a NAT Gateway running?
When I couldn't find a lightweight, affordable tool that did all three cleanly, I spent the last few months building ClockingPulse (clockingpulse.com).
The Stack: I built it on Next.js and Supabase. The coolest part is the Incident Playbooks—if your site goes down, it doesn't just alert you, it instantly loads a markdown playbook for your team so they know exactly what commands to run to fix it.
....
I’m launching the MVP today. Because this community knows SaaS and infrastructure better than anyone else, I would be incredibly grateful for your brutal, unfiltered feedback.
Does the UI look clean? Is the setup actually as easy as I think it is? (You should be able to get a monitor running on the free tier in about 60 seconds).
If you have a spare 5 minutes to poke around and tear it apart, it would mean the world to me.
Link: clockingpulse.com
Thanks so much!
This hits — I’ve definitely been in that exact situation of juggling 4–5 tools and still not feeling in control.
The problem is very clear, which is good. Uptime + cron + billing in one place already makes sense without overexplaining.
What stands out to me is the Incident Playbooks. That’s actually different. Most tools just say “something broke” and then you’re on your own. Having “here’s what to do right now” built in is реально useful.
A couple honest thoughts:
Overall it feels like a solid, focused MVP. Not trying to do too much, just cleaning up a messy part of running apps.
I like that the value proposition isn't "more observability"—it's reducing the number of decisions someone has to make when something goes wrong. Incident playbooks especially stand out because an alert only tells you there's a problem; knowing the next step is what actually shortens downtime. That feels like a more meaningful distinction than just replacing another monitoring tool.
Thanks a lot! That's exactly what I was aiming for. Alerts are only useful if they help you fix the problem faster. Really appreciate you taking the time to share your thoughts. 🙌
That's exactly why I wanted to continue the conversation.
Reading your reply, I think there's one strategic business decision sitting underneath that distinction which becomes much more significant as the product evolves, but I don't think I can do the reasoning behind it justice in a thread.
Happy to explain what I mean if it's useful. What's the best email to reach you?
I would love to hear your thoughts! You can reach me at [email protected]
or shoot me a DM on Twitter at https://x.com/ClockingPulse
. Looking forward to hearing what you think!
Just sent it over by email.
Looking forward to hearing your thoughts once you've had a chance to read it.