# CronPulser

> CronPulser is a centralized scheduling and execution service. It triggers HTTP endpoints first and runs approved private-machine commands through CronPulser Runner, with history and alerts built in.

Build the job; CronPulser handles the schedule. Teams can keep business operations in their applications, trigger them through scheduled HTTP requests, and avoid operating a scheduler in every codebase. When work must remain on a private machine, CronPulser Runner provides centralized Linux and Windows execution. The canonical website is https://cronpulser.com.

## Documentation

- [CronPulser Documentation](https://cronpulser.com/docs/): Index of the API reference, Runner setup, MCP integration, and Agent Skill.
- [CronPulser API](https://cronpulser.com/docs/api/): Authentication, job management, triggering, and execution-log API reference.
- [CronPulser MCP](https://cronpulser.com/docs/mcp/): Connect supported AI agents to CronPulser through scoped OAuth 2.1 access.
- [CronPulser Agent Skill](https://cronpulser.com/docs/agents/): Install the Agent Skill so Claude Code, Codex, Cursor, and other coding agents can help manage jobs, write Linux and Windows Runner scripts, and troubleshoot.
- [Agent Skill source](https://cronpulser.com/skills/cronpulser/SKILL.md): SKILL.md entry point; reference files are listed in https://cronpulser.com/skills/cronpulser/manifest.txt.
- [CronPulser Runner](https://cronpulser.com/remote-job-runner/): Centralize recurring Linux and Windows commands without inbound SSH or open ports.
- [Runner Setup](https://cronpulser.com/docs/runner/): Install a runner on Linux or Windows Server, run a first test job, configure allow-listed scripts, start, stop, restart, and uninstall.
- [Runner source code](https://github.com/cronpulser/cronpulser-runner): The open-source (MIT) Runner agent; releases are built by GitHub Actions with build provenance.

## Product guides

- [CronPulser Guides](https://cronpulser.com/guides/): Practical guides for reliable HTTP scheduling and private-machine command execution.
- [HTTP Cron Job Scheduler](https://cronpulser.com/http-cron-job-scheduler/): Schedule HTTP requests with execution logs, retries, secure headers, and failure alerts.
- [TLS Certificate Monitoring](https://cronpulser.com/tls-certificate-monitoring/): Check a hostname's TLS certificate on any cron schedule, record expiry, issuer, and validity, and alert a chosen number of days before expiry.
- [Windows Job Scheduler for Servers](https://cronpulser.com/guides/windows-job-scheduler/): Schedule PowerShell scripts on Windows Server with central history and alerts, compared honestly with Task Scheduler.
- [How to Monitor Cron Jobs](https://cronpulser.com/guides/how-to-monitor-cron-jobs/): Six failure modes, heartbeat and hosted-scheduling coverage, and validation of business outcomes.
- [Authenticate Incoming CronPulser Requests](https://cronpulser.com/guides/authenticate-cronpulser-requests/): Verify the job-specific X-CronPulser-Secret safely in ASP.NET Core, Express, FastAPI, Go, and Laravel.
- [Schedule API Calls with Cron Safely](https://cronpulser.com/guides/schedule-api-calls-with-cron/): Design authenticated, retry-safe recurring API requests with explicit idempotency, overlap, logging, and alert behavior.
- [Prevent Cron Job Overlap](https://cronpulser.com/guides/prevent-cron-job-overlap/): Stop concurrent Linux cron runs with flock and make skipped work visible in CronPulser Runner.
- [Run Cron Jobs in Order](https://cronpulser.com/guides/run-cron-jobs-in-order/): Sequence dependent commands in one Bash wrapper, preserve failures, and monitor the result.
- [Retry a Failed Cron Run](https://cronpulser.com/guides/retry-a-failed-cron-run/): Decide when to retry, handle uncertain outcomes and duplicate writes, and understand bounded HTTP retries.
- [Verify a Cron Job Did the Work](https://cronpulser.com/guides/verify-a-cron-job-did-the-work/): Validate completed work explicitly, because exit code 0 alone cannot prove the outcome.

## Blog and examples

- [CronPulser vs Cronitor](https://cronpulser.com/blog/cronpulser-vs-cronitor/): Hosted scheduling versus existing-job instrumentation, pricing examples, and operational tradeoffs.
- [CronPulser vs Healthchecks.io](https://cronpulser.com/blog/cronpulser-vs-healthchecks/): Hosted dispatch versus heartbeat reporting, free plans, and retention models.
- [CronPulser vs Runhooks](https://cronpulser.com/blog/cronpulser-vs-runhooks/): Pricing by jobs versus by runs, local commands, MCP, CLI, and where Runhooks is the better pick.
- [CronPulser Blog](https://cronpulser.com/blog/): Real-world HTTP, Linux Runner, Windows Runner, and execution-log examples.
- [ASP.NET Core Contract Expiration](https://cronpulser.com/blog/expire-contracts-aspnet-core/): Keep contract transition logic in ASP.NET Core while CronPulser schedules a protected, idempotent endpoint.
- [HTTP API Sync Example](https://cronpulser.com/blog/http-api-sync-execution-logs/): Design a traceable, authenticated, idempotent recurring API request.
- [Linux Backup Example](https://cronpulser.com/blog/linux-backup-cron-runner/): Run an allow-listed backup wrapper and interpret its output safely.
- [Windows PowerShell Example](https://cronpulser.com/blog/windows-powershell-cron-runner/): Schedule a non-interactive service report through Windows Runner.
- [Windows SQL Server Backup](https://cronpulser.com/blog/windows-sql-server-backup-runner/): Create and verify a timestamped SQL Server backup on protected UNC storage.

## Product and policies

- [CronPulser](https://cronpulser.com/): Product overview and features.
- [CronPulser Pricing](https://cronpulser.com/pricing/): Free, Pro, and Scale plans, annual prices, log retention, and API/MCP availability.
- [Privacy Policy](https://cronpulser.com/privacy/): How CronPulser handles personal data.
- [Terms of Service](https://cronpulser.com/terms/): Terms governing use of CronPulser.

## Additional discovery

- [Sitemap](https://cronpulser.com/sitemap.xml): Canonical list of public pages.