IoT Development — Edge to Cloud

Overview

Enterprise software development at iGates is tailored for organizations requiring a premium technology partner to build robust B2B systems, enterprise applications, secure integrations, and deployment pipelines engineered for long-term production stability.

We bring proven delivery experience with global enterprises such as Siemens, Microsoft, and AT&T - placing uncompromising focus on clean software architecture, rigorous security compliance, high performance, and future-proof maintainability.

Our end-to-end delivery lifecycle encompasses comprehensive requirements discovery, technical architecture planning, full-stack backend and web engineering, legacy system integration, automated testing, continuous monitoring, and a structured handoff process that empowers internal engineering teams to scale the product with confidence.

IoT Development

End-to-end engineering capability

End-to-end IoT development: device firmware, connectivity (MQTT, OPC-UA, BLE), cloud, fleet management, and dashboards. iGates has built IoT for Siemens, Nayax, AngelSense, and Hamagen — senior team in Tel Aviv.

This page content is sourced from the approved handoff and can be edited later through the CMS.

Frequently asked questions

What is the difference between IoT development and embedded development?

Embedded development focuses on the device itself: firmware, drivers, kernel, and BSP. IoT development is broader and adds connectivity, cloud, dashboards, and fleet management. Almost every IoT project requires embedded work at the edge, but not every embedded project is IoT. At iGates both disciplines sit in the same house, so we deliver end-to-end projects instead of relying on integration between two vendors.

Which IoT communication protocols do you support?

Short-range wireless: BLE, Zigbee, Thread, NFC, Wi-Fi. Long-range or low-power wireless: LoRaWAN, NB-IoT, LTE-M, Sigfox. Industrial: OPC-UA, Modbus TCP/RTU, CAN, EtherCAT. Application-layer: MQTT, CoAP, AMQP, REST, WebSocket. Protocol choice is made during specification based on range, battery, cost, and regulatory requirements.

Do you also build dashboards and fleet management?

Yes. Operational dashboards, fleet management, OTA updates, alerts, reports, and multi-tenancy are standard parts of a complete IoT project. We use React and Next.js for management UIs, and Grafana for operations dashboards that need many fast panels. For Nayax we built management at the scale of hundreds of thousands of devices.

How do you connect to industrial sensors and controllers?

In industry, most equipment communicates through OPC-UA, Modbus TCP or RTU, Profinet, EtherCAT, or CAN. We build industrial gateways that translate equipment-level protocols into modern application protocols such as MQTT and REST, and provide store-and-forward behavior for unstable connectivity. For Siemens we built such a layer to connect TEAM CENTER PLM to controllers at the process edge.

How do you handle IoT security?

In several layers: secure boot and signed firmware on the device; X.509 device identity from factory provisioning; MQTT-over-TLS with mutual authentication; hardware-backed keystores such as TPM or ATECC where supported; signed OTA updates with rollback; automatic certificate rotation in the cloud; and attack-surface reduction on custom Linux distributions. In medical or payment projects we also go through external penetration testing.

Which IoT industries do you work in?

Industrial IoT and PLM with Siemens; unattended retail and vending with Nayax; wearables and health with AngelSense; public health and proximity with Hamagen; payments with Paybox and Verifone-adjacent experience. Thirty years in telecom and industry give our team depth in protocols, compliance, and operating connected products at scale.

How long does a complete IoT product take?

A POC on existing hardware usually takes 8-12 weeks. A full MVP including firmware, connectivity, cloud, and an initial dashboard takes 6-9 months. A production-grade product with fleet management, OTA, and CE/FCC compliance takes 9-15 months. Medical or payment compliance can add another 3-6 months. We always start with a 3-4 week specification phase that summarizes timeline and cost.

Do you support AWS, Azure, and Google IoT clouds?

Yes. AWS IoT Core and Greengrass are our standard for global projects. Azure IoT Hub and IoT Edge are used for enterprise projects already in the Microsoft ecosystem. Google Cloud IoT is now mostly migration-path work after Google removed the service from GA. We also support on-prem or private cloud where clients require it, such as defense or financial industries.

See more: IoT Development — Edge to Cloud