Managed network security and backup for London small businesses. IT consultancy for organisations that want to understand their infrastructure honestly.
James Bacchus founded δivergent Byte Limited on 19 June 2025 — FreeBSD Day. The date was not accidental.
The thirty-second version: he read Physiological Sciences at Lincoln College, Oxford, spent thirty years running production IT for organisations that could not afford for it to fail, and arrived at BSD through the same process he applied to everything else — following the evidence until it stopped.
The longer version is in the essays.
A vendor-side career teaches you what systems can be sold. A client-side career teaches you what systems actually do, what they cost to maintain, what happens when the licensing model changes, and what it feels like at 11pm when something that was supposed to work does not.
The knowledge accumulates differently. It accumulates in specific places, from specific events, and it tends to produce opinions that are harder to shift because they were earned rather than inherited.
The most significant posting was as head of IT at the Ministry of Sound — a 180-staff multisector SME operating a nightclub, record label, brand licensing operation, media company, and venue simultaneously. The data governance complexity of that estate was not simple. The accountability ran directly to CEO and MD. The infrastructure had to work through the 2008 financial crisis and through COVID-19, both of which tested, in different ways, the value of systems you can read when you cannot ring the vendor's support line.
That experience produced the offsite replication architecture now deployed as the Remote Data Vault: the same architectural judgement made with better tools, validated in production at scale before it was offered as a service. It also produced the Schrödinger-Peter Parker Principle, the FD Principle, and a fairly specific view of what managed service agreements should and should not contain.
The move to BSD was not a conversion. It was a conclusion. The same analytical habit that produced the defence of Ballmer's Systems and Management principle produced the recognition that the BSD architecture was correct for the problems δivergent Byte's clients actually have: network boundary security without subscription dependency, backup without cloud relay, offsite replication without US jurisdiction. The tools are different. The method is the same.
The Double Maths piece is the explanation of why the GUI exists and what it costs. The NGFW piece is the documented evidence of that cost in the CVE record. The FD Principle is the governance argument. The Ballmer essay is the honest account of thirty years in a Microsoft estate. The Efficiency Paradox is the structural market argument — why BSD is penalised by the market for being too good at extending hardware life.
The Prisoners' Problem series is something different in kind. It started with two FreeBSD security advisories from early 2026 and a question: are these the same thing? They were. Gustavus Simmons described the class in 1983. The field still does not have a shared operational vocabulary for it. Each instance is treated as a novel finding. The series is an attempt to name the class precisely enough that the defence can be systematic rather than reactive.
The Oxford formation is visible in that, if you are looking for it. The habit of checking whether the phenomenon has been named before. The discomfort with imprecision in a field where imprecision has consequences. The willingness to follow the argument past the comfortable stopping point.
It is not a credential that is led with. It is a formation that shows in the work.
δivergent Byte is based in Islington and serves London small businesses — primarily professional services firms of two to twenty people who have been meaning to sort out the backup situation, or whose IT person told them they need a proper firewall, or who are running a Time Capsule that Apple discontinued and have been putting off the conversation.
The work is also available to organisations that want to think more carefully about their infrastructure before they make a significant decision. The Gatekeepers of POSIX workshop exists for that conversation.
The essays are available to anyone. They are licensed under CC BY 4.0. Attribution matters — it is one of the principles the work is built on.
δivergent Byte is a single-operator consultancy. That means one person who built the products, knows every deployment, and is accountable for all of them. It also means the service is scoped honestly to what one operator can maintain well. The managed service documentation defines the scope. The break-glass credential in the client's deed safe defines the exit. Neither requires trust as a substitute for clarity.
Divergent thinking is the cognitive process of generating multiple possible solutions by exploring many directions. It is what happens when you do not accept the first plausible answer, when you follow the evidence past the comfortable conclusion, when you ask whether the phenomenon has been named before rather than treating it as novel.
A scoping conversation takes thirty minutes and produces a clear picture of what the right configuration is and what it will cost. No obligation. No sales pressure. If we are not the right fit, we will say so.
Request a conversation