Custom Wi-Fi & mesh dashboards, built around your actual faults

Vendor controllers are built around coverage, because coverage is easy to draw and looks reassuring. What they rarely put on one screen is channel utilisation, PoE headroom, noise floor and client counts moving together over time. That combination is what explains a floor that is green everywhere and unusable at eleven in the morning.

No. We read from what you already have and present it properly. Your controller stays exactly where it is, doing its job - we are adding a view, not another system to manage, and nothing we build changes how your wireless runs.

It depends on what your platform exposes and how, which is the first thing we check and the first thing we would tell you if the answer were no. Most business wireless platforms offer an API or an export; some are far more generous than others. We will not promise a build before we have confirmed we can read your data.

It is quoted per site, because a two-access-point office and an eighteen-access-point sales floor across two acres are not the same job. We publish no price for this work - we would rather give you a real number after seeing what you have than a fake one on a web page.

No. Dashboards are built and delivered remotely, so this is a service we provide anywhere - the same way our custom Victron dashboards run for customers well outside the UK. On-site survey work is Dorset and the surrounding counties.

Because replacing the access points is the expensive way to find out what was wrong. A dashboard that shows channel utilisation and PoE headroom over a fortnight will usually tell you whether new hardware would help at all - and quite often the honest answer is that it would not.

Yes. Every 365 member gets the dashboard studio in the portal to arrange and save, and on 365 Business Support the tiles covering the estate we already manage go live on your own account - every computer in the business on one line, Windows versions and pending restarts, backups, antivirus, your visits and reports. Reading your wireless controller, switches or machines is the bespoke build, quoted per site, because it needs someone to check what your platform actually exposes first.

Where the supplier exposes the data, yes - half-hourly usage and tariff information can sit alongside your solar and battery so you can see what you are actually buying and when. Coverage varies a great deal by supplier: some publish a proper API, others publish nothing. We check yours before promising anything.

Yes, and we would usually recommend it. An alert that lands where your team already is gets read; an alert in a fourteenth app does not. We do this on our own systems - every booking and completed job on our internal setup pings Slack.

From a standards-based diagnostics or telematics device, yes - location, mileage, fuel economy, fault codes and battery health. We work from documented interfaces rather than by reverse-engineering a manufacturer's app, because anything built that way breaks the next time they update it.

Yes - live position, the route it took, the miles it covered, and geofences you draw yourself so the dashboard raises an alarm when something leaves an area, or when its signal drops. On a Victron system the GPS can come from the GX itself; on a vehicle it comes from a diagnostics or telematics device. Credit where it is due: Victron's own VRM portal already does geofencing and keeps a position history. What we add is your own screen, several vehicles on one map, and route history that does not expire after six months. It is not a theft tracker, and we will not sell it as one: it is not concealed, it runs off the battery bank it is watching, and no insurer recognises it.

Yes - there is a dashboard studio in the 365 portal, and it is free to join and play with. Drag the tiles where you want them, take off what you do not care about, save the layout to your account and it follows you to any device. Being precise about what is real in it: on a 365 support plan the tiles about the computers we look after read your own account, and every other tile is clearly marked as a sample of what we could connect. Making one of those samples real - your cameras, your solar, your sensors - is still a build we do for you, because it needs someone to check what your equipment actually publishes first.

Those are some of the best uses for it, because they are the buildings you are not standing in. Batteries and bilge on a boat, leisure power and whether it started this morning on a campervan, heating and damp and leaks on a holiday home two hundred miles away.

We tell you before you have spent anything. Some equipment simply does not publish its data, and some budget cloud-only cameras deliberately prevent anyone else reading them. Finding that out afterwards is how these projects go wrong, so we check first.