You built something. You shipped it. Someone on Twitter said they use it every day. That's the dream, right? But now there's this low-grade anxiety: what if it breaks while you're offline?

The Guilt of Going AFK

When you have real users—even just 50 of them—you start feeling responsible. Taking a weekend off feels risky. Going on vacation feels irresponsible. This isn't sustainable.

But here's the thing: you're not running a bank. Your side project doesn't need five nines of uptime. It needs to not be silently broken.

Good Enough Monitoring

You don't need a fancy observability stack. You need:

  • To know if your main endpoints are returning valid data (not just 200 OK)
  • To get notified somewhere you'll actually see it
  • To spend less than 5 minutes setting this up

My "Set and Forget" Setup

For every side project, I set up three things:

  1. Health check on the homepage: Makes sure the app loads and returns real HTML
  2. Check on the main API: Validates the JSON structure, not just the status code
  3. One check on a third-party integration: Stripe, auth provider, whatever. These break more often than your code.

Takes 10 minutes. Runs automatically. I get a Discord message if anything's weird. That's it.

Permission to Relax

The point of building side projects is joy. Shipping things. Seeing people use them. The anxiety of "what if it's broken" shouldn't be part of the package.

Set up basic monitoring. Give yourself permission to close your laptop. Your project will be fine—and if it's not, you'll know immediately.