Custom IoT hardware, built from a controller that already ships

A custom IoT device does not have to start from a blank board. Most products need a proven controller with their own enclosure, their own sensor set and their own name on it. A new board is designed only when the product really cannot be built on the existing one.

What can be customised

The sensor set

Each port is set from the dashboard to the protocol its sensor speaks. Over fifty sensor types are supported today, and a driver for one that is not is added on request.

The enclosure and labelling

Custom enclosures, your part numbers and your labels, so the unit installed at the customer site is recognisably your product.

What the firmware does

How often the device measures and transmits, which outputs switch on which conditions, and behaviour specific to your product. Updates reach units in the field over the air.

How it is powered

Rechargeable battery, solar, or a 6 to 32 V DC supply from the machine or the site. The choice follows where the unit lives.

How it connects

4G-LTE as the default, Wi-Fi where the site network is yours, and an expansion slot that takes external modules such as LoRa, LoRaWAN and GPS.

Three depths of custom

The shallowest one that meets the product is the right one. It is the fastest, and it leaves the least for anyone to maintain.

DepthWhat changesWhen it fits
ConfiguredA standard controller with your sensors and your settingsThe product monitors and switches, and the standard enclosure is acceptable
AdaptedA custom enclosure and labelling, a new sensor driver, firmware behaviour of your ownThe product needs its own identity, or a sensor that is not supported yet
New designA board, an enclosure and firmware designed for the productThe form factor or the function cannot be met by the controller

A new design is an ODM engagement, described on the ODM page.

What stays the same at every depth

The cloud

The same multi-tenant cloud, with accounts for you and your customers and a REST API, whatever the hardware looks like.

The updates

Firmware reaches units in the field over the air, so a fix or a feature is not a recall.

The brand

Your name on the dashboard and on the apps in the stores, as on the hardware.

What we say before you commit

Certification is scoped, not assumed

Certification for a target market is part of the work and depends on the market and the installation. Tell us both at the start.

It is not a safety controller

The controller measures, reports and switches. It has no safety rating and no deterministic scan cycle, and it is not sold as a replacement for a PLC.

Related

Frequently asked questions

Can you add a sensor you do not support yet?

Yes. If it speaks one of the supported protocols, we add a driver for it. Send the model and its documentation.

Can the hardware carry our brand?

Yes. Custom enclosures, your part numbers and your labelling are part of the offer.

Do you handle certification?

Certification for a target market is scoped as part of the work and never assumed. It depends on the market and on where the unit is installed, so we ask for both at the start.

How do updates reach devices already in the field?

Over the air, by cellular. Where there is no network at all, the unit raises its own Wi-Fi access point and takes the update from a phone or laptop beside it.

When do we need a new board?

When the size, the shape or the function of the product cannot be met by the controller. That is less often than it first seems, and it is worth checking before paying for a design.

Tell us what the device has to do

What it measures, what it switches, where it is installed and what it has to look like. We come back with the shallowest route that meets it.

Talk to us →