The person who built PingArk is the same one who answers when you write in.

Twenty years of shipping led to one small, sharp tool

I started building websites when the job meant hand-writing everything and hoping it held. Over the years I moved through Joomla and WordPress, then into Laravel and Next.js, and I have built and looked after more sites and applications than I can easily count. Different clients, different stacks, one constant: almost all of them leaned on jobs that run on a schedule. Backups. Imports. Invoices. The nightly email that has to go out.

And scheduled jobs share a quiet, nasty habit. When they work, you forget they exist. When they stop, they usually stop silently. No error on a page, no phone call, nothing. You find out days later, from a customer asking where their report went, or worse, from a backup that was never there when you finally needed it.

I have been on the wrong side of that silence more than once. PingArk is my answer to it. A job pings a URL when it runs; if the ping does not arrive on time, you hear about it in seconds, not days. It is deliberately small and sharp, because the whole point is that it works every single time without you thinking about it.

If you run anything on a schedule, you already know the feeling I am describing. That is exactly who I built this for.