Engineering services

The engineering behind the platforms, available on its own.

We build device software, wireless networks and delivery pipelines for our own products. Those same teams work directly for operators and manufacturers who need the capability rather than the platform.

Why take engineering services from a product company

Consultancies that only advise drift away from what actually ships. Vendors that only sell products have an answer before they hear the question. We do both, which means the advice is grounded in code we maintain and the products are shaped by networks we have had to fix.

What that means for you

  • Protocol advice from the team that implements both ends of it
  • Wireless design from people who operate wireless at scale
  • Vendor-neutral recommendations, including about our own platforms
  • Work handed over documented, not held behind a retainer

How engagements usually start

01

A scoping conversation

Free, technical, and with an engineer rather than an account manager. We will tell you if it is not something we should take on.

02

A written proposal

Scope, assumptions, what is explicitly out, and where the risk sits. Fixed price where the scope allows it, time and materials where it honestly does not.

03

Delivery and handover

Working software or a written report, plus the documentation your team needs to carry it on without us.

Tell us what you are trying to build

A short technical conversation costs nothing and usually clarifies the problem. If we are the wrong people for it, we will say so and point you at who is not.