Watch · monitoring — one year, paid once
It writes to you the day something has changed
An analysis is only valid for the day it was run. Watch turns it into a continuous state, and it monitors two things at once: what changes ON YOUR SIDE — the first executable file that changes without explanation — and what changes ON THE VENDORS' SIDE, whose fingerprints and published vulnerabilities change even when your site itself hasn't moved. The rest of the time, it stays silent.
per site per year · Watch + Restore at €199 · one-time payment, no auto-renewal
An analysis is valid for the day it was performed
That is the honest limit of any diagnosis, and we write it on every one of our documents. Watch is the answer: the attestation is anchored to the inventory's fingerprint — a single root computed from all your files. The first executable file that changes breaks it. Mechanically, without anything having to be recognized.
So this is not an annual badge you display and hope for the best. It is a continuous state, one that disproves itself on its own.
The inventory fingerprint is identical. You receive nothing — and that's the intended behaviour, not an oversight.
Your site's fingerprint no longer matches the one on record. We know something has changed; we don't keep what it would take to say what — that's a deliberate choice, and a full analysis will tell you. We never say "infected": a legitimate deployment produces exactly the same signal.
Reported at every pass, never silently swallowed. A monitoring tool that stays quiet because it couldn't look is worse than no monitoring at all.
- 02 Augustnothing to report
- 03 Augustnothing to report
- 04 August3 executable files appearedyou'll be notified
- 05 Augustsite injoignableyou'll be notified
- 06 Augustnothing to report
Quiet days produce no messages. A tool that writes every day ends up in a folder no one opens.
Its only reference is what the publishers release
Your site's attestation is anchored to a single root, computed from the fingerprint of all your files. One executable file changes, and that root changes all the way up.
This is what makes Watch indifferent to novelty: it does not try to identify what has appeared, it observes that the attested state is no longer yesterday's. No signature database can be missing from it, since it uses none.
It stays silent when all is well
A monitoring tool that sends a daily message saying everything is fine ends up in a folder no one opens. The day it has something to say, it is already invisible.
Watch only writes on change. That is also what makes it workable across an entire portfolio: an agency managing sixty sites receives one message when one site moves, not sixty messages a day.
One year, paid once — and the year ends on its own
The watch works every day, but it is not sold by recurring debit: you pay for one year, once. At the end, it stops on its own and notifies you — resuming it is a new purchase, never a tacit renewal. Selling "lifetime" monitoring that would have to stop one day would be a promise we could not keep; selling one year, we know we can keep.
The price is the same whether you have an incident or not — and over a year, it amounts to less than one day of a closed shop.
Monitor, or monitor and repair
The second includes the first. That is the only thing to grasp here: a merchant who only wants to KNOW does not need the repair, and should not be pushed toward it.
Watch
« Has anything changed? »
99 €
one year — one-time payment, no auto-renewal
- Your site's attestation is anchored to a single root: the first file that changes breaks it
- Every core file checked against its publisher's official fingerprint, continuously
- Vulnerabilities published since, matched against YOUR installed versions
- No alerts when all is well — a tool that speaks every day ends up in the "read" folder
Watch + Restore
includes the previous one« And brings it back into compliance all by itself. »
199 €
one year — one-time payment, no auto-renewal
- Everything included in Watch
- Diverging core files are restored automatically
- Proven or rolled back, with a revert if the site stops responding
- Whatever ALREADY diverged when you signed up is named, never rewritten: we only restore what we have seen change
- The shift from "I'm warning you" to "it's fixed"
One year, paid once. Nothing renews: at the end of the year, monitoring stops on its own and notifies you — resuming it is a new purchase, never a charge to your card.
It knows how long that file has been there
Every file version seen on your site is dated from its first appearance. When a file called into question arrived SINCE our last pass, it says so and steps up a level: this is not an old state discovered late, it is something that has just happened.
And when our registry is too young to decide, it stays silent. A fingerprint seen on its very first day tells us nothing: we could not distinguish "it appeared that day" from "it existed before we looked."
It restores what changed under its watch
At your first comparison against the publishers, some files may already diverge. We name them for you, and we do not touch them: we have never seen your site in a known state, and "restoring" a state we never observed could mean overwriting a fix you had applied by hand.
From that point on, everything that changes is restored. But a site already altered when it arrives calls for a full analysis — and it is that analysis, not the watch, that produces the signed finding a host requires to restore a suspended site.
You can still ask us to restore them, once, after reading the list. We do not offer this at sign-up: on that day, neither you nor we yet know which files are involved. And this permission is never left standing — otherwise it would erase every night the fix you have just reapplied.
It compares fingerprints, and it keeps a record
Watch sends back neither the contents of your files, nor your customer data, nor your orders. It does keep a record, though, and it is better said in full: your site’s address, your contact, the address of the agent installed, your site’s root, the reference fingerprint, the list of paths and fingerprints of your executable files, the destinations your page actually contacted, the date each unexplained file first appeared, and the chained log of its passes. Without the paths and the fingerprints, it would know that a byte had moved without being able to tell you which one, or since when: that record is what makes it possible to name the file, date its arrival, and recognise the same bytes on another of your sites.
And when Watch stops — at the end of the year, or earlier if you ask — the record is deleted: there is nothing left to retrieve from us.
A site cleaned today is a site to watch tomorrow
Cleanup rarely holds on its own: the door someone came in through is often still open.