Skip to content
BigTree108

IoT development services

IoT development services from the device to the dashboard: connectivity, device provisioning, cloud platforms on Azure or AWS, fleet updates, edge gateways, industrial IoT, asset tracking, EV charging and energy platforms, web portals and companion apps for smart home and building, manufacturing, energy and utilities, logistics, agriculture and healthcare, with dedicated IoT developers for your team or projects delivered end to end.

IoT systems we build

  • Device connectivity

    Bluetooth Low Energy, Wi-Fi, Thread and Matter in the home, LoRaWAN on ChirpStack or The Things Stack across fields and buildings, and LTE-M or NB-IoT with eSIM for trackers and meters, chosen on range, battery life and running cost per device.

  • Provisioning and device identity

    A unique X.509 certificate per device, kept in a secure element where the hardware has one, issued on the production line and enrolled through the Azure IoT Hub Device Provisioning Service or AWS IoT Core, with no shared password anywhere.

  • Cloud ingestion and storage

    MQTT into Azure IoT Hub, the Event Grid MQTT broker, AWS IoT Core or a self-hosted EMQX or HiveMQ cluster, processed by functions or containers and stored as time series in Azure Data Explorer or PostgreSQL with TimescaleDB, all deployed with Terraform.

  • Fleet management and updates

    Device twins or shadows for configuration, firmware rolled out to a small share of the fleet first, and health telemetry that pauses a rollout when crash or reconnect rates rise.

  • Dashboards and companion apps

    Web portals in Angular or React, ThingsBoard where an off-the-shelf platform fits, and mobile apps on iOS, .NET MAUI or React Native for pairing, setup and alerts, built by the same company as the device side.

  • Industrial IoT

    Machine and sensor data collected from PLCs over OPC UA and MQTT Sparkplug B into a unified namespace, condition monitoring on vibration, temperature and power draw, and links to your MES, maintenance and ERP systems.

  • Gateways and edge computing

    Edge gateways on embedded Linux that read Modbus, BACnet, M-Bus or DLMS devices, run containers and local rules on Azure IoT Edge or AWS IoT Greengrass, buffer through network outages and forward only what the cloud needs.

  • Asset tracking and telematics

    GNSS and cellular trackers for vehicles, containers and pallets, Bluetooth and ultra-wideband tags for indoor location, vehicle data from OBD-II, J1939 and CAN, and the geofences, trips and alerts built on them.

  • EV charging and energy platforms

    Charge point management on OCPP 1.6, 2.0.1 and 2.1, Plug & Charge with ISO 15118, roaming over OCPI, and monitoring and control of solar, battery storage and smart meters, with demand response over OpenADR.

Hire IoT developers

  • Dedicated IoT developers

    IoT developers who join your team full time, work in your tools and process, and report to your lead. You interview them; we carry the Ukrainian contract, payroll, invoicing and leave.

  • IoT development projects

    A defined piece of IoT development with a scope, a fixed plan and a named lead on our side who owns the result and reports progress in your channels.

  • Ongoing IoT development

    IoT development as a continuing service: the same people every month, a backlog you prioritise, and hours you can see in our portal and on the invoice.

The dedicated team page explains how specialists join your team, and the outsourcing page covers project delivery, take-overs and how we charge.

Who works on your IoT development

  • IoT developers

    Connectivity, provisioning and fleet updates

  • Firmware engineers

    The code on the device

  • .NET, Python and Java engineers

    Ingestion, APIs and data pipelines on Azure or AWS

  • Front-end and mobile engineers

    Web dashboards and companion apps

  • QA engineers

    End-to-end tests from device to dashboard

How we build IoT systems

Every device is treated as an untrusted network client: its own identity, no default or shared passwords, encrypted connections, access to exactly the topics it needs, and a published way to report vulnerabilities. That is what ETSI EN 303 645, the UK product security regime and the cybersecurity requirements of the EU Radio Equipment Directive ask of connected products, and the EU Cyber Resilience Act adds a software bill of materials and vulnerability handling for the whole support period, which we generate from the build.

The cloud side follows the rules we run our own systems by: infrastructure in Terraform, deployments from GitHub Actions with federated credentials, secrets and signing keys in a vault, and deny-by-default network rules, whether it runs on Azure, on AWS or on servers you operate yourself.

Other embedded and hardware services

Embedded and hardware overview

Questions about IoT development

Which connectivity should our device use?

It follows from where the device lives, how often it reports and what powers it. Bluetooth Low Energy when a phone is nearby; Wi-Fi, or Thread with Matter, for mains-powered home and building devices; LoRaWAN for small readings from fields or basements over years on one battery; LTE-M or NB-IoT when the device moves or there is no local network. We compare the running cost per device per year before the radio is chosen.

Can you build the whole system, from device to app?

Yes, as one team: firmware, cloud, web portal and mobile app built against one set of message contracts, so a change on the device does not break the dashboard. When part of the system already exists, we build the rest against what is there.

Which IoT clouds and platforms do you work with?

Azure IoT Hub and the Event Grid MQTT broker, AWS IoT Core, self-hosted brokers such as EMQX, HiveMQ or Mosquitto, and platforms such as ThingsBoard, built on the cloud your estate already uses. The device side stays portable: MQTT over TLS with X.509 identities works with all of them, so the cloud can change without rewriting the firmware.

Which industries do your IoT developers work in?

Smart home and building, in thermostats, locks, lighting and building management; manufacturing, in machine monitoring and predictive maintenance; energy and utilities, in smart meters, solar and battery systems and EV charging networks; logistics, in fleet, container and cold-chain tracking; agriculture, in field sensors and greenhouse control; healthcare, in remote patient monitoring and connected medical devices; and security, in alarm and access control systems linked to monitoring centres.

How quickly can IoT developers start?

When the right IoT developer is available, the start is gated only by your interview and the NDA and IP assignment. Otherwise we run a search, which typically produces candidate profiles within two to three weeks, and nobody starts until you have said yes.

How do we hire IoT developers through BigTree108?

Tell us the work, the seniority and the hours you need. We propose one or two people with their profiles, you interview them the way you would interview your own hire, and you sign one agreement with BIG TREE 108 LLC and receive one invoice a month.

Who owns the work they produce?

You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.

Building a connected product?

Tell us what the device measures or controls, where it lives and how many there will be. You get an answer within one business day: a plan for the system, candidate profiles, or a recommendation on connectivity.