--- title: "The case for unifying a city's surveillance networks" date: 2026-08-02 summary: "Why citywide cameras cannot talk to each other—and how a shared network could change that." type: long-form tags: ["cities","security","infrastructure"] --- Walk through any major business district and you can count cameras everywhere. Gated estates have their own loops. Malls and hotels run their own systems. Government cameras sit at traffic lights, bus stops, and major junctions. On paper, that looks like a lot of coverage. In practice, most of it becomes useless the moment something actually happens. The problem is not that cities have too few cameras. The problem is that the cameras they already have cannot talk to each other. Different vendors. Different formats. Different control rooms. No shared network. No common protocol. So when police need to track a suspect vehicle across a few streets, they usually cannot just pull up a feed and follow the trail in real time. Someone has to visit each estate, mall, hotel, or office building. Someone has to request access. Someone has to copy footage to a drive. By the time the useful clip is found, the window for real-time response has already closed. This is not a hardware problem. Cities do not need to start by buying thousands of new cameras. They need the cameras they already have to work together. ## What is actually broken The current model breaks in three obvious places. First, private and public systems operate in silos. A residential estate may have useful street-facing cameras, but those feeds sit inside its own security room. A mall may have cameras covering a public road, but that footage is only accessible through the mall's own system. Government may have traffic cameras nearby, but those feeds live somewhere else entirely. Second, vendors do not always share a common language. One building uses one camera brand. The next uses another. The city uses a different stack. Each system may work fine on its own, but the city has no easy way to coordinate them during an incident. Third, almost everything is reactive. Footage gets pulled after something has happened. A person reviews it manually. The system helps explain the past, but it rarely helps shape the response while the event is still unfolding. That is the wrong way to think about city surveillance. ## Fix the software, not the hardware The expensive answer is to rip out everything and start again. That is unrealistic, and in most cities it will not get funded. The practical answer is a middleware layer: an open-architecture video management system that sits above the cameras already installed and gives them one shared operating layer. This works because of a standard most people have never heard of: ONVIF. Think of it as a universal translator for security cameras. If a camera is ONVIF-compliant, a central system can usually discover it, authenticate it, and pull its feed regardless of who manufactured it. That changes the shape of the problem. Instead of asking every estate, hotel, office building, mall, and public agency to replace its cameras, the city can ask them to connect selected feeds into a federated network. Suddenly, you can put a residential estate's cameras, a mall's cameras, and the city's traffic cameras on the same dashboard.
Diagram showing private estates, commercial venues, and municipal hubs feeding unified middleware, a central VMS platform, AI analytics, and a governance layer.
Two things become possible once you do this. **Federated control.** Estates and businesses should not have to surrender their entire security systems to a central authority. They should keep ownership of their own footage. They should keep their internal cameras private. They should decide which outward-facing feeds are eligible for sharing, especially the ones covering public roads, entrances, exits, and perimeter lines. The city command centre does not need to see inside people's homes, offices, hotel corridors, or private compounds. It needs a lawful, auditable way to access the public-facing cameras that help reconstruct or respond to events in shared space. That is the difference between integration and seizure. A well-designed system lets private operators keep control while still contributing to public safety. **Automated alerts.** The second benefit is automation. The goal should not be to pay people to stare at thousands of screens. That model does not scale, and it fails exactly when attention matters most. The system should watch for specific signals and escalate only when something is worth reviewing. License plate recognition can flag a wanted vehicle. Object detection can identify a stalled vehicle blocking a key route. Crowd detection can highlight abnormal gathering patterns. Perimeter analytics can flag activity around restricted infrastructure. A human operator then reviews the alert and decides what to do next. This is not about replacing judgment. It is about using software to make sure human attention is spent on the few moments that actually matter. ## The infrastructure problem nobody talks about Even a perfect software layer fails if the physical infrastructure is weak. If you have lived in Lagos for more than a week, you already know the problem: power drops, network links fail, fibre gets cut, and the system that looked good in a presentation suddenly goes dark. A citywide camera network has to be built for that reality. Every important camera node needs local resilience. That means solar panels and battery banks where possible, especially for road-facing and perimeter cameras. A camera that depends entirely on one unstable grid connection is not public safety infrastructure, just a decoration. The network also cannot depend only on buried fibre. Fibre is valuable, but it is fragile in cities where construction, road work, and informal digging happen constantly. A wireless mesh can give the system a second path. Cameras and network nodes can relay data to each other and reroute around dead links instead of collapsing when one line is cut. The third piece is edge processing. You should not stream everything, all the time. Most of what a camera sees is nothing happening. Sending every frame from every camera to a central command centre is a fast way to waste bandwidth, overload storage, and create a system that cannot scale. Processing should happen close to the camera. The edge device should detect motion, plates, anomalies, or other configured events locally, then send metadata or selected clips back to the centre when something matters. That is the difference between a citywide system that scales and one that chokes when camera number 501 comes online. ## Who pays for it A city cannot fund this entirely with public money. It has to be a partnership, and the incentives have to match the type of participant. For residents and private estates, the model should be a carrot, not a stick. Install a compliant outward-facing camera. Agree to share specific feeds during defined emergencies. In return, receive a property tax rebate, subsidised hardware, discounted maintenance, or priority access to verified incident support. Nobody wants government mandating what happens inside a private compound. The better approach is to reward people for contributing useful public-facing coverage while leaving private areas private. Commercial venues are different. Malls, hotels, logistics hubs, event centres, fuel stations, and large office complexes draw public traffic and create public safety obligations. For them, camera compliance can reasonably be tied to operating licenses, especially for entrances, exits, loading bays, and street-facing perimeters. If a business benefits from public movement around its property, it is not unreasonable to require basic, interoperable coverage of the public edges of that property. ## The part that actually matters: privacy This is where most surveillance proposals fall apart, and honestly, where they should get the most scrutiny. A unified camera network only works if people trust that it will not become a tool for casual monitoring, political abuse, commercial spying, or personal harassment. That trust cannot be built on speeches. It has to be built into the system. Access should always be logged. Nobody should be able to browse feeds casually. Every camera view should be tied to an active case file, with a permanent record of who accessed the feed, when they accessed it, what they viewed, and why. Footage should not live forever. Set a hard purge window. Two to four weeks is reasonable for routine footage. If a clip is not explicitly locked as evidence for an active investigation, it should be deleted automatically. Emergency access should still leave a paper trail. If law enforcement needs a private feed during an active emergency without a warrant, the system can allow a time-limited override. But that override must be logged, reviewed, and followed by proper legal authorization within a defined window, such as 48 hours. If the authorization does not arrive, access should be cut automatically and regulators should be alerted. These rules should be enforced in code, not buried in a policy manual. Rules people can quietly ignore are not rules. They are suggestions. ## The real design problem Fixing city surveillance is not really about better cameras. It is about getting the cameras that already exist to cooperate. It is about building infrastructure that survives bad power and bad networks. It is about using analytics to move from after-the-fact review to real-time response. And it is about putting automatic limits on who gets to look at what. Cities that get this right will not just be safer. They will be safer without becoming the kind of surveillance state nobody wants to live in. That balance is the whole design problem. Get it wrong in either direction, and you build something worse than what you started with.