Why I Built VEER After My Yamaha MT-07 Was Stolen

I did not set out to build another gadget for a crowded market. I started building VEER because my Yamaha MT-07 was stolen. It is difficult to describe the feeling of walking out and finding the space where your bike should be completely empty. Beyond the financial loss, there is the frustration of knowing that something you worked for and enjoyed riding can disappear in minutes—and that the technology you trusted may not be enough when it matters most.

I had a MetaTrack system fitted to the bike, but my experience showed me that simply having a tracker is not the same as having a theft-proof security system. If a device can be found, disabled, disconnected, or prevented from reporting, the location dot in an app offers very little reassurance. That experience changed the way I thought about motorcycle and vehicle tracking: security cannot be an extra feature. It has to shape the hardware, connectivity, alerts, and software from the beginning.

I am also a riding and driving enthusiast, so I use RaceBox and Dragy for performance data. They can be useful tools, but they solve a different part of the problem. One device helps with lap or sector timing, another focuses on acceleration runs, and a separate tracker watches the bike or car when it is parked. The result is several pieces of hardware, several accounts, and several apps for one vehicle.

In my own use, the applications could also feel buggy and inconsistent. A device is only as useful as the software around it: pairing failures, unreliable syncing, confusing workflows, or data that is hard to access quickly can turn a clever product into a frustrating experience. I wanted the information I care about to live in one dependable place.

That became the idea behind VEER: one GPS platform for monitoring, security, and performance tracking. Instead of treating those as separate products, I wanted them to work together. The same accurate position and motion data that can show a journey or measure a run can also detect unexpected movement, preserve evidence around an incident, and help an owner respond quickly.

For everyday monitoring, that means a clear live location, useful journey history, and the ability to understand where and how the vehicle has been used. For security, it means fast alerts, resilient connectivity, concealed hardware, and safeguards designed around the reality that a thief may try to defeat the tracker. For performance, it means capturing high-quality GPS and motion data without needing to assemble a collection of disconnected devices.

A tracker is not just a box hidden in a vehicle, and it is not just an app. It is a chain: the sensors must capture the right data, the device must stay powered and connected, the service must process events reliably, and the app must make the important information obvious. A weakness anywhere in that chain can make the whole system fail at the exact moment it is needed.

That is why I am approaching VEER as an integrated system. The tracker, connectivity options, driver fobs, live dashboard, alerts, and performance tools are being designed to support one another. The goal is not to add features for the sake of a longer specification. It is to remove the gaps I experienced as an owner.

VEER is being built because I wanted a product I could genuinely trust with my next motorcycle or car. I wanted security that assumes someone may attack the system, monitoring that is useful every day, and performance data that does not require another device and another unreliable workflow.

I cannot undo the theft of my MT-07, but I can turn that experience into something better: a tracker designed by someone who knows what it feels like when the existing solution is not enough. That is the standard I want VEER to meet—for my own bikes and cars first, and ultimately for every owner who puts their trust in it.