From September, 200 city cameras and three plate-reader feeds arrive on one police screen.

What the city runs

What is in the Axon package

The council description reads only "public safety equipment, hardware and software." The pricing schedule inside the signed contract is specific.

Neither the drones, the counter-drone radar nor the plate readers were named in the 21-minute presentation to council. Across the full transcript of that meeting, "ALPR" and "plate reader" appear zero times.

What actually connects to it

The Axon system is not a replacement for what the city already has. It is a hub. A planning document inside the contract — the Fusus Qualifier Summary — lists exactly what gets plugged in.

200 cameras the city already owns

The 250 purchased streams are allocated in two phases:

These are not new cameras. They are the city's existing traffic and parks networks, being connected to a police platform. Phase 1 is "connect up to 100 CCTV video streams." Phase 2 is "deploy remaining core streams across the jurisdiction."

It is worth reading why the traffic cameras were bought. In May 2016 the council approved 70 Axis pan-tilt-zoom cameras at signalized intersections, on top of the 20 the city already had, for $189,350. The resolution states the purpose three separate times: "to monitor traffic flow," "for helping with traffic signal timing," and to "cut down on unnecessary maintenance trips to intersections." Nothing in it contemplates police use. ↓ resolution

Do those cameras read plates? No — and they can't

The line item is called "CCTV AI streams," which invites the assumption that connecting a traffic camera turns it into a plate reader. It does not, for two separate reasons — one contractual, one physical.

The statement of work is worth quoting exactly:

"The Agency is responsible for identifying which streams should be configured for AI object detection. The actual number of AI streams available is contingent upon stream characteristics and hardware capabilities, as not all CORES support AI analytics."

The named function is object detection, not plate recognition. The police department chooses which streams get AI, after deployment, so which traffic and parks cameras become analytic cameras is decided later and appears nowhere in the contract. And not every camera can have it; it depends on the edge hardware.

Beyond that, the platform is not built to read plates off ordinary video at all. Axon's published documentation describes Fusus as ingesting plate reads from dedicated systems rather than generating them — the sources it lists are Axon Fleet 3, Axon Outpost, "Works with Axon" partner cameras, Jenoptik Vector, Vigilant Solutions and Flock Safety. The contract's own integration clause says the same thing from the other direction: Fusus connects to IP cameras "using industry-standard RTSP and ONVIF protocols" — a generic video pipe, not a plate-reading one.

The hardware settles the rest. Plate capture needs a purpose-built camera: a locked-down field of view, dedicated optics, infrared illumination, and shutter speeds fast enough to freeze a moving vehicle — well under 1/500th of a second. A pan-tilt-zoom dome bought in 2016 to watch traffic flow has none of that, and it can be pointed away from the road at the moment it matters. The city plainly knows the difference: when Transit actually wanted a plate camera in 2024 it bought one AXIS Q1700-LE, a model sold specifically for license-plate capture, alongside 55 ordinary cameras. Axon's own new Lightpost product is built around the same family, the Axis Q1800.

So the traffic and parks cameras arrive on the police platform as what they are — live video, searchable by location, some of it flagged for crowd or intrusion alerts. The plate reads come from the plate readers.

The contract does name the functions, and they are narrower than "AI" suggests: "Supported AI functionality may vary by configuration type, including crowd detection, or object intrusion zone detection." Crowd detection counts people in a scene. Intrusion-zone detection fires when something enters an area someone has drawn on a map. Neither reads a license plate.

One further number from the same section: Axon will place cameras on the Fusus map "up to a maximum of 5000 during the implementation period" — a mapping capacity twenty times the 250 streams actually purchased.

Private cameras, by invitation — and by ordinance

Axon builds the city three things here. A branded Community Connect microsite, a landing page for "camera registration and integration of community video assets." $1,000 of marketing materials for public outreach. And a Fusus Registry — "a map of all the public and private security cameras in a location," so that after an incident investigators "can easily locate and reach out to all the camera owners in the vicinity to request video footage." Registering is voluntary; being mapped is what the registry is for.

That invitation lands on top of an obligation that has been in the municipal code since 2015. Chapter 60A requires a named list of businesses — banks, convenience stores, liquor stores, hotels, firearm dealers, coin dealers, payday lenders, after-hours businesses — to install and maintain video surveillance, with cameras covering every point of sale, every entrance and exit, and the parking lot. If a crime occurs the business must give police "immediate access to the Media containing the recorded event" and a copy within 48 hours; and if the system is web-enabled or wireless, the business "shall enable the Police Department to directly access the live system during incidents requiring a police response or intervention." The Chief of Police may inspect any such system. The council repealed and re-enacted the chapter on April 14, 2026, ten weeks before the Axon vote, and adopted Resolution 0474-04-26 setting the technical minimums — 2K resolution, 30 days of storage, 15 frames per second, infrared outdoors, and the ability to email a screenshot to an officer on request. The Police Department reviews those standards annually and recommends the updates. ↓ 2015 ordinance ↓ 2026 ordinance

The plate-reader feeds

"Expected ALPR Integrations: Fleet3 LPR; Flock ALPR; Milestone xProtect LPR"

Fleet3 LPR is Axon's in-car camera, which reads plates — Axon's own cooperative contract classifies its Fleet line as an ALPR product. Flock ALPR is the existing 70-camera network. So the platform is built to take plate reads from the city's own patrol cars and from the fixed Flock network, alongside the 20 Axon Outpost readers the contract buys outright.

Notably, Vigilant is not on the list. The squad-car readers the city has run since 2015 are not named as an expected integration — and not because the platform cannot take them. Vigilant Solutions is one of the ALPR sources Axon's own documentation lists as supported in Fusus. It could have been named here. It was not.

And the rest of it

The same document lists Hexagon Intergraph for both dispatch and automatic vehicle location — so live police vehicle positions land on the same screen — plus RapidSOS caller location and Skydio drone feeds.

Put together: roughly 200 municipal cameras, three plate-read sources, registered private cameras, drone video, 227 body cameras and 200 in-car cameras with live streaming, vehicle positions and 911 caller locations, in one interface.

Two systems that are not in that picture

Vigilant — the term ran out five weeks ago

Every Vigilant document the city holds was a scan with no searchable text. They have now been transcribed, and they describe an eleven-year program that reached a public vote exactly once.

That once was the beginning. In July 2015 the council voted unanimously to buy a "Vigilant Intelligent Led Policing Package" from Turn-Key Mobile for $31,700 — paid for with a $30,000 Methamphetamine Drug Hot Spots grant from the Governor's Office of Drug Control Policy and $1,700 of asset-forfeiture money, not city funds. The service agreement signed that November ticked the Intelligence-Led Policing tier, which is the tier that carries Vigilant's facial-recognition products — a FaceSearch account and FaceSearch Mobile Companion. When the city re-contracted in 2021 it ticked the Basic package instead, and left that box empty. The contracts record which tier was bought; they do not record whether any face search was ever run.

From there it never went back to council. A new contract in April 2021 — six plate readers for two police cars, $46,860 — was executed on the City Manager's signature, its resolution number recorded on the cover sheet as TBD. Then four one-year renewals, each also by signature:

The renewals are not buying cameras. The single line item on all four is "Investigative Data Platform Annual Subscription" — a hosted account on Vigilant's LEARN network, where, under the 2021 agreement, plate data collected by one agency is "freely available" to other agencies that subscribe.

Two things follow, and they should be held apart. Amendment No. 4's term ended on June 25, 2026. As of this writing the city's portal holds five Vigilant documents and Amendment No. 4 is the last of them; there is no Amendment No. 5, and no Vigilant or license-plate document of any kind bearing a 2026 date. The portal itself is current — it holds contracts filed in June 2026.

That is not yet proof of anything, and the reason is in the record. Amendments 2, 3 and 4 were each signed five to eleven weeks before the term they covered. But Amendment No. 1 was signed on August 17, 2022, for a term that had begun on June 26 — executed nearly two months retroactively. A renewal following that precedent in 2026 would not have been signed yet. If nothing is filed by late September, that explanation runs out.

What can be said now is narrower: the subscription's documented term has expired, no renewal appears, and Vigilant is absent from the Axon contract — not as an integration, not as a system being replaced, not at all. One records request would settle it.

Worth noting who owns it: Motorola Solutions acquired Vigilant in 2019. The vendor supplying the city's oldest plate readers is the same one supplying its radios.

Motorola — radios, not cameras

Motorola is the city's largest public-safety vendor by document count, with contracts running back to 2001, but all of it is radio communications rather than surveillance. The current agreement — APX Next Radios Phase 3, $1,950,000, July 2026 through June 2034 — was signed two weeks before the Axon package.

It is out of scope here because radios are not cameras. The connection worth holding onto is the ownership one above.

The timeline

• 2012 In-car cameras

  Baycom Arbitrator squad-car camera system — a decade before Axon.

  ↓ agreement
• May 2015 Chapter 60A — businesses must run cameras

  Named business types required to install surveillance and give police live access.

  ↓ ordinance
• July 2015 Vigilant — first plate readers

  $31,700, approved unanimously. Paid from a meth-enforcement grant and asset forfeiture.

  ↓ resolution ↓ agreement
• May 2016 70 traffic cameras, for signal timing

  Added to 20 already installed. These become the Axon platform's Phase 1 and 2 streams.

  ↓ resolution
• January 2018 First city drones

  Three UAS on Homeland Security grant funds, one stationed with Iowa Task Force 1.

  ↓ MOU
• April 2021 Vigilant — enterprise license

  Six readers for two cars, $46,860. Renewed by signature in 2022, 2023, 2024 and 2025.

  ↓ contract ↓ amd. #4
• September 2022 Axon — Tasers

  $709,853, running to December 2027. The city's first Axon contract.

  ↓ contract
• April 2024 A plate camera at the bus garage

  One AXIS Q1700-LE license-plate camera among 56 in a Transit security replacement.

  ↓ contract
• November 2024 Flock — 70 fixed cameras go live

  Approved June 2024 at $499,250; the two-year clock ran from installation.

  ↓ contract
• February 2025 A mobile Flock trailer, by grant

  CRPD applies to Iowa Homeland Security for a camera trailer "which integrates with our current Flock camera system."

  ↓ application
• April 14 2026 Chapter 60A re-enacted

  Business camera mandate carried forward; technical minimums updated on police recommendation.

  ↓ resolution
• April 2026 Axon equipment trial

  CRPD trials Axon in-car and body cameras free for 90 days.

  ↓ agreement
• June 23 2026 Axon — $14.6M package approved

  Ten-year term, September 2026 to August 2036.

  ↓ contract
• June 25 2026 Vigilant's term ends

  No Amendment No. 5 appears in the city's portal.

  ↓ amd. #4
• September 1 2026 Axon term begins

  Outpost cameras scheduled for delivery August 1. Three plate-reader systems now running at once.

• October 1 2026 Flock renewal decision window closes

  Thirty days before the term ends — the notice date under both readings of the contract.

  ↓ contract
• October 31 2026 Flock term ends, or renews

  Renewals from here run November through October.

  ↓ amendment

Flock: what the subscription reaches, and how it renews

The 70 fixed readers are the visible part. The order form the city signed also lists what the software reaches, and the list runs well past Cedar Rapids: State Network, "allows agencies to look up license plates on all cameras opted in to the statewide Flock network"; Nationwide Network, "all cameras opted in to the nationwide Flock network"; Law Enforcement Network Access, all law-enforcement Flock devices directly shared with the city; and Community Network Access, "all privately owned Flock devices within your jurisdiction that have been shared with you." Searches run on plate, and on Vehicle Fingerprint — "vehicle type, make, color, license plate state, missing / covered plates, and other unique features like bumper stickers, decals, and roof racks."

The city's own specification, written into the scope of work, is more restrictive than that reach might suggest, and is worth having on the record. It requires that the system "shall not be structured as a facial recognition system," that it "shall not have the ability to be used for/in traffic enforcement," that data "shall be owned by CRPD" and not sold or shared by the vendor, and that footage be discarded automatically after 30 days. It also requires — and this is the provision that matters most for anyone filing a records request — that the system "provide web-based access/hosting including the ability to audit the trail of access and contain search justification capabilities." The order form confirms the subscription includes a reporting tool covering "user and network audits, plate read reports, hot list alert reports, event logs." Those records are a contracted feature of the system the city bought. ↓ contract

How it renews is genuinely unsettled

The October 31 date is not in any council record. It comes from a one-page amendment signed in October 2025, which moved the end date because the cameras were installed later than the contract assumed. It changed the price by $0.

The amendment also sets the pattern for what follows: "any subsequent renewals will be November through October."

What happens at that date is worth pinning down, because the paperwork points two ways at once — and the two clauses sit one paragraph apart in the same document.

Section 7.1 of the Flock master services agreement is standard vendor language: the agreement "will renew for successive renewal terms" — the order form sets that term at 24 months — "unless either Party gives the other Party notice of non-renewal at least thirty (30) days prior to the end of the then-current term." On its own that is an automatic renewal, and it would make the operative deadline roughly October 1, with silence counting as consent.

Directly beneath it is section 7.2, which has no heading of its own where every other clause in that section has one — the mark of a term added to the vendor's standard form:

"Customer will contact Flock to renew the agreement via contract amendment at least 30 days prior to the end of the current term."

That is the opposite mechanism: an affirmative act, in writing, to continue. It matches the city's own contract, which says the parties "may renew the original Contract for two (2) additional two-year time periods by mutual agreement," and it matches what actually happened last time — the October 2025 change was executed as a contract amendment, not left to run automatically. Neither document contains an order-of-precedence clause; each recites that it and its attachments are the entire agreement.

Checking this yourself

Every ↓ link above opens the signed document on the city's own portal. If one stops working, they are all findable by hand:

• Go to the Cedar Rapids public records search
• Set Search Type to Public Contracts, Resolutions and Ordinances
• Enter the contract number in the CIP/DID # box — PUR0424-254 Flock, PUR0822-039 Vigilant, PUR0526-344 Axon package, PUR0822-052 Axon Tasers, OB449776 Sensys Gatso, PUR0122-180 redaction software, OB1380220 Chapter 60A, PUR1215-116 traffic cameras, PD0079 Flock camera trailer

Built from 363 signed contract documents — 2,545 pages — retrieved from the City of Cedar Rapids public contracts portal, plus council packets, presentations and the June 23 2026 meeting transcript. 2,227 of those pages were scans with no searchable text and were put through optical character recognition for this report; every figure quoted from one has been checked against the page image. Underlying documents and data available on request.