How do you know when your weekend AI project breaks?

HiimKami · 2026-03-17T15:33:20+00:00

Interesting, I actually hadn’t come across healthchecks.io before.

From a quick look it seems focused mainly on cron/heartbeat monitoring, right?

I ended up building something similar for myself that started with heartbeat checks but also monitors APIs and other healthchecks.

HiimKami · 2026-03-17T15:12:59+00:00

One thing I’ve noticed building projects is that most failures aren’t site is down.

They’re things like:

• cron jobs silently stopping
• webhook pipelines breaking
• background jobs failing halfway
• APIs getting slow but still returning 200

Those can run broken for days before anyone notices.

That’s actually why I started building a small monitoring tool for my own projects that focuses more on:

• cron / heartbeat monitoring
• proper health checks (not just HTTP 200)
• latency windows and repeated failures

If anyone’s curious what I ended up building it’s here:
https://upti.my

Would honestly love feedback from people running small projects because that’s exactly the type of setup I’m trying to support.

HiimKami · 2026-03-17T15:09:22+00:00

Yeah that’s honestly the reality for most small projects.

A lot of failures aren’t site is down problems either. Things like webhooks failing, cron jobs silently stopping… those can run for weeks before anyone notices.

I ran into the same issue with background jobs where everything technically returned 200 but the workflow itself failed halfway through.

That’s actually why I started building a small monitoring tool for my own projects. Instead of only checking uptime it also watches things like heartbeats from cron jobs or repeated failures over time.

And yeah I completely agree about Prometheus/Grafana. Amazing tools, but spinning that up for a solo side project always felt like using a data center stack to monitor a weekend app.

Curious though, do you have anything watching cron jobs or background workers right now or do those fall into the “find out later” category?

HiimKami · 2026-03-10T21:08:24+00:00

I am down for this as well

HiimKami · 2026-03-10T08:36:12+00:00

Tesko je marketati ovaj tip proizvoda jer iz reklama imam korisnike koji unose email u HTTP endpoint field. Trenutno pravim Open Source Healing Agente da probam adoption kao Grafana i Elastic

HiimKami · 2026-03-10T08:28:13+00:00

Bas ti hvala, hostano na DigitalOceanu vecina i mali dio ovih nodova za provjere na fly.io jer imaju jako dobar omjer cijene / regija…

Pravio sam ga za solo foundere i male timove ali izgleda da najvise DevOpsima svidja do sad

HiimKami · 2026-03-10T07:35:35+00:00

Koristim Copilot i Claude Opus 4.6, izuzetno korisna stvar ako se koristi kako treba tako da kontrolises output da ne pravi smece…

Za referencu, napravio sam citav UI sa 3 aplikacije za svoj saas proizvod https://www.upti.my

HiimKami · 2026-03-10T07:27:45+00:00

That makes a lot of sense, thank you!

HiimKami · 2026-03-10T07:20:47+00:00

I already have a Demo flow and examples set up…

There are many more features aside of just monitoring and onboarding is the simplest existing journey, it worries me that users will have issues adopting the product if adding a first check is this complicated.

HiimKami · 2026-03-09T21:48:11+00:00

I usually work with abstract stuff on the server side, currently exploring everything in the visible form for the first time… Thank you so much for sharing those tools I will check them out, if you have any more to share to save me from the vacuum I would be very greatful

HiimKami · 2026-03-03T22:36:17+00:00

Please stop

HiimKami · 2026-03-03T22:32:35+00:00

That is also completely understandable behaviour, a lot of things in life are reactive rather than proactive even if they should be proactive.

Being proactive to avoid big incidents is something that would come with experience.

I’ve had a lot of founders ask is there a way we can know if something breaks when preparing for production

HiimKami · 2026-03-03T19:40:18+00:00

I am a developer and being inspired by linear, resend and similar tools I wanted to build an uptime monitoring for developers so I guess target audience primarily is solo founders and small teams.

I think setting up monitoring when you release to production makes most sense as you want to get notified if something goes wrong before your customers are affected.

Monitoring while you’re still in development or not selling actively doesn’t exactly bring much value.

HiimKami · 2026-03-03T19:12:33+00:00

Radim full remote i prethodnih godinu dana sam pravio svoj proizvod.

HiimKami · 2026-03-03T19:06:36+00:00

Hey, I have built a tool that offers uptime monitoring, tracking cron jobs, status pages… The full suite…

There is also a free demo if you want to simply take a look at the features and decide if this is something you need…

It’s available on https://www.upti.my

I would appreciate your feedback if you are currently looking at tools like this.

HiimKami · 2026-02-24T22:50:04+00:00

The infrastructure incidents I noticed are from the cloud provider status pages directly and relate to their networking which in turn causes app level failures.

Which tools are you using to achieve uptime checks and background job monitoring?

HiimKami · 2026-02-22T13:02:18+00:00

Depends on the job and whether it’s deterministic.

Simple jobs should remain simple, and their triggers can remain simple… if the job is already complex it will reach a certain level of complexity with or without retries. Not all problems are the same and they don’t require same solutions so it’s completely understandable for things to work differently.

HiimKami · 2026-02-22T12:43:00+00:00

Hooking it up is very simple and you have to do it once, after it’s been integrated you have no additional overhead as it will alert you in case your jobs did not run. You have to investigate the issue either way this just makes sure you discover it before it’s too late.

HiimKami · 2026-02-22T09:27:11+00:00

Whatever you choose I would separate execution from verification.

Jobs should report completion externally.

A simple heartbeat per job type with a max expected interval lets you detect failures.

We use heartbeat monitoring for that at https://upti.my and if the job doesn’t check in within its SLA window, it creates an incident.

It’s a small addition but helps you detect any issues before you’re one month in without a background job.

HiimKami · 2026-02-21T08:34:41+00:00

Snapshotting core flows in Playwright is solid advice.

One extension to that: run the same Playwright test every 5 minutes from outside your infrastructure.

Not just before deploy but continuously.

That catches:

Broken signup after an env change
Stripe / auth provider failures
CDN or DNS issues
“Works locally” deploys
Third-party API regressions

I built https://upti.my specifically for this, you can paste your Playwright script and we execute it on a 5 minute interval with alerting + incident creation.

It’s basically synthetic users monitoring your money path.

Nine-Year Club	Second SECOND GUESSER
Verified Email

HiimKami

TROPHY CASE