Last year I broke our Facebook pixel during a vibe coding session. No alert, nothing in the logs. We found out when our media buyer asked why ad conversions dropped. Just wasted spend for a week.
That wasn't the first time. A typo once cost me $30K because I only caught it when revenue was down.
So I built Upflag. Uptime monitoring, client-side JS error tracking, and status pages. Errors get translated into plain English ("Your checkout page can't load the payment form") instead of showing a stack trace. Setup is npx upflag init, it detects your framework and drops in the tracking snippet.
I built it for people who ship without a DevOps team. Most of the people I talk to are building with Cursor, Claude Code, Lovable, that kind of thing. (Upflag itself was built with Claude Code.)
Free: 3 monitors, 1 status page, 100 errors/day. Paid is $15/mo. No credit card.
Curious what HN thinks of the plain-English error summaries. Is translating stack traces actually useful, or would you rather just see the raw trace?
Last year I broke our Facebook pixel during a vibe coding session. No alert, nothing in the logs. We found out when our media buyer asked why ad conversions dropped. Just wasted spend for a week.
That wasn't the first time. A typo once cost me $30K because I only caught it when revenue was down.
So I built Upflag. Uptime monitoring, client-side JS error tracking, and status pages. Errors get translated into plain English ("Your checkout page can't load the payment form") instead of showing a stack trace. Setup is npx upflag init, it detects your framework and drops in the tracking snippet.
I built it for people who ship without a DevOps team. Most of the people I talk to are building with Cursor, Claude Code, Lovable, that kind of thing. (Upflag itself was built with Claude Code.)
Free: 3 monitors, 1 status page, 100 errors/day. Paid is $15/mo. No credit card.
Curious what HN thinks of the plain-English error summaries. Is translating stack traces actually useful, or would you rather just see the raw trace?