ENFR — Passer en français
IT emergencyLet’s talk about your project
Operations centre for monitoring, backups and disaster recovery across clients
CASE STUDY / 07ANONYMISED ASSIGNMENT
Operations tooling · cross-client

Monitoring, backups and continuity

Tools born from one assignment then reused elsewhere: detect before the phone rings, verify the backups and prepare a standby switchover without improvisation.

← All case studiesA similar challenge?
DURATION3 years
ROLEDesign and build
SCOPEMulti-client
STATUSIn production
THE CONTEXT WE FOUND

Understand the system
before transforming it.

The founding incident was a monitor frozen for twenty days without a single alert: an unreachable site blocked the cycle, whose lock was only released at the end. Since then, the monitoring tools monitor themselves.

WHAT WAS DONE

From diagnosis.
To production.

The scope describes the decisions and the work actually carried out, without naming the organisation involved.

01

Monitor beyond a simple ping

Availability, certificates, languages, content, fingerprints and browser-rendered pages, with targeted alerts.

02

Bring operations onto one screen

Services, servers, scheduled jobs, errors, SEO, caches, queues, partner feeds and forms, without opening access to production.

03

Centralise the backups

Dumps every 30 minutes through restricted tunnels, named by client and service, plus object storage for media.

04

Prepare a progressive switchover

Traffic, database and scheduled jobs switch separately, on a human decision and after prior checks.

05

Operate without an inbound port

Local dashboard reachable through an outbound tunnel with access control.

MEASURED RESULTS

Facts.
Not a logo.

30 minbetween two backups
Multi-clienta shared operations foundation
DR planprogressive switchover prepared
Self-checkthe monitor monitors itself
TECHNOLOGIES IN PRODUCTION

The foundation actually used.

TypeScriptNode.jsPlaywrightSQLiteExpressDockerCronSSHCloudflare Tunnel

Clients, brands, domains, addresses and identifying details are not published. The figures come from the logs, databases, clusters, repositories and control reports provided for these assignments. Security incidents are described without any reproducible exploitation path.

OTHER CASE STUDIES

Two other systems.
Two other sets of constraints.

Cybersecurity team responding to an attack and hardening servers08
Operational security · cross-client

Hardening and incident response

Several real compromises handled end to end on production servers, then turned into a reusable method.

3 yearsMethod in place
Read the full case study
Digital ecosystem connecting a vehicle catalogue, branches and data flows01
Automotive retail · franchise network

National automotive marketplace

A network of around 90 branches, a marketplace in 7 languages and 14 country versions, and the whole system connecting catalogue, acquisition, CRM, distribution, invoicing and cloud operations.

2 yearsIn production
Read the full case study

A critical system to build or to take over?

Describe the context, the existing systems and the expected result. We will propose the right level of intervention.

Talk to RGAIX