The Cloud Isn’t a Metaphor: What Flock Has to Do With the Data-Center Fight

Across North Carolina, communities are pushing back on a kind of building most people never thought about two years ago: the data center. Since February 2026, more than thirty North Carolina local governments have paused new data-center development. In the Cape Fear, Southport adopted a 15-month moratorium and Boiling Spring Lakes a 12-month one — Boiling Spring Lakes with no project even proposed — while Leland and Shallotte revised their development rules for data centers, and New Hanover County commissioners asked staff to re-examine the ordinances. A fair question follows, and we get asked it: does any of this have to do with Flock?

The short answer is yes and no, and the difference is the whole point. To say it plainly up front: we found no evidence that any Cape Fear data center hosts Flock data, that the local moratoriums touch Flock, or that Flock drives data-center demand. The connection we examine here is narrower — architectural and civic.

What the data-center fight is actually about

Start with what these moratoriums are not about. The objection to hyperscale data centers in North Carolina is about resources, not surveillance. Opponents point to the power grid — Duke Energy says, in its filings to state regulators, that data centers account for more than 85% of projected load growth from new economic-development projects seeking electric service — to water, since by one widely cited estimate (the Brookings Institution) a large campus can draw millions of gallons a day for cooling, and to noise and the effect on nearby neighborhoods. The local actions we reviewed focus on power, water, noise, and land-use oversight — not Flock. If Flock disappeared tomorrow, the data-center fight would go on unchanged.

The economics are contested too. In June 2026, Duke proposed a new “large-load tariff” to the North Carolina Utilities Commission that would require qualifying large-load customers, including data centers, to sign ten- or fifteen-year contracts and pay for at least 75% of their requested demand even if they use less — a structure Duke says is intended to reduce the risk that ordinary ratepayers end up covering the cost of the buildout. Consumer and clean-energy advocates argue the proposed safeguards do not go far enough. It is a proposal, now before the Commission, not yet law. That fight — who pays for the power — is a real part of the debate, and it has nothing to do with license plates.

Where Flock actually lives

And yet Flock belongs to the same story, because Flock sells cameras and a cloud-hosted surveillance platform — it is as much a cloud-AI company as a hardware maker. The camera detects passing vehicles, captures and selects images on the device, and sends those images over a cellular connection to Flock’s servers. Recent reverse-engineering of an actual Flock camera indicates that reading the plate and identifying attributes like make, model, and color happen on Flock’s servers, not on the roadside unit (WIRED). The part that makes Flock valuable to police happens in the cloud: storing those reads and turning vehicle sightings across a nationwide network into a searchable history of where a vehicle has been observed.

By Flock’s own contract terms, that cloud is Amazon. Flock’s Customer Information Security Addendum states plainly that “Flock will exclusively use Amazon Web Services (‘AWS’) for the provision of data center facilities,” and that it does not store customer data outside the United States (Flock InfoSec Addendum). The camera captures and briefly stores data before uploading it, but the searchable history police query — where your car has been — lives in a data center, not on the pole.

With more than 120,000 cameras deployed nationally — the figure Flock itself reports — the images and plate reads are a continuous firehose, and the AI that recognizes vehicles and answers a query like “show me where this car has been” is data-center compute. How far back such a query reaches depends on retention: in August 2026 Flock announced a seven-day standard retention period for new law-enforcement customers (down from thirty), with evidence preservation for active cases — while agreements can specify other periods, so existing customers may keep longer, locally set ones (Flock). The retrospective search is exactly what drew a federal court’s attention. In United States v. Kyle (N.D. Okla., Oct. 1, 2026), a deputy used Flock and Motorola’s Vehicle Manager to pull more than fifty location records over roughly a month without a warrant; Judge Sara E. Hill held that search unconstitutional — and separately faulted the extended traffic stop — and called the technology “a type of indiscriminate mass surveillance.” It is a single district-court decision, not binding nationwide, and Judge Hill acknowledged that nearly every other court to consider ALPR use had reached the opposite conclusion, which is part of why it stands out. The narrower point for us: a plate network like Flock’s, with AI behind it, is a data-center application. The cameras are the visible part; the cloud is what turns scattered sightings into a searchable history. (For how these systems work, see ALPR, explained.)

So is there a connection? Three honest ones.

1. The same civic question, with a different grievance. The strongest link is not technical — it is civic. Both controversies raise the same local-governance question: how much say residents get before consequential infrastructure becomes part of their community — what is being built here, who approved it, and can the public still weigh in? Both have drawn opposition across the usual political lines, and both are fought with the same tools — moratoriums, zoning, and votes by county and town commissioners. In Brunswick County this is not hypothetical: how the Sheriff’s Flock program was authorized, and whether it ever got a public vote, is the question we examined in who authorized the surveillance. (One caveat cuts the other way: a moratorium usually pauses new projects, not ones already approved — so “can we still say no?” often applies only going forward.)

2. The same category of infrastructure. Flock runs on the AWS cloud, which in turn depends on the same broad category of large-scale data-center infrastructure now drawing scrutiny around the country. The data-center fight makes concrete what the surveillance debate struggles to: “the cloud” where your movements are stored is not a metaphor. It is a real building, drawing real power and water, somewhere in the country.

3. What the infrastructure makes possible. This is the connection that actually matters, and it is not “Flock uses AWS, so data centers are suspect.” Banks, hospitals, and streaming services use data centers too. The point is what cheap, abundant computing now enables. Twenty years ago, reconstructing a month of someone’s movements across several states would have taken extraordinary police manpower. Today a single database query does it in seconds — which is exactly what happened in Kyle, where one search returned more than fifty sightings across multiple states. Communities debating a data center talk about megawatts, water, and taxes; they rarely talk about the capabilities all that computation puts within easy reach of government. A megawatt is agnostic about what the servers are doing. A community deciding whether to host the servers does not have to be.

To be fair to the other side

Police and Flock point to real uses, and we won’t pretend otherwise. Flock says that in July 2026 alone its network helped detect more than 1,000 missing people and over 20,000 stolen vehicles, and the company stresses that an alert “is a lead, not a conclusion” an officer must confirm (Flock). Those are the company’s own figures, not an independent audit, and should be weighed as such — though there is little serious dispute that plate readers can help locate stolen vehicles and generate investigative leads. That utility doesn’t change where the system lives or what it keeps: every search, the good ones included, runs through the same cloud and the same standing record of vehicles observed by participating cameras. The question isn’t whether such a network can ever do good. It’s whether a free country should keep a standing record of where its people drive in order to.

What we won’t claim

Here is the line we won’t cross. There is no evidence that any Cape Fear data center currently hosts Flock data, and none of the local moratoriums we reviewed appears to have anything to do with Flock. AWS runs Flock’s workloads, but those workloads could sit in any of dozens of facilities in other states. The local fights are about water and power. Anyone who tells you the Southport moratorium “shuts down Flock” is wrong, and we will not say it.

And one more boundary, because it cuts our own way: nothing we found suggests Flock itself is a meaningful driver of data-center construction, electricity demand, or water use. Against the scale of AWS, Flock’s workload may be a tiny fraction of the whole. The connection we are drawing is architectural and civic — not a claim that Flock is fueling North Carolina’s data-center boom.

Before it arrives, or after

There is an irony worth sitting with. Southport paused data centers before a single one was proposed. Boiling Spring Lakes did the same. Leland wrote rules before it received an application. These towns are deciding what protections should exist before the infrastructure shows up. With police surveillance technology, the sequence has usually run the other way: communities are asked what rules should govern the cameras only after the cameras are already watching. The data-center fight is, in part, a community insisting on the first order of operations. That instinct is worth borrowing.

The throughline

What ties these together is not a wiring diagram. It is a principle. Whether the thing being built is a server farm drawing heavily on the power grid and water supply or a camera network that records the cars that pass it, residents keep asking the same two questions: who decided this, and can we still say no? That instinct is, in our view, one of the healthier things happening in North Carolina local government right now. It deserves to be asked about the data center at the edge of town and about the cameras on the poles downtown — with the same seriousness, and the same right to a straight answer.

Related: ALPR, explained · the federal ruling that called Flock mass surveillance · where New Hanover’s plate data goes.