Skip to content
Codense
Live · Codense product

Six monitoring tools in one, hosted entirely in the EU.

Uptime, API checks, recorded browser flows, visual regression, sitemap scanning and cron heartbeats — behind one dashboard, one alert engine and one on-call chain, instead of four subscriptions that do not talk to each other.

Product

Detectly

Built for

Teams running real revenue online who do not have an SRE.

Pricing

From €49 / month

Visit detectly.codense.dk
detectly.codense.dk
Tools in one suite
Six
Pages per full-site scan
500
Fastest check interval
60s
Data residency
EU only
Why it exists

The problem we got tired of

We kept watching small teams assemble monitoring from four or five tools, each with its own alert rules, so an incident arrived as four unrelated notifications and nobody knew which one mattered. And nearly all of those tools ship the data to a US cloud, which is an awkward conversation for a European company with a GDPR posture to defend. Building it ourselves meant we could make EU residency an architectural decision up front rather than a compliance addendum bolted on later.

What it replaces

6 subscriptions, or one.

Each of these is a tool teams buy separately, with its own alert rules and its own bill. That is the problem, not the feature list.

  • Uptime monitoring
  • API checks
  • Browser testing
  • Visual regression
  • Sitemap scanning
  • Cron heartbeats

Detectly

Monitoring

One dashboard, one alert engine, one bill. 6 subscriptions become one, and the alerts finally agree with each other.

Was
6
Now
1
What it does

The parts that matter

Not a feature list. The handful of decisions that make it different from assembling the same capability out of four subscriptions.

01

Checks that assert more than "200 OK"

Response-time budgets, deep JSON assertions with dot-notation paths, and required or forbidden text on the page. A server can answer perfectly and still be broken.

02

Browser flows recorded by pointing, not scripting

You click through your own checkout on a live screenshot of it. A real Chromium then walks that path every few minutes and keeps an image of every step.

03

Visual regression against an approved baseline

A deploy that silently hides the buy button never fails a status check. Comparing renders is the only way to catch it.

04

Alerts that escalate on their own

A warning on first failure, a critical incident when it persists, then up the on-call tiers if nobody reacts.

Under it

What it runs on

Laravel PHP 8.4 PostgreSQL Redis Chromium Hetzner (DE)
Inside it

One alert, climbing on its own.

Nobody watched this happen. The warning became an incident, the incident found the second tier, and the recovery closed itself — with the timeline kept for the post-mortem.

incident #4192 resolved
  1. 14:02 Warning

    Checkout flow over its response-time budget on one run.

  2. 14:04 Incident opened

    Third consecutive failure. "Add to cart" no longer on the page.

  3. 14:09 Escalated

    Nobody acknowledged, so the alert climbed to the second on-call tier.

  4. 14:11 Recovered

    Deploy rolled back. Incident closed automatically, with the timeline kept.

Next up

What comes after this

In the order we expect to ship it. Say if you need one sooner.

  1. 01 Public status pages for your customers Planned
  2. 02 Alert routing to Slack and Teams Planned
  3. 03 Checks from a second EU region Planned
Next step

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