Two paths through the same incident.
Without the Doppelgänger
- 1
Before the campaign
An agency edits theme files directly on the live server, without consultation and without documentation.
- 2
Weeks later
A theme update overwrites these changes. The landing page is broken, and nobody knows why.
With the Doppelgänger
- 1
Next morning
The nightly file comparison shows every deviation from the version-controlled state.
- 2
After that
The change is either adopted properly or rolled back, and the dossier shows when it came in.
An update alone is not enough: for almost half of all WordPress vulnerabilities there is no patch yet when they are published. That is why nightly monitoring is part of it.
What the incident costs.
More case studies
Nobody did it
After a new feature went in, the product search found nothing anymore. Nobody knew who had changed what.
A thousand pages nobody wrote
Google suddenly showed thousands of pages with Japanese ads for the company website.
The test email to every customer
While the new newsletter was being tested, 4,000 real customers received an email saying “Test Test”.
A typical course of events, assembled from real incidents. Figures are example calculations based on the stated assumptions.