Guli Isichei
Network editorGuli spent a decade designing campus and data-centre networks. He tests vendor claims against packet captures and outage reports.
About Murray Updates
Clear thinking for the systems that keep work moving.
Murray Updates gives infrastructure professionals useful reporting, careful software updates, and practical context for decisions made under pressure.
The people behind the pages
Meet the team
Our contributors have spent years inside live networks, security reviews, cloud migrations, and hardware rooms.
Zeenat Soutter
Security editorZeenat has led incident response and identity reviews for regulated organisations. Her writing focuses on controls that teams can check in practice.
Jassika Chijuka
Cloud contributorJassika has moved production services between public cloud platforms and private clusters. She writes about cost, resilience, and the work between the diagrams.
Dobromir Tevlin
Hardware contributorDobromir has maintained server fleets through refresh cycles and difficult procurement windows. He looks closely at thermals, firmware, and serviceability.
Why we publish
Useful answers beat loud opinions.
Murray Updates began with a small group of system administrators and technology journalists who saw too much enterprise coverage written around vendor talking points. We report what changes in the rack, the console, and the incident room. Every article is produced in-house, checked against primary sources, and reviewed by practising engineers before publication. Our base is in Waltham Forest, London; our contributors work across the globe. Stay close to the evidence.
In-houseReporting and editing
GlobalContributor network
LondonHeadquartered in E18
Editorial standards
How we work
Trust is built in the small details. Here is what readers can expect before an article reaches the page.
Sources are visible
We cite original vendor documentation, peer-reviewed research, and the lab notes behind our own tests. Readers should be able to follow the trail.
Independence comes first
We do not publish sponsored content or paid reviews. Commercial relationships cannot decide which products receive attention or how they are assessed.
Corrections are clear
When an article contains an error, we note the correction at the top of the article and explain what changed. Quiet edits are not our policy.
Accessibility is part of the job
We work towards WCAG 2.1 AA guidance across structure, contrast, keyboard access, and readable language. Good information should be usable by more people.
Keep informed
Bring better context to your next infrastructure decision.
Receive a focused note when we publish substantial reporting on systems, security, hardware, or software changes.