Hi Product Hunt! I'm Savas, and I built CronPulser.

I run several small products on my own servers, and kept getting surprised by cron jobs that had quietly stopped, especially database backups on Windows Server, where Task Scheduler fails without telling anyone.

CronPulser owns the schedule and starts the work, so you don't need a server just to keep cron alive:

- HTTP jobs: any method, headers and payload, a cron expression with a timezone. Every run is recorded with status, duration and, if you want, the response body.

- Runner: a small open-source Go agent (MIT) for Linux and Windows Server 2019-2025, for work that can't be an HTTP call, like database backups on a private box. It connects outbound over 443, so there's no inbound port or SSH, and it only runs commands you list in its local config file.

- Alerts on failed runs, slow runs, unexpected output, and schedules that stop running at all.

- An MCP server, so AI agents like Claude can list, create, pause and trigger jobs.

Honest limits: there's no heartbeat/ping-in endpoint, so it doesn't watch cron jobs you run elsewhere, and 4xx responses are never retried.

The free plan has 5 active jobs, no credit card. Paid plans are $9 and $29 a month, priced by active jobs, not runs.

I'd love to hear what you would need before trusting a hosted scheduler with production jobs.