Rewriting an AI video surveillance platform

Whose product this is

Jetsons Living builds the Jetsons Management System, an AI video surveillance platform that works with IP cameras. The product is theirs: their idea, their architecture, their design. They came to us for the build.

Version two was a full rewrite rather than a set of changes to version one. Jetsons Living asked us to keep everything the platform already did, make it substantially faster throughout, and put a new design on it. For a product that competes on what it does and how quickly it does it, that step mattered commercially.

What we did

We wrote most of the code, to Jetsons Living’s specification, and got the system up and running. We did not do the architecture and we did not do the design. Both came from Jetsons Living, and every decision about what the platform is and how it is put together stayed with them.

The work took about six months, and it took that long because nothing carried over: version two shares no code with version one, so every part of the platform had to be written again before any of it could go live. It did, in June 2026.

The front end is Next.js. The back end is Jetsons Living’s own, built by their team; we wrote the front end to work with it rather than replacing it.

What version two changed

Setting up a new customer on the platform used to take roughly a full working day of somebody’s time. On version two a customer sets themselves up in about 15 minutes, without anyone at Jetsons Living doing it for them.

Jetsons Living supports their own product, and version two made that far easier to do remotely. Tracking a bug and taking it all the way through triage, fix and review used to be difficult, and a fix typically took multiple days to reach a customer. They now turn one around in a few hours, with the investigation done properly rather than skipped - the point is not that they rush, it is that they can look into a problem carefully and still get the fix out the same day.

Both figures say the same thing. The rewrite did not only make the product faster, it made the company faster at running it.

How it runs now

The system has since moved onto Sylo’s platform, and updates to the Jetsons Management System now go out through it. That is a different arrangement from the one a Sylo project agreement sets out by default, which ends with a handover: the repository, the infrastructure and the runbook go to the customer, and our access ends that day. This project is set up to carry on instead, and the platform is how new work goes live.

The product remains Jetsons Living’s.