iGates is a Tel Aviv–based software house specializing in end-to-end IoT systems — from the device in the field, through the communication layer, all the way to the cloud platform and the management dashboard. We take IoT projects from initial spec to shipped product, including embedded firmware, industrial protocols (MQTT, OPC-UA, Modbus), device security, cloud, and fleet management. Notable clients: Siemens (Industrial IoT), Nayax (global-scale vending IoT), AngelSense (wearable IoT), and Hamagen (national-scale BLE proximity IoT).
IoT (Internet of Things) development is the discipline that connects physical devices — sensors, cameras, controllers, terminals, consumer-grade smart products — to the internet, and turns the data they produce into business value.
A typical IoT system has four layers: (1) the device itself (hardware + embedded firmware), (2) a communication layer (wireless or wired — BLE, Wi-Fi, LoRa, LTE-M, NB-IoT, or industrial protocols like OPC-UA and Modbus), (3) a cloud backend (telemetry ingestion, processing, storage, security), and (4) an application layer — dashboards, fleet management, alerts, analytics, and AI integration.
iGates works across all four layers within a single project. That's the difference between a full-stack IoT software house and a point-vendor that builds only the dashboard or only the firmware.
Planning an IoT product — an industrial device, a wearable, a connected product, or a fleet-management platform? We take projects from initial spec all the way through long-term maintenance, across every layer. Reach out for a no-commitment technical review.
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.
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.
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.
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.
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.
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.
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.
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.
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.
