EU-hosted uptime and cron monitoring

Find out fast when a website, API, or scheduled job stops working. Checks run as often as every minute and are confirmed from several EU regions before anyone is alerted.

Built for teams whose compliance review asks where monitoring data goes.

Free plan · no credit card required.

Getting started

Two minutes to your first alert

Paste a URL to watch an endpoint, or curl a ping URL at the end of a scheduled job. No agent to install, no config file to learn.

Paste a URL

https://api.example.com/health

Checked as often as every minute, from EU regions.

Add one line to your job

curl https://watchcat.io/p/cron/YOUR_TOKEN

Miss a ping and WatchCat opens an incident.

Websites and APIs

HTTP checks with expected status codes, body assertions, SSL expiry and multi-region confirmation before anyone gets an alert.

status codes body contains SSL expiry multi-region

Cron and background jobs

Heartbeat monitoring for scheduled work. Catch the runs that never started, ran long, or exited non-zero.

/start /end /fail exit codes

Incidents and alerts

A confirmed failure opens an incident with a timeline. Every alert delivery is recorded, so you can see which alert went where and when — not just that something fired.

confirmation period recovery alerts incident timeline delivery log
EU data path

Core monitoring stays in Europe. Exceptions are explicit.

WatchCat is built for teams that need a clear data path, not vague residency promises. Core checks and incident data run on EU-hosted infrastructure; external providers enter the flow only when you configure them.

Core data path

Checks, incidents, logs, and status history are processed on EU-hosted infrastructure operated by WatchCat.

Where data leaves

Slack, Discord, Telegram, Google Chat, custom webhooks, and Stripe only enter the flow when you configure an integration or use billing.

Paper trail

Security measures, subprocessors, and a DPA are published, so your compliance review has documents to work from.

Monitor detail

Every check, with the reason it failed

Response times, status codes, and the rule that tripped — not a guess from the HTTP code alone.

WatchCat monitor detail Uptime monitoring
Incidents

Know what broke, when, and for how long

Every outage becomes a structured incident with a timeline, alert delivery details, and recovery time.

WatchCat incidents overview How detection works
Integrations

Alerts where your team already works

Slack, Discord, Telegram, Google Chat, webhooks, or plain email — with delivery tracked per alert.

WatchCat integrations Alerts & integrations
Status pages

Tell customers before they ask

Publish a live status page that reflects the real state of your services, and post updates as you work the incident.

WatchCat status page See WatchCat's live status
Automation

Manage monitors from your code — or your AI agent

WatchCat ships an MCP server and a REST API. Define monitors as part of your deploy pipeline, or connect an assistant to triage incidents and post status updates.

MCP server REST API scoped keys
Automation & API
terminal
# Connect an AI assistant over MCP
$ claude mcp add --transport http watchcat \
https://watchcat.io/mcp \
--header "Authorization: Bearer wc_…"
# …or create a monitor from your pipeline
$ curl -X POST https://watchcat.io/api/v1/service_monitors \
-H "Authorization: Bearer wc_…" \
-d '{"url":"https://example.com"}'
Pricing

Simple, predictable pricing

No per-seat surprises. Pay for what you monitor, not how many people are on your team.

Start free No credit card required.
Free €0 /mo Always free Pro €19 /mo excl. VAT Team €49 /mo excl. VAT
Monitors 5 50 200
Check frequency 3 min 1 min 1 min
Data retention 7 days 90 days 365 days
Status pages 1 3 10
Audit log 90 days 365 days
Support Email Email
FAQ

Frequently asked questions

The things teams ask before they move monitoring to WatchCat.

Where exactly is my data hosted?

Uptime checks run from these European datacenters, and monitoring data is stored on EU-hosted infrastructure:

  • Austria flag Austria
  • Finland flag Finland
  • Germany flag Germany

Checking from Europe gives realistic latency for European users and keeps data residency aligned with EU expectations. Additional regions may be added in the future.

Core monitoring data stays in the EU: WatchCat does not route monitoring traffic through US servers. There are two exceptions: payment processing is handled by Stripe (billing data only, not your monitoring data), and if you enable alert integrations — Slack, Discord, Telegram, Google Chat, or custom webhooks — those alerts route through the destination you choose, subject to that provider's own infrastructure.

Do you offer a Data Processing Agreement (DPA)?

Yes. Once you sign up, you can generate and sign a compliant DPA directly from your dashboard for your records.

What happens if WatchCat goes down?

WatchCat's infrastructure is monitored independently from customer checks, so an internal incident raises internal alerts and gets a post-incident review like any other outage. You can see the current and historical state yourself on WatchCat's public status page.

How fast are alerts sent?

Alerts are typically delivered within seconds after a failure is confirmed.

Checks run continuously, and notifications are dispatched immediately once a monitor transitions into a failing state (after any configured confirmation or grace period). In practice, this means:

  • detection → confirmation → notification happens very fast
  • no artificial delays or batching

Actual delivery time also depends on the notification channel itself (email provider, Slack, webhook receiver, etc.), but WatchCat does not intentionally slow alerts down

Can I migrate from UptimeRobot or Better Stack?

Yes. While there is no one-click importer yet, migrating is straightforward.

Most users recreate their monitors manually in a few minutes, especially for HTTP checks and cron jobs. The concepts are familiar, and WatchCat avoids unnecessary complexity during setup.

For larger setups, you can script the move with our REST API, or let an AI agent recreate your monitors through the MCP server.

Do you support on-call schedules or escalations?

Not yet.

WatchCat currently focuses on fast detection and reliable delivery. On-call schedules and escalation policies are not currently supported.

What payment methods do you accept?

Payments are handled securely via Stripe.

This means you can pay using:

  • major credit and debit cards
  • international payments without friction

Invoices, receipts, and subscription management are all handled through the Stripe billing portal, accessible directly from your account.

Why is WatchCat billed monthly only?

Monitoring is built on trust. Monthly billing keeps WatchCat simple, transparent, and easy to cancel — you stay because it works for you, not because you prepaid a year in advance.

No lock-in, no forgotten renewals.

Still unsure? [email protected]