NextFin News - A proposed datacentre on Brick Lane has become a political test of how much of central London should be reserved for digital infrastructure, especially when that infrastructure competes directly with housing and neighbourhood character. The plan, submitted for part of the former Truman Brewery site, has drawn resistance from local residents who say the land should be used for homes rather than a facility built to serve latency-sensitive trading operations in the City of London.
The planning documents show the project would cover 5,200 square metres and have a peak output of 5.2MW. Campaigners say that scale is enough to power about 15,000 homes, which turns the issue into an unusually concrete trade-off: a central London site with scarce grid capacity could either support a power-hungry data operation or be directed toward uses that create more visible local value. The documents say the site would be used mainly for high-frequency trading, a business model that depends on being close to the City because milliseconds matter.
That detail is crucial. This is not just a generic AI story with a convenient technological label attached to it. It is a planning dispute over whether a prime inner-London site should host an energy-intensive financial utility that benefits from proximity to the Square Mile, or whether the same land should be allocated to housing in a borough where that need is already acute.
Jonathan Moberly, a resident and member of the Save Brick Lane campaign, said the project would do nothing for local people and argued that the site should instead be used for housing, ideally council homes.
“We have a severe housing crisis here and this site should be used to build affordable – ideally council – houses. Instead we are talking about this datacentre, which will bring literally no benefit to anyone living here.”
The political sensitivity is heightened by the location itself. Brick Lane is one of east London’s most recognisable streets, associated with curry houses, bagel shops and late-night foot traffic, and the Truman Brewery site has long been part of the area’s transition from industrial land to a mixed commercial and cultural district. In that context, a datacentre is not being proposed on a blank slate. It is competing with an existing urban identity and with the possibility of more housing density in one of the capital’s most pressured neighbourhoods.
What makes the row especially revealing is that the project’s stated use case is narrower than the broad “AI” label that often accompanies data infrastructure debates. The documents say the facility would mainly serve high-frequency trading in London’s nearby financial district. That means the economic logic is not about serving consumers or broad digital demand, but about shaving latency off financial transactions. The same central location that irritates residents is the very thing that makes the project commercially attractive.
That creates a familiar urban policy dilemma with a new technological wrapper. A datacentre can be a critical enabling asset for the financial system, but it is also a low-visibility, high-resource building that can outbid other land uses on the basis of private returns rather than public benefit. In a city such as London, where space is scarce and every site has an alternative use, that tension is unavoidable.
Why The Opposition Is So Strong
The opposition is not simply about aesthetics or NIMBY politics. Residents are responding to a straightforward distributional question: who gets the benefit of the project, and who bears the cost? If the answer is a small number of trading firms and a broader financial ecosystem, while local residents absorb the disruption and lose the chance of housing, then the political coalition against the scheme becomes easy to build.
That is why the campaign has been able to cast the issue in housing terms rather than only energy terms. A datacentre on a city-centre site does not just consume electricity; it also consumes optionality. Once a parcel of land is tied up in a technically efficient but socially narrow use, the neighbourhood loses the possibility of a more housing-intensive or mixed-use outcome.
The point is not that datacentres are illegitimate. Britain needs more compute capacity, and the AI boom has made the infrastructure question more urgent. But the Brick Lane proposal shows that the politics change depending on where the facility sits. A campus on the edge of a logistics park is one thing. A facility on a culturally important street in inner London, adjacent to a housing-pressured borough and close to the City, is another.
Jonathan Moberly also said the logic being used to justify the building was wrong for the neighbourhood.
“In some cases the government might say ‘oh you all want your Instagram feeds or TikTok so you need this’ but that is not the case with this proposal. The value of putting one here is for high-frequency trading because of its proximity to the City, where milliseconds count.”
That quote matters because it exposes the real tension in the project. The local argument is not against technology in general; it is against a site-specific allocation of value. Residents are being asked to accept a building whose benefits accrue elsewhere and whose purpose is tightly linked to the financial district rather than the immediate community.
What The 5.2MW Figure Really Means
The 5.2MW peak output is small compared with the biggest industrial energy users, but in dense urban planning it is still a serious load. The headline figure campaigners cite - enough to power about 15,000 homes - gives the number political force, because it translates a technical planning metric into an everyday comparison that residents can understand. That comparison does not mean the project literally prevents 15,000 homes from being powered in all circumstances, but it does show why the proposal is easy to frame as a trade-off against housing and other civic uses.
In London, the most contentious infrastructure projects are often not the largest ones, but the ones that collide with multiple constraints at once: land scarcity, electricity availability, transport access and planning politics. Brick Lane has all four. That is why even a 5.2MW site can become politically significant. It is not the absolute scale of the load that matters most; it is the scarcity of the setting.
There is also a broader lesson for the AI build-out. Much of the public discussion around artificial intelligence imagines new data campuses as remote, high-capex industrial assets located well outside the city. The Brick Lane case shows a different reality: some of the most valuable facilities are still those close enough to financial markets to reduce latency and preserve competitive edge. Those are the projects most likely to run into planning resistance because they occupy some of the most contested land in the country.
That is where urban policy becomes an investment issue, even if the story is not about listed companies or share prices. Land adjacent to the City of London is scarce precisely because proximity has economic value. If a datacentre can monetize that proximity more effectively than housing or mixed-use development, it may win the first round. But if planning rules and local opposition push back, then the value of the site has to be reconsidered in civic rather than purely financial terms.
What Happens Next
The immediate question is whether the planning process can accommodate a use that is technically efficient but politically unpopular. If the proposal advances, it will signal that central London remains open to infrastructure tied to the financial system even when local resistance is intense. If it is blocked or substantially altered, the result will reinforce the idea that the next wave of compute capacity will need to move to less contested parts of the capital or beyond it.
Either outcome tells investors and policymakers something important. The bottleneck is no longer only software demand or hardware availability. It is also planning permission, grid access and the social licence to place energy-intensive infrastructure in dense urban areas. For London, that could mean AI and trading capacity grow most easily where the city has already been industrialized for digital use; for residents, it raises the more basic question of how much of the city should be sacrificed to low-employment but high-value computing assets.
The Brick Lane row is therefore not a quirky local dispute. It is a preview of the compromises that will define urban AI infrastructure in Europe: high-value compute wants centrality, while communities want homes, public utility and a neighbourhood that still looks like a place people live in, not just a place where milliseconds are monetized.
Explore more exclusive insights at nextfin.ai.
