The engineering help before the hardware arrives
Most of what goes wrong with a mesh deployment is decided before anything is mounted — a repeater in the wrong place, a protocol that does not fit the problem, or a team that inherited a network nobody explained to them. We work at that end.
What we help with
Software, full-stack or embedded
We write cloud-based software and embedded firmware for mesh systems, and we are comfortable at either end of that — the radio and the console are both ours to build.
- Embedded and firmware work
- Backend services and APIs
- Web consoles and dashboards
- Integration with what you already run
Hardware development
Custom hardware for mesh-based problems: sensor nodes, gateways, enclosures and power. Built around what has to survive the site, not around a reference design.
- Node and gateway design
- Power and solar budgeting
- Enclosure and environmental
- Bring-up and field testing
Site planning
Where the repeaters go, and why. Terrain, obstruction, height, mounting and power, worked through before you commit to a bill of materials.
- Terrain and path analysis
- Mount and power siting
- Bill of materials
- Phasing for budget
Coverage mapping
For a network you have not built yet, or for repeaters you already run and are not sure about. We map what you are actually getting against what you were promised.
- Predicted link budgets
- Survey of existing repeaters
- Gap and redundancy analysis
- A written map you keep
Educational sessions
01
What mesh is, and what it is not
The honest version. What LoRa and MeshCore actually do, the range you can expect on your terrain rather than in a brochure, and the problems mesh is the wrong tool for.02
For the team that will run it
How to add a node, read the health of the network, and tell a dead radio from a bad path. Aimed at whoever picks up the phone when something stops working.03
For the people who sign off on it
Where the risk actually sits, what the failure modes are, what it costs to run, and what happens if we disappear. Sessions for councils, boards and committees.
We will tell you when the answer is no
Mesh is not right for everything, and a consultancy that never says so is selling hardware rather than advice. If your problem is better solved by a length of fibre, an existing cellular plan or a single point-to-point link, we would rather tell you that at the first meeting than at the third invoice.
The coverage model is yours either way. If it shows that mesh does not fit, you still have the map.
- A written recommendation, including when it recommends against us
- The coverage model is yours, whoever builds the network
- No hardware markup riding on the advice
- Plain language, and a session to walk your team through it
Start with the map, not the hardware
Tell us the ground, the distances and what has to cross them. A first conversation costs nothing and usually saves a repeater.