Answers, before you have to ask.

Yes. Cronitorex monitors production cron jobs, HTTP endpoints and SSL certificates every day. Production traffic welcome on every plan, including Free.

Cronitorex exposes a standard HTTP API with run/complete/fail pattern. If your current tool uses a similar ping model, migration is just changing URL and API key in existing scripts. Full API reference at docs.cronitorex.com, and a step-by-step migration guide covers switching from Cronitor, PostPing, and other tools.

Hosted on our own infrastructure in the EU, GDPR-compliant. All traffic over HTTPS (TLS 1.3) - no ping ever travels in plaintext. The database sits on a private network, accessible only from our application services. User passwords stored as cryptographic hashes. You can rotate your API key at any time from the profile page - the old one stops working immediately. Daily database backups, encrypted, 30-day retention. Full data export and account deletion from the dashboard. We do not sell or share data with third parties. Need an audit report or on-prem deployment? Email hello@cronitorex.com.

On our own infrastructure in the European Union, in line with GDPR. All traffic uses HTTPS, and daily encrypted backups are kept for 30 days.

Yes, at any time from your profile page. The old key stops working immediately, so update your scripts right after rotating.

Yes. Pick which monitors to publish and Cronitorex generates a public status page with live status, uptime percentages and incident history - available on every plan, including Free.

Extra time after the expected start of a run before Cronitorex raises a missed alert. It absorbs normal jitter, like a job starting a minute late.

Yes. Export and import monitors as JSON or YAML, or manage them through the REST API. The full reference lives at docs.cronitorex.com.

Send a host field with each ping. Events keep their origin, so one monitor can cover a job that runs on many machines.

Email, Telegram, Discord and webhook notifications are available on all plans. Slack is included from the Pro plan. Webhooks let you connect any HTTP endpoint, enabling integration with any external service yourself.

Connect the channel in your notification settings and choose which monitors use it. Step-by-step instructions are in the documentation.

One event = one ping (run/complete/fail/skip) from your script, one HTTP check, or one SSL evaluation. A typical cron with 3 pings per run, running every minute = ~130k events/mo. Cron every 5 min = ~26k. You'll easily fit dozens of monitors in 50k.

The API returns HTTP 402 (Quota Exceeded). Your pings stop being accepted until end of month. Nothing disappears - dashboard still shows history. Normal mode resumes on month reset or plan upgrade.

30-day money back on all new subscriptions, no questions asked.

Paid plans are sold through Paddle.com, our merchant of record. Paddle handles the checkout (card, PayPal), charges the correct VAT or sales tax for your country and emails you a proper invoice after every payment. The charge appears on your statement as PADDLE.NET*.