The RF and embedded engineering behind every deployment

Most of the market integrates other people's radios. We design our own. Our RF engineers have spent careers — in several cases more than four decades — at the sharp end of radio, on work spanning government-grade systems through to some of the most demanding RF problems in the UK. That depth is not a marketing line; it is the reason a signal gets out of a location everyone else said was impossible. Several of these engineers are shareholders in the business, so the people designing your system are personally invested in it working in the field, for years, not just passing a bench test.

We write the firmware. We design the hardware. We design the radio. We build the intellectual property from scratch, in-house — nothing critical is sub-contracted, bought in or licensed from a third party. For a client that means no hidden dependencies and no surprises: one team accountable for the whole signal chain, from the physics of the radio link to the firmware that runs on the device. It also means that when a deployment needs something that does not exist yet, we can build it — rather than wait for a vendor to decide whether it is on their roadmap.

Before a board is ever laid out, our engineers model the radio environment the device will actually live in. That means real RF analysis: link budgets, path loss, the effect of enclosures, structures, soil and water on the signal, the local noise floor and interference, and the regulatory duty-cycle limits that govern how often a device may transmit. Only then do they select the right approach from across the sub-GHz toolkit — the licence-free 433 and 868 MHz bands, narrowband against spread-spectrum techniques and their spreading factors — matched to the range, penetration, power budget and regulation of that specific site. There is no single default and no favourite band. The physics of each deployment decides, and the analysis is done up front so the result is right the first time.

The embedded team writes bespoke firmware for each platform, engineered around multi-year battery life and absolute reliability in remote, harsh and hard-to-reach places — the basements, chambers, plant rooms and exposed structures where IoT actually has to work. Custom hardware is designed to match the job rather than forced to fit an off-the-shelf module. Every design is built for the long, unattended deployments our clients depend on: years in the field, no van visits, no surprises.

The RF and embedded team works hand in hand with our platform engineers, not in a silo. They scope each project from first principles — what has to be measured, where, in what conditions, and what good looks like for the client — then design the bespoke firmware and embedded hardware to deliver it. Survey, scope, design, build, test, deploy, support: one team carries it the whole way, which is why the systems behave in the field the way they did on the bench.

This is not a lab capability. Our engineers have delivered at enterprise scale and worked on some of the largest and most challenging RF projects in the UK, from government-grade systems through to estate-wide enterprise rollouts. The same team and the same rigour are behind a single difficult sensor and a national deployment.