This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
CronPulser
Hosted cron for HTTP jobs and servers behind a firewall
CronPulser runs your scheduled jobs and records every run. Call any HTTP endpoint on a cron schedule, or run commands on your own Linux and Windows servers through an open-source Runner, with no inbound ports. Get alerts on failures and missed runs.
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.
No comment highlights available yet. Please check back later!
About CronPulser on Product Hunt
“ Hosted cron for HTTP jobs and servers behind a firewall”
CronPulser was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #149 on the daily leaderboard. CronPulser runs your scheduled jobs and records every run. Call any HTTP endpoint on a cron schedule, or run commands on your own Linux and Windows servers through an open-source Runner, with no inbound ports. Get alerts on failures and missed runs.
CronPulser was featured in Open Source (69.1k followers) and Developer Tools (523.3k followers) on Product Hunt. Together, these topics include over 113.2k products, making this a competitive space to launch in.
Who hunted CronPulser?
CronPulser was hunted by Savas Ozturk. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how CronPulser stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
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.