How VoyagerOTA Started

VoyagerOTA began as a small experiment while I was working on a firmware project under R&D. I was the sole programmer on the software side, writing firmware, mobile app, and backend services. As development progressed, our R&D head, a mentor I deeply respect, mentioned the system might eventually be deployed to out of city clients. That changed how I looked at it.

As the firmware grew more complex, I kept asking myself how I would update devices later if a bug or feature change was needed. Most OTA tools were LAN-only, overly complex, expensive, or complete overkill. I wanted something simple and reliable.

I built a minimal prototype with a small custom API and some OTA logic in the firmware and deployed it to a VPS. But small decisions added up. Tight coupling between firmware and service made changes fragile, especially if I wanted to reuse the system later. So I split them.

That separation changed everything. What started as a tiny utility became a reusable platform, not just for that project but for anything that might need OTA in the future.

The Name and Inspiration

I’ve always loved space, which is why I named the project VoyagerOTA after NASA's Voyager probes, still sending data from the edge of the solar system. They carry a Golden Record with music and messages from Earth. Voyager 1 once had software problems billions of miles away. NASA called the engineers who originally worked on it they studied old plans, ran tests, and sent a software fix. And it worked. That story inspired me that even a small signal can have a big impact. VoyagerOTA is my small signal into the world it's not perfect, but it works.