The machines we dreamed about are becoming real
The machine outlasts any single AI model. Why we started a new company to help Physical AI move from impressive demos to fleets people can depend on.
By Amit Ezer →Lessons from managing hundreds of thousands of edge devices, why Physical AI makes those problems harder, and why we are building fleet infrastructure again.

In 2018, Amit and I kept running into the same problem from different sources: companies were shipping more and more connected products into the world, but once a product left the lab, it was very hard to maintain remotely.
So we founded Upswift, a fleet management platform for Linux devices. Fast forward few years, JFrog acquired Upswift to close the loop from Artifactory to the edge device.
Now Amit and I are starting again - We’re building the infrastructure layer for Physical AI fleets.
This post is about why, and why now.
The short version: everything our customers taught us about IoT and edge fleets in production is coming back in robotics, about 10x harder. And the timing is right. Not too early but early enough.
Upswift was a cloud platform for fleets of Linux, IoT, and edge devices. We provided tools for continuous monitoring, remote control, device health, anomaly detection, and secure over-the-air software updates.
Our customers managed through the platform hundreds of thousands of devices worldwide. They taught us most of what we know about real world production. A few lessons stuck.
Our customers were almost never “IoT companies.” They made casino machines, welding machines, and coffee roasting machines. One built a life-saving device mounted above swimming pools to prevent drowning. Another built a dog training robot that plays commands and throws a snack when the dog gets it right. Completely different products, completely different industries, and completely different scale. But all of them had the same problems: devices far away, updates that have to land safely, and a team that needs to know what’s actually running. When the device is watching a pool, “mostly works” is not good enough.
Every device we managed at Upswift was deterministic. A coffee roaster ran its profile. A welding machine ran its program. The dog robot played a command, waited for a sensor, and threw a snack. Same input, same output, every time. When something broke, it broke the same way on every unit, and the logs told you where.
That predictability was the hidden foundation of everything we built. A canary rollout works because a bad build fails the same way on ten devices as it would on ten thousand. Monitoring works because “healthy” has a clear definition. Rollback works because the old version behaves exactly like it did yesterday.
AI-powered machines break that foundation. They run models: VLA (vision-language-action) models that turn camera input and instructions into motion, and World Models that help them predict what happens next. They don’t follow a script. They make decisions in real time, many times a second, based on what they see right now: the light in the room, where a box landed, whether a person just walked by.
That shift, from executing instructions to making decisions, is the real change. It’s why I think the fleet problem doesn’t just grow in Physical AI. It changes shape.
Every lesson above still holds. Here’s what makes each one harder.
Same lessons. Higher stakes, more moving parts.
The models are arriving fast:
That last point matters a lot to me. When a model can be adapted to a new task with a couple of hundred examples, you get many versions of many models, running on many robots. That’s a fleet problem.
Honestly, most of this is still in labs and early-partner deployments. Fleets of AI-powered robots in production are not everywhere yet.
That’s exactly why I think the timing is right.
When we started Upswift, edge devices were spreading fast, but there wasn’t a standard in terms of managing them in production. Teams built their own update scripts, their own dashboards, their own remote access. Most of it broke the first time the fleet grew 10x. The companies that used Upswift moved faster and slept better..
Physical AI is at that same point. The models are here. The fleets are next. If the infrastructure only shows up after fleets scale, every robotics team will rebuild the same fragile plumbing, and some of them will learn the lessons in the physical world, where mistakes cost more than downtime.
So, Not too early: the models are real. Early enough: there’s still time to build the infrastructure layer before the fleets need it badly.
I’m excited in a way I haven’t been in a while. Amit and I have done this once, on devices that were predictable by design. Now they see the world, make decisions in real time, and act on them.
This is a marathon, not a sprint. We’re at the starting line, and we’re glad to be here early enough.
If you’re running robots in the field, or about to, I’d love to hear what’s hard for you.
See Physicalfleet run a live fleet, or talk to the team about yours.
Free for up to 5 devices · Works with robots of every shape and size