EU hosting · GDPR
EU-hosted cron job monitoring & scheduling
Most cron monitoring services run on US infrastructure. If your company is European, that means transfer impact assessments, DPA back-and-forth, and a vendor review that takes longer than the integration. SteadyCron runs on Hetzner servers in Germany, under a German entity — monitoring and execution, GDPR-clean by default.
Data residency you can put in a vendor review
Jobs run and logs live on Hetzner servers in Germany. When your DPO asks where the data goes, the answer is one line: it stays in the EU.
Self-serve DPA — no sales call
The GDPR Art. 28 Data Processing Agreement is part of our standard terms and applies from signup. Procurement gets a link, not a negotiation.
A sub-processor list that fits on one screen
No sprawling US cloud dependency chain. The complete list — with roles and locations — is public on our Trust page and stays short by design.
German legal entity, EU jurisdiction
SteadyCron is operated from Germany under German and EU law. No Schrems II transfer analysis needed for the core service.
How the usual options compare
All of these are good tools. But if EU data residency is a requirement rather than a preference, the hosting column decides for you.
| Service | Hosting | DPA | Runs your jobs |
|---|---|---|---|
| SteadyCron | Germany (Hetzner) | Self-serve, included | Yes |
| Healthchecks.io (managed) | US | Self-host for full control | No |
| Cronitor | US | On request | Limited |
| Dead Man's Snitch | US | — | No |
Hosting and DPA details for other services as published at the time of writing — verify against their current documentation. Detailed feature comparisons: vs Healthchecks.io · vs Cronitor · vs Dead Man's Snitch
What "GDPR-native" means here
GDPR compliance for a monitoring vendor isn't a badge — it's a set of concrete questions your DPO will ask. Here are the answers, up front:
- Where does personal data live? On Hetzner servers in Germany. Execution logs, ping payloads, and account data stay in the EU.
- Under which legal basis do we process it? Art. 6(1)(b) — performance of contract. Analytics are cookieless (Cloudflare Web Analytics).
- Is there an Art. 28 DPA? Yes, self-serve, incorporated into the Terms — read it on the Trust page.
- Who are the sub-processors? A short public list, EU-focused, on the same page.
- What about international transfers? Core service: none. Edge cases (e.g. email delivery) are documented with safeguards on the Trust page.
If your procurement process needs more, the Trust & DPA page is the complete pack: DPA text, sub-processor table, transfer safeguards, and the Team-plan SLA — all readable without a sales call.
Frequently asked questions
Is SteadyCron GDPR compliant?
Yes. SteadyCron is operated by a German business under German and EU law. A GDPR Art. 28 Data Processing Agreement is part of our standard terms — no negotiation or sales call needed — and the full sub-processor list is public on our Trust page.
Where is my data stored?
Your account data, job configurations, execution logs, and the job execution itself run on Hetzner servers in Germany. Core data does not leave the EU.
Is SteadyCron an EU alternative to Healthchecks.io or Cronitor?
Yes. Healthchecks.io (managed) and Cronitor are US-hosted. SteadyCron offers heartbeat monitoring like both, plus scheduled HTTP job execution — hosted in Germany with a self-serve DPA, which simplifies GDPR vendor reviews for EU companies.
Do you offer a signed Data Processing Agreement (DPA)?
Yes, self-serve. The DPA is incorporated into our Terms of Service and applies to every customer from signup. You can reference it directly in your records of processing activities (Art. 30 GDPR).
Which sub-processors does SteadyCron use?
A short, public list — Hetzner (Germany) for infrastructure and a small number of EU-focused services for email and payments. The complete, current list with roles and locations is on the Trust page.