Launching today
vibePulse
Keep your vibe-coded apps alive while you sleep
4 followers
Keep your vibe-coded apps alive while you sleep
4 followers
You vibe-coded an app, a bot, or a cron job. It shipped, it worked, you moved on. Then one night it dies quietly — a worker crashes, a deploy breaks, an endpoint starts 500ing — and nobody notices until users complain. vibePulse watches your stuff and wakes you first. Paste a URL and we probe it on a schedule, or drop one line into your worker/cron for a dead-man's-switch. When something goes quiet, you get pinged on Slack, Discord, Telegram. 5-minute setup. 1 monitor free, no card required.
Hey Product Hunt! 👋 I'm goodtek, the solo maker behind vibePulse.
I kept shipping small side projects fast — and then quietly breaking them. A cron job would silently die, an API would 500 at 2 a.m., and I'd only find out when someone else told me. Existing uptime tools felt like they were built for ops teams, not for someone who just wants to know "is my thing still alive?"
So I built vibePulse: dead-simple "is it alive?" monitoring for people who ship fast.
What makes it different:
🤖 Vibe Install — instead of filling out forms, you grab a vibepulse-install.md and hand it to Cursor / Claude Code / Codex. Your AI agent wires up the heartbeat in your repo (env var, no hardcoded URLs). This is the part I'm most excited about.
💓 Two ways to watch — we ping your public URLs and support heartbeats (dead-man's-switch) for cron jobs and background workers that have no URL to ping.
🔔 Alerts that reach you — Email, Slack, Discord, Telegram, KakaoTalk.
🟢 Quiet when healthy, impossible to miss when it's not. First alert in under 5 minutes.
It's been a full build-in-public journey (I've written up the messy decisions and the stuff I got wrong and had to redo), and I'd genuinely love your feedback.
👉 What's the scariest "it silently died and I had no idea" moment you've had? And if you try the AI install with your agent, I'd love to hear how it went. 🙏