Flock CEO defends surveillance technology amid national backlash: ‘We shouldn’t pause progress’

At TechCrunch Disrupt 2026, Flock’s CEO Garrett Langley doubled‑down on the premise that surveillance tech is a necessary trade‑off for public safety. He brushed aside the growing backlash, saying society must accept a loss of privacy if it wants a higher chance of catching criminals. As a founder who has spent a decade wrestling with the gritty realities of running production servers and selling infrastructure to municipalities, I hear the same line of thinking from hyperscalers and VC‑backed “AI‑first” startups: “don’t pause progress.” The problem is that the rhetoric ignores the very real business‑risk calculus that independent hosting providers and city IT departments have to live with every day.

Why the “progress‑must‑continue” mantra is a red flag

Langley’s argument that “if we want a society where criminals are held accountable, we shouldn’t pause progress” mirrors the pitch you hear from big‑cloud providers when they roll out new data‑analytics services. They sell the promise of better outcomes while downplaying the cost of lock‑in, compliance headaches, and the inevitable “mistakes” that surface once the product is in production. In Flock’s case, the CEO admitted the company has already faced cancelled contracts and layoffs, yet he deflected the core concerns by leaning on anecdotes about police chiefs and “numerous crimes solved.” That’s classic hype: sell the win, hide the pain.

For an independent hosting provider, the lesson is clear: if a vendor’s narrative is built on “we can’t stop because the world needs us,” you should ask who bears the fallout when the tech misfires. In my experience, every time a surveillance system glitches, the city’s legal team, the IT staff, and ultimately the taxpayers foot the bill for data breaches, wrongful arrests, and the cost of retrofitting the infrastructure. The “progress” argument rarely accounts for those downstream expenses.

The illusion of “minimal mandated features”

Langley insisted that Flock will “provide recommendations, we’ll provide defaults, but we’re going to minimize the number of mandated features, functions, and policies.” On the surface that sounds like a hands‑off approach, but in practice it’s a way to dodge responsibility. When a city deploys license‑plate cameras that can also “detect and track people,” the lack of mandated safeguards means the municipality must build its own governance framework from scratch. That’s a massive operational risk for any local government that already struggles to staff a modest IT department.

Contrast that with the way hyperscalers handle similar concerns: they bundle compliance tools, audit logs, and policy templates into the service, precisely because they know the cost of a breach to their brand. Flock’s strategy of leaving the policy heavy‑lifting to the client is a red flag for anyone who has to answer to a city council or a board of directors. It shifts the liability from the vendor to the buyer, a classic move in the “VC‑funded hype” playbook.

Privacy trade‑offs masquerading as public good

The CEO’s claim that “if people want a better society with reduced crime, they have to offer up their privacy” is a moral framing that sidesteps the practicalities of data governance. He even referenced a cancelled contract that stemmed from a mistaken belief that Flock’s cameras performed facial recognition—a capability they do not have, but they can still “detect and track people.” That distinction matters because the legal thresholds for storing and processing movement data differ from those for biometric data, yet both sit on a slippery slope of surveillance.

From a risk‑management perspective, the moment you collect continuous location traces, you open a Pandora’s box of compliance requirements: data retention limits, access controls, audit trails, and the ever‑present threat of mission‑critical outages. In my own infrastructure runs, a single misconfiguration in a camera feed can flood a network, choke bandwidth, and bring down unrelated services. The cost of securing that data pipeline is often far higher than the marginal benefit of catching a few extra offenders.

Comparisons to driverless cars fall flat

Langley likened Flock’s technology to driverless cars, arguing that a single accident shouldn’t halt an entire industry. He noted that autonomous vehicle firms pause fleets and apply fixes after crashes. The problem is that the automotive sector is heavily regulated, with safety standards, recall processes, and liability frameworks baked in. Surveillance tech, especially when sold to municipalities, operates in a regulatory vacuum. When a camera misidentifies a suspect or a data breach exposes civilian movements, the fallout is legal, not just technical.

In my decade of running production servers, the difference is stark: a driverless car company can pull a software update across a fleet under a controlled rollout. A city’s surveillance network is a patchwork of legacy systems, third‑party integrations, and on‑prem hardware that often cannot be updated without a full hardware swap. The “pause and fix” model that works for autonomous vehicles simply doesn’t translate to municipal surveillance, making Langley’s analogy more of a talking point than a realistic risk mitigation strategy.

The staffing crunch narrative masks a deeper issue

Langley highlighted a “decline” in law‑enforcement employment post‑COVID, pointing to open positions in places like San Francisco as justification for Flock’s technology. While it’s true that many departments face staffing shortages, using that as a selling point for pervasive surveillance sidesteps the question of whether the technology actually solves the underlying problem or just adds a layer of complexity.

From a provider’s angle, the promise of “doing more with fewer staff” often translates into higher data‑ingestion rates, more storage requirements, and increased bandwidth consumption—all of which drive up operational costs for the city’s IT budget. In my own work, we’ve seen municipalities over‑commit to data‑heavy solutions only to discover they can’t sustain the recurring expenses, leading to contract terminations and, ultimately, layoffs of the very staff the tech was supposed to replace.

The ethical vacuum: leaving decisions to “others”

When pressed about abuse and invasiveness, Langley offered no concrete safeguards, merely suggesting there are ways “to curb abuse” that don’t “disrupt the legal system.” That lack of specificity is a red flag for any independent provider evaluating a partnership. Ethical frameworks need to be baked into the product, not left as an after‑thought for the buyer to invent.

In practice, the absence of built‑in audit logs, role‑based access controls, and transparent data‑use policies means the city must allocate scarce resources to develop those controls themselves. That’s a hidden cost that can quickly erode any projected ROI. Moreover, when a vendor refuses to define “acceptable use,” they effectively hand over the power to dictate surveillance scope to local officials who may lack the technical expertise to set appropriate limits.

Actionable takeaways for independent hosting providers

First, demand clear, enforceable service‑level agreements that spell out data‑retention limits, breach notification timelines, and mandatory security updates. Anything less is a gamble that could land your client in a compliance nightmare.

Second, scrutinize the vendor’s default configurations. If they claim to “minimize mandated features,” ask for a detailed risk assessment of each optional capability—especially those that enable people‑tracking. In my own deployments, the moment you enable a tracking module, you double the attack surface and the compliance burden.

Third, factor the hidden operational costs into any business case. Bandwidth, storage, and ongoing support for a surveillance network often exceed the upfront hardware price tag. Independent providers must model those expenses and communicate them transparently to municipal decision‑makers.

Finally, keep a healthy skepticism toward any narrative that frames privacy loss as a necessary sacrifice for safety. As I’ve learned over ten years of running production infrastructure, technology that promises to solve a problem often creates a new set of problems—especially when the vendor’s focus is on growth, not on the long‑term health of the ecosystem.

In short, Langley’s defense of Flock reads like a classic VC‑funded pitch: “the future is inevitable, so you better hop on board.” For independent hosting providers and the cities they serve, the smarter move is to ask tough questions, demand concrete safeguards, and remember that progress without accountability is just a shortcut to future headaches.

— Allan Ali, Founder

This article was produced with AI-assisted research and editorial support. Reporting is based on the source material cited below. Sources: TechCrunch; techcrunch.com; Global1.News (15 October 2026).

By Allan Ali, Global1.News