The LAPD Just Showed Us Where to Build in the Surveillance Market

I saw a post on Hacker News from forks about how the LAPD let its contract with Flock expire, citing civil liberties and privacy worries. It's an interesting piece on a big shift for mass surveillance, but honestly, the comments felt like a well-worn track: privacy advocates celebrating, law enforcement hand-wringing, and the usual stalemate.

But what caught my eye wasn't the civic debate—it was the footnote that nobody seems to be talking about: what this means for the actual security industry professionals who work with this tech every day.

Flock's network of automated license plate readers is massive, installed on private property and feeding data to thousands of departments. The ACLU and EFF have hammered them for creating a panopticon. So when a major department walks away, it's a signal. But I think the signal is being read wrong.

The LAPD isn't ditching surveillance. They're ditching a vendor that couldn't address the liability of privacy overreach. That's a procurement problem, not a philosophical awakening.

Meanwhile, inside the security industry, there's a quieter revolt happening. On PainSignal, we track problems that security professionals actually complain about. The patterns are surprising. Yes, there are 867 problems tracked just in Equipment Management, but the stuff keeping people up at night isn't about catching bad guys—it's about their own tools being the bad guy.

Take the SilentGuard Scheduling problem. Severity 4 out of 5. Marketing emails from a work management app are waking security workers up in the middle of the night. Opportunity score: 47/100. That's not a minor annoyance—that's a symptom of a deeper rot. The very systems designed to coordinate safety are disregarding the personal boundaries of the coordinators.

When I read about the LAPD walking away from Flock over privacy, I connect it to these data points. The backlash against surveillance isn't just about citizens; it's creeping into the workforce. Security guards—the same people who might use ALPR data—are fed up with being surveilled and interrupted by their own employers. The industry has two tracked problems with an average severity of 4.0 out of 5. That's screaming demand for a new approach.

The article's author and the HN crowd are focused on the public sector, but the real action is in the private market. If I'm a builder looking at this, I'm not trying to sell the next cop tech. I'm building something like SilentGuard—a scheduling tool that respects do-not-disturb hours, uses intelligent batching for alerts, and treats staff as humans with a right to sleep.

This isn't just a niche. The security industry is massive and fragmented. Thousands of small firms run on duct-taped systems. The LAPD decision is a market signal: privacy-first is not just a marketing term. It's an operational requirement. The next generation of security software won't win on data aggregation; it'll win on consent, transparency, and humane design.

Investors should take note. While everyone chases the generative AI shiny object, here's a sector where the pain is real, specific, and unaddressed. The opportunity score on SilentGuard is 47 out of 100—not a guaranteed unicorn, but a solid starting point for a capital-efficient SaaS targeting an underserved vertical. Combine that with the broader tech backlash, and you've got a tailwind for any tool that replaces intrusive monitoring with respectful coordination.

I'm not saying Flock is going away. They have over 5,000 agencies locked in. But the LAPD's move, paired with the data we're seeing, suggests a split in the market. On one side, traditional surveillance tech that courts controversy; on the other, privacy-centric operational tools that might never make headlines but will quietly eat the industry from within.

For vibe coders out there: the problems are documented. The demand is measurable. The incumbents are vulnerable. You don't need to solve the surveillance debate. You just need to let a security guard sleep through the night.