Your product has a board, a cloud and an app. We build all three.

NE Solutions is a product engineering firm for companies that put hardware into the field. One team owns the whole signal path — from the sensor on the board to the screen the customer taps — so nothing falls between vendors.

Start a project See what we have built

The stack we ownDevice → Interface

Interface

Consoles for operators, commissioning tools for installers, apps for end customers.

AngularReactReact NativeOffline-first

Platform

Device registry, telemetry ingest, OTA campaigns, tenancy, reporting and APIs.

NestJSGoMQTTPostgreSQLAWS

Link

Getting data off the device reliably, over whatever the site already runs.

BLEWi-FiLoRaModbusCANBACnet

Device

Boards, firmware and embedded Linux built to survive a decade in the field.

STM32ESP32i.MXYoctoZephyrFreeRTOS

Why clients call us

Most connected-product programmes do not fail on technology. They fail in the gaps.

Hardware, cloud and app are usually bought from three different suppliers. Each one delivers what was in its own contract, and the integration is left to whoever is unlucky. We take that risk off the table by holding all three.

How we structure an engagement

“The boards are ready, the cloud is not.”

Production is booked and the platform that is supposed to receive the devices is still a prototype. We sequence platform work against your hardware milestones, not against ours.

“The person who wrote our firmware has left.”

Undocumented code, no build reproducibility, no update path. We take custody of legacy firmware, get it building from a clean checkout, and add a safe way to update units already in the field.

“Nobody owns the integration.”

Three vendors, three sets of assumptions about protocols, identity and error handling. One engineering team, one architecture and one point of accountability removes that whole category of problem.

Capabilities

Three disciplines, staffed in-house

Every engagement draws on some combination of these. You are not handed a fixed package — you get the mix your product actually needs.

01 · Hardware and firmware

Embedded & IoT engineering

Schematic and PCB design, firmware on bare metal or RTOS, embedded Linux images you can reproduce years later, and update mechanisms that will not brick a unit on a bad connection.

Embedded & IoT

Silicon: STM32, ESP32, NXP i.MX, Nordic nRF, TI
Operating systems: Embedded Linux, Yocto, Torizon, Zephyr, FreeRTOS
Wireless: BLE, Wi‑Fi, LoRa/LoRaWAN, Zigbee, cellular
Wired & fieldbus: CAN/CANopen, Modbus, Ethernet, BACnet, DALI, KNX
Security: Secure boot, signed images, ATECC/TPM key storage
Field updates: A/B partitions, delta OTA, rollback and staged rollout

02 · The system behind the fleet

Device platforms & cloud

The part that turns a shipment of units into a manageable fleet: identity, provisioning, telemetry, update campaigns, tenancy for your distributors, and APIs your customers can build against.

Device platforms

Backend: NestJS / TypeScript, Go, Python
Device transport: MQTT, AMQP, OPC‑UA, HTTPS, WebSocket
Data: PostgreSQL, MySQL, time‑series stores, object storage
Cloud: AWS, Azure, GCP, or your own hardware
Delivery: Docker, CI/CD, infrastructure as code
Operations: Metrics, tracing, alerting, on‑call runbooks

03 · What people actually touch

Web & mobile applications

Operator consoles, installer commissioning tools that work in a basement with no signal, dealer portals and customer apps — designed around the job someone is doing, not around your database schema.

Web & mobile apps

Web: Angular, React, TypeScript, design systems
Mobile: React Native, Expo, native modules where needed
On-site work: Offline‑first sync, BLE commissioning, QR provisioning
Access control: Roles, multi‑tenant scoping, audit trails
Design: UX research, interface design, accessibility
Quality: Automated tests, device labs, release checklists

Engagement

Four ways to work with us

Pick the one that matches where your product is. Most clients start with one and move between them as the programme changes.

Build the product

Concept to production. We own scope, architecture and delivery, and hand over a product plus everything needed to keep making it.

Most common

Dedicated team

A named team working only on your roadmap, in your tools and your sprint rhythm, scaling up and down as the programme demands.

Rescue and maintain

Inherit a codebase nobody can build any more. We stabilise it, document it, and put it back under version control and CI.

Add one discipline

You have firmware but no cloud, or an app but no embedded team. We fill the missing layer and integrate with the people you already have.

Rates, process and what we commit to

Selected work

Recent engagements

Client names are withheld under confidentiality agreements. We are happy to talk through any of these in detail on a call.

Building automation

Controller platform for motorised shading

The problem

A controller line with ageing firmware, no remote update path, and commissioning that required a laptop and a site visit for every change.

What we did

Rebuilt the controller software on embedded Linux with signed A/B updates, added per‑unit hardware‑backed identity, and shipped an installer app that commissions over Bluetooth with no internet on site.

Embedded LinuxYoctoBLESecure elementAngular

Industrial robotics

Fleet control for autonomous mobile robots

The problem

Vehicles from more than one supplier, each with its own control interface, and no single view of where a fleet was or how much charge it had left.

What we did

Built a control and telemetry layer over ROS 2 and CANopen, with battery and charging management, plus a dispatcher console that treats mixed fleets as one.

ROS 2Nav2CANopenGoReact

Commerce operations

Multi-marketplace seller platform

The problem

Orders, stock and returns spread across several marketplaces, reconciled by hand in spreadsheets, with margins only visible weeks later.

What we did

One operations platform that syncs listings and inventory across channels, reconciles settlements automatically, and reports true per‑order margin as it happens.

NestJSMySQLQueue workersReact

More engagements

Terms you can hold us to

The commercial answers, before you ask

Procurement asks the same questions on every engagement. Here are our standing answers — they go into the contract, not just the proposal.

Read the detail

You own the intellectual property, including firmware, schematics and cloud code
Source lives in your repository from the first commit, not at handover
NDA signed before the first technical conversation
Fixed scope or time and materials — your choice, stated up front

Every release ships with test evidence and a build you can reproduce
Security review on identity, key storage, transport and update paths
Named engineers, no silent substitutions mid‑project
Support and maintenance terms agreed before go‑live, not after

Industries

Where our engineering already has scar tissue

Domain knowledge shortens every programme. These are the sectors where we already know the protocols, the certification path and the failure modes.

Building automation

Shading, lighting, HVAC integration, BACnet and KNX estates, installer tooling.

Industrial & robotics

Factory connectivity, Industry 4.0 data paths, AMR and AGV control, OPC‑UA.

Energy & metering

Metering, submetering, load monitoring and long‑life low‑power devices.

Healthcare devices

Connected instruments, data capture, traceability and documented development.

Consumer products

Connected appliances, provisioning that ordinary people can complete unaided.

Retail & commerce

Marketplace operations, inventory systems, in‑store devices and back office.

What we build in each sector

Tell us what you are trying to ship.

Send a paragraph about the product and where it is stuck. You will get an engineer's reply, not a sales sequence.

Start a project Browse capabilities