Work

Contracting buyers evaluate evidence, not capability claims. These are the systems we’ve built and the properties we run — named, linked and checkable where they can be.

Two industries, one job description

Nearly thirty years of this has run across two industries, both of them still going, and they look unrelated until you look at what the work actually was.

Games

1997 – present

Twenty-three shipped titles, and the most recent credits are security ones — Battlefield 6 and Battlefield: REDSEC in 2025. Anti-cheat against opponents who adapt to your detections within days. Petabyte-scale log analysis. Streaming dev kits from one controlled location. A carbon dashboard spanning an entire publisher and its players.

The founder’s career, ongoing alongside Ozdyne.

Motorsport

2008 – present

The two overlap more than they look like they should: rigging cars with microphones and pulling data off the CAN bus for Need for Speed was games work and motorsport work at the same time. It is now the ARC4 — battery pack, 48V systems, the vehicle software stack, and telemetry feeding real-time AI coaching at a race school.

The ARC4 and Apex Suite are Ozdyne’s delivered work, with ERA Advanced.

The job description never changed. Get clean data off a system that wasn’t built to give it to you. Decide what matters while it is still arriving, not in next quarter’s report. Assume something on the other side is adapting to whatever you just deployed.

That is why neither industry appears on this site as a specialism. They are where the work was proven, not the limit of where it applies — the same problems turn up in a detection pipeline, a payments platform or a factory floor, and Ozdyne contracts on all of it.