A monitoring platform that keeps European data in Europe
Six monitoring tools most teams buy separately — uptime, API checks, recorded browser flows, visual regression, sitemap scanning and heartbeats — behind one dashboard, one alert engine and one on-call chain. Built and operated by us, hosted entirely in the EU.
- Tools in one suite
- Six
- Pages per full-site scan
- 500
- Fastest check interval
- 60s
- Data residency
- EU only
The situation
Small teams running real revenue online are told to assemble their monitoring from four or five subscriptions that do not talk to each other: one for uptime, another for browser tests, another for visual diffs, another for cron heartbeats. Each has its own alert rules, so an incident arrives as four unrelated notifications and nobody knows which one matters. And nearly all of them ship the data to a US cloud, which is an awkward conversation for a European company with a GDPR posture to defend.
What we did
One suite, one alert engine, one on-call chain. Checks run from every minute to every hour and assert on more than a status code: response-time budgets, deep JSON assertions with dot-notation paths, and required or forbidden text on the page — because "200 OK" and "working" are not the same thing. Browser flows are recorded by pointing and clicking at a live screenshot of your own site rather than written in Selenium, and a real Chromium walks the checkout every few minutes, keeping a screenshot of every step. Visual regression compares each run against an approved baseline, because a deploy that silently hides the buy button never fails a status check. Alerts escalate on their own: a warning on first failure, a critical incident when it persists, then up the on-call tiers if nobody reacts. All of it runs on Hetzner in Germany — an architectural decision taken up front, not a compliance addendum bolted on later.
Where it landed
Detectly is live and selling, from €49 a month for a single site to unlimited monitors on the top plan. A new workspace is watching its first page within a minute of signing up, full-site scans cover up to 500 pages, and monitors appear and retire automatically as the customer's sitemap changes. Monitoring data, screenshots and incident history never leave the EU.
The product, doing its job.
Not a screenshot — this is the interface rendered in the page, which is also why it is still accurate.
- Homepage GET / · text contains "Add to cart" 182ms
- Checkout flow Recorded browser flow · 4 steps 8.4s
- Orders API POST /v1/orders · JSON assert 96ms
- Nightly export Heartbeat · expected 02:00 late
-
14:02 Warning
Checkout flow over its response-time budget on one run.
-
14:04 Incident opened
Third consecutive failure. "Add to cart" no longer on the page.
-
14:09 Escalated
Nobody acknowledged, so the alert climbed to the second on-call tier.
-
14:11 Recovered
Deploy rolled back. Incident closed automatically, with the timeline kept.
More work.
A checkout that stopped falling over on campaign days
Peak traffic took checkout down three times in one quarter. We measured where it actually bent, fixed four things, and left the load model behind.
- Checkout p95, before
- 4.2s
- Checkout p95, after
- 780ms
- Peak orders held
- 2x
Eleven years of grant software, made changeable again
A working system nobody dared touch. We moved it seam by seam, in production the whole time, with no cutover weekend.
- Change lead time, before
- 6 weeks
- Change lead time, after
- 4 days
- Cutover weekends
- None
Tell us what is not working.
An hour on a call, no charge and no deck. We will tell you honestly whether this is work we are good at — and if it is not, who to talk to instead.
- Reply within
- One working day
- First call
- One hour, free
- Notice period
- One month, either way
- Based in
- Odense & Copenhagen