Ohio robot cop retires after zero arrests

Dublin, Ohio, gave a robot cop a trial run inside a public parking garage. Less than a year later, the machine was off the job and headed back to its maker.

Now the failed pilot raises a bigger question nationwide. Should local leaders have to prove these machines work before putting them on patrol?

Sign up for my FREE CyberGuy Report

Dublin retired DubBot on May 12 after deciding the pilot no longer fit the city's operational needs. The robot has since gone back to Knightscope.

The city's public safety page now says the autonomous safety robot pilot has ended. It also notes that Dublin added other security measures at the Rock Cress garage, including entrance and exit gate arms and mirrors.

In theory, that sounds useful. A robot moving through a parking garage could make people feel watched over. It could also give police a live look at an area without assigning an officer there full time.

Dublin spent $128,080 in the first year of the agreement. The city expects a reimbursement from Knightscope of about $60,500, bringing the final cost down to $67,548.

The original plan was larger. Dublin had planned to pay $238,440 for two robots over two years. However, the second robot never rolled out. It was supposed to serve Riverside Crossing Park, but development needs and infrastructure limits kept it from going into service.

That leaves one robot, one parking garage and a pilot that ended with no arrests, no criminal cases and no tickets.

The city also collected no other performance metrics because the pilot was meant to test the robot before any expansion.

That part should make taxpayers pause. When a city tests an expensive public safety tool, people deserve a clear way to judge whether it worked.

Security robots promise a lot. They can move around, stream video, offer a help button and act as a visible deterrent. They also give a city a technology-forward image, which can sound appealing during a public safety pitch.

Those cases do not prove that every security robot will fail. They do show that public spaces are tough testing grounds. A robot may look impressive in a demo, then struggle when crowds, tight spaces, doors, stairs and real people get involved.

What does the robot record? Who can access the footage? How long does the city keep it? Does the system use facial recognition? What happens when someone presses the emergency button? What data goes to the company?

Cities should answer those questions before a robot starts patrolling public spaces. The point isn't to reject every new tool. The point is to make sure public safety tech comes with public accountability.

If a robot starts patrolling your local garage, mall, park or transit hub, do not get distracted by the cool tech factor. The first question should be: What does it actually do when something goes wrong?

Can it connect you to a real person fast? Is someone watching the video when it matters? Can it help during an emergency, or does it mostly record what has already happened?

But let's be real here. If your tax dollars are paying for this kind of technology, your city should explain the goal before the robot rolls out. Otherwise, people may only learn whether it worked after the money has already been spent. New technology can sound impressive. However, results still count.

A robot cop patrolled a parking garage, led to zero arrests and then got sent back. That should make taxpayers ask some hard questions. But let's be real here. If local leaders are paying for AI-powered public safety tools, they should explain what problem the tech solves, how success will be measured and what happens to the data it collects. Dublin deserves credit for ending the pilot when DubBot failed to deliver enough value. A robot can look like progress, but the real test is whether it makes people safer and gives taxpayers results they can actually see.

Would you feel safer knowing a robot was watching your public space, or should your city have to prove the machine works before spending your tax dollars? Let us know by writing to us at CyberGuy.com.

Sign up for my FREE CyberGuy Report

Copyright 2026 CyberGuy.com. All rights reserved.