Your clients’ WordPress cron, finally reliable
No more wp-cron waiting for a visit. One organization per client, each sees their own history.
- 10:05:00GET /wp-cron.php200184 ms
- 10:10:00GET /wp-cron.php200201 ms
- 10:15:00GET /wp-cron.php200176 ms
Cronhound fires your HTTP requests at a fixed time, retries on failure and alerts you by e-mail or webhook. One service for all your teams.
Your jobs, your account, your payments and your e-mails stay with European providers.
Signing in with Google is optional: an e-mail address and a password are enough.
European sovereignty
Your jobs, your URLs and your history stay in Europe. No data resale, no advertising, no advertising trackers.
Our servers run in an OVHcloud datacenter in France. Your data does not leave the EU.
Hosting and service data depend on European companies, not on a US jurisdiction.
Only the data the service needs, for a clear purpose, while respecting your rights.
No advertising cookies and no third-party analytics tools. Anonymous audience measurement, without cookies.
URLs, headers and request bodies are encrypted at rest (AES-256-GCM). History is purged automatically.
Why not a crontab?
| Crontab on a server | Cronhound |
|---|---|
| A failure goes unnoticed. The MAILTO e-mail is never read. | You are warnedHistory, HTTP code and alert by e-mail or webhook. |
| One server: if it goes down, nothing runs. | Outside your infrastructureWith automatic retries on failure. |
| You need SSH access to change a single line. | Roles per projectEach member acts on their own jobs, without server access. |
| Nobody knows who changed what, or when. | A chained audit logIt helps you document your controls (ISO 27001, NIS2). |
| Impossible on a serverless platform or a PaaS. | A simple URL is enoughYour code stays where it is. |
Use cases
A URL, a frequency. Cronhound calls it, checks the response and warns you if something goes wrong.
No more wp-cron waiting for a visit. One organization per client, each sees their own history.
Your ERP and your shop show the same figure. No orders on a sold-out item.
The export runs on its own. If your server stumbles, Cronhound retries before anyone notices.
Your integrations stop breaking on a Monday morning because a token expired over the weekend.
Your retention period is respected every week, and every run leaves a trace.
If it stops answering, you know before your customers do.
Features
GET, POST or PUT requests triggered by a cron expression, without writing a worker.
Retry automatically on failure and set a timeout for each request.
Get notified as soon as a job fails, by e-mail or to your own webhook.
Review each execution, its status code, its duration and the response received.
Organize your jobs by environment, project or server with tags.
Create tokens to drive Cronhound from your scripts and your CI.
Pricing
Start with Basic, move to Starter or Pro when your jobs grow.
€0for 3 months
then €1.00 excl. VAT per month, €1.20 incl. VAT
Includes:
€3.49excl. VAT /month
i.e. €4.19 incl. VAT
Everything in Basic, plus:
€9.99excl. VAT /month
i.e. €11.99 incl. VAT
Everything in Starter, plus:
| Feature | Basic | Starter | Pro |
|---|---|---|---|
| Price excl. VAT per month | €1.00 | €3.49 | €9.99 |
| Owned organizations | 1 | 1 | 3 |
| Projects per organization | 1 | 1 | 3 |
| Active jobs per project | 1 | 5 | 20 |
| Minimum interval | 1 hr | 1 min | 15 sec |
| Members per organization | 1 | 3 | 50 |
| History | 7 days | 30 days | 90 days |
| Maximum request timeout | 15 sec | 30 sec | 2 min |
| E-mail alerts | Included | Included | Included |
| Webhook alerts | Not included | Included | Included |