Embedded and IoT development, from firmware to dashboard
Gjethe develops embedded and IoT systems: firmware for microcontrollers such as ESP32, STM32 and Nordic nRF, sensor and peripheral integration, Bluetooth, Wi-Fi, LoRaWAN and cellular connectivity, secure over-the-air updates, IoT cloud back-ends and dashboards, and the companion mobile apps that talk to the device. Hardware certification and electrical design sign-off stay with qualified partners.
- Free first consultation
- Written quote for your project
- Flexible payment milestones
At a glance
- Microcontrollers
- ESP32, STM32, nRF52/nRF53, RP2040
- Connectivity
- BLE, Wi-Fi, LoRaWAN, cellular, MQTT
- Cloud
- AWS IoT, Azure IoT, self-hosted MQTT
- Apps
- Mobile companion apps and web dashboards
Definition
What is embedded & iot development?
Embedded development is writing software that runs directly on devices with limited resources. IoT (Internet of Things) development connects those devices to networks, clouds and apps so they can be monitored and controlled remotely.
A connected product has three parts that must work together: the device firmware, the cloud that collects data and sends commands, and the app or dashboard people use. Many projects stall because each part is built by a different team with different assumptions. Building them together, with clear protocols between them, makes devices more reliable and much easier to update after they ship.
Who is it for?
Hardware startups
Firmware, cloud and app for a first connected product.
Industrial companies
Sensors, monitoring and retrofits for machines and facilities.
Smart building and energy projects
Metering, environmental sensing and control.
Logistics and fleet
Tracking and condition monitoring for assets in transit.
What's included, and what you keep
What's included
- Architecture of device, connectivity and cloud
- Firmware development in C, C++ or Rust
- RTOS and bare-metal development
- Sensor and peripheral drivers
- Bluetooth Low Energy and Wi-Fi provisioning
- MQTT and other IoT protocols
- Secure boot and over-the-air updates
- Power optimisation for battery devices
- IoT cloud back-end and device management
- Dashboards and companion mobile apps
- Test rigs and automated firmware tests
What you receive
Handed over at the end. Yours to keep.
- Firmware source code and build instructions
- Cloud infrastructure as code
- Dashboards and app source code
- Protocol and API documentation
- Test reports and an update procedure
Firmware that can be updated safely
Devices in the field will need updates: bug fixes, security patches, new features. Over-the-air updates must be secure and recoverable, so a failed update doesn't leave a device unusable. We design dual-image updates with signature checks and rollback, and test them with interrupted downloads and power loss.
Choosing connectivity
| Option | Range and power | Good for |
|---|---|---|
| Bluetooth Low Energy | Short range, very low power | Wearables, sensors paired with a phone |
| Wi-Fi | Building range, higher power | Mains-powered devices at home or in offices |
| LoRaWAN | Long range, very low power, small data | Remote sensors, agriculture, utilities |
| Cellular (LTE-M, NB-IoT) | Wide coverage, moderate power | Trackers and devices without local networks |
Battery life is designed, not hoped for
For battery-powered devices, firmware decides how long the battery lasts: how often the device wakes, how long the radio is on, how data is batched. We measure power consumption on real hardware, model battery life for realistic usage and optimise until the target is met.
Security from the device up
Connected devices are attractive targets. We use unique device credentials, encrypted connections, signed firmware, minimal open interfaces and least-privilege cloud permissions. For products sold in the EU, cybersecurity requirements for connected products are tightening, and designing security in from the start makes compliance far easier.
What stays with specialists
Our focus is software: firmware, connectivity, cloud and apps. Electrical design, PCB layout sign-off, radio certification and product safety certification require specialist engineers and accredited labs. We work alongside your hardware partner or help you find one, and prepare the software documentation those processes need.
What helps us start
- What the device must measure or control
- Existing hardware, schematics or development boards
- Power source and battery-life target
- Where devices will be installed and how they connect
- Who will use the data, and how
- Expected number of devices
Dashboards and alerts people act on
Data from devices is only useful if someone acts on it. We design dashboards around decisions: which machine needs attention, which sensor is out of range, which device has gone silent. Alerts go to the right person by email, SMS or messaging app, with enough context to act, and are tuned so they don't become noise.
From prototype to production
Moving from a handful of prototypes to hundreds of devices raises new questions: how each device gets its unique credentials, how firmware is flashed and tested on the production line, and how devices are registered in the cloud. We build provisioning and test tools so manufacturing can follow a repeatable procedure.
How embedded & iot development works, step by step
Every step has a clear output you can review. Timing is agreed in your quote.
- 1
Architecture
Device, connectivity, cloud and app designed together.
- 2
Proof of concept
Development boards and a minimal end-to-end data path.
- 3
Firmware
Drivers, logic, connectivity and updates on target hardware.
- 4
Cloud and apps
Device management, data storage, dashboards and app.
- 5
Testing
Automated tests, field trials, power and update testing.
- 6
Production support
Provisioning, manufacturing test tools and documentation.
Tools, and what shapes your quote
Pricing is based on your project and agreed in your quote. These are the things that move it.
| Factor | Why it matters |
|---|---|
| Hardware maturity | Working with development boards first is different from finished hardware. |
| Connectivity | Each radio technology adds firmware and testing. |
| Power constraints | Battery devices need careful optimisation. |
| Cloud scope | Device management, data storage and dashboards add development. |
| Companion app | A mobile app is a project of its own. |
| Fleet size | Larger fleets need provisioning and monitoring tooling. |
| Area | Tools |
|---|---|
| Firmware | C and C++, Rust, ESP-IDF, Zephyr RTOS, FreeRTOS, STM32Cube |
| Connectivity | MQTT, BLE GATT, LoRaWAN, CoAP |
| Cloud | AWS IoT Core, Azure IoT Hub, Mosquitto, InfluxDB, TimescaleDB |
| Apps and dashboards | React Native, Grafana, Next.js |
Common mistakes to avoid
What we see go wrong most often, and how a good project avoids it.
No plan for updates
Devices you can't update can't be fixed. Build secure OTA updates from the start.
Shared credentials
One password for every device means one leak exposes them all.
Testing only on the bench
Real installations have weak signals, interference and power glitches. Run field trials.
Building cloud and firmware separately
Agree protocols and data formats early so the parts fit.
Frequently asked questions
Which microcontrollers do you work with?
ESP32, STM32, Nordic nRF52 and nRF53, RP2040 and similar families, chosen to suit the product.
Do you design circuit boards?
Our focus is software. We work with your hardware engineers or a partner for electrical design and PCB layout.
Can you handle certification?
Radio and safety certification are done by accredited labs. We prepare the software and documentation those processes require.
Can you build the mobile app for our device?
Yes. We build companion apps in React Native or native code, with Bluetooth or cloud communication.
Which cloud platforms do you use?
AWS IoT Core, Azure IoT Hub or self-hosted MQTT brokers, depending on scale and preference.
Can you add connectivity to existing machines?
Often, yes, with retrofit sensors or gateways reading existing interfaces such as Modbus.
Do you write firmware in Rust?
Yes, where the platform supports it well, as well as C and C++.
Who owns the firmware?
You do, once the project is paid, along with the cloud and app code.
How is IoT development priced?
It is quoted on hardware maturity, connectivity, power requirements, cloud scope and whether an app is included.
Can you take over firmware someone else wrote?
Yes. We review the code, document how it works, fix issues and set up a build and test process before adding features.
Do you work with Raspberry Pi or Linux devices?
Yes, for gateways and devices that need more computing power, alongside microcontroller projects.
How do you test firmware?
With unit tests where possible, hardware-in-the-loop test rigs for key functions, and field trials on real installations.
Can devices work when the connection drops?
Yes. We design firmware to store data locally and send it when the connection returns, so nothing is lost during outages.
Related services
Cloud Deployment
Vercel, AWS, Azure and Google Cloud set up properly.
Dashboard Development
Live dashboards for operations, sales and finance.
Mobile App Development
iOS and Android apps, from design to store launch.
Data Engineering
Pipelines and warehouses that keep your data reliable.
CAD Design & Drafting
2D drawings and 3D CAD models for making things.
Embedded & IoT Development by industry
Connect your product.
Tell us what you need. You get an honest assessment, a clear plan and a written quote. The first consultation is always free.
- What happens next
- 1You tell us what you need
- 2We aim to reply within 24 hours with questions
- 3You get a written quote for your project