Operating temperature
-40°C to +70°C
Connect machine telemetry to your cloud without locking your architecture
A Melqart-shipped owa gateway combines Owasys hardware with integration, OTA delivery, and structured handover, so your team retains control of code, data, and operations.
owa units variants
Navigate the owa family
Select a gateway form factor, compare capabilities, or add factory-aligned accessories.
Choose your gateway
Owasys owa3x · owa4x · owa5x
Three form factors, one unified platform. Select the gateway that matches your deployment.
| Feature | |||
|---|---|---|---|
| Processor | ARM Cortex A7 @ 792MHz | ARM Cortex A8 @ 800MHz | Quad A53 @ 1.6GHz (optional NPU/GPU) |
| RAM / Storage | 512 MB / 512 MB NAND | 512 MB / 1 GB NAND (up to 2 GB) | 2 GB LPDDR4 / 8 GB eMMC (up to 32 GB) |
| Cellular | LTE Cat 1 bis | LTE Cat 4 (IP 67) / Cat 1 (IP 40) | LTE Cat 4 |
| CAN Interfaces | 2x CAN (344A variant only) | Up to 4x CAN (2x CAN 2.0B, 2x CAN FD) | Up to 4x CAN-FD |
| Power | 9-48V DC input | 9-36V DC (IP 67) / 9-48V DC (IP 40) | 9-36V DC input |
| Ingress Protection | IP40 | IP67 / IP40 | IP67/IP6K9K |
| Edge Apps | Embedded Linux (Yocto) | Debian Linux (C/C++, Python, Java, Lua) | Debian/Yocto Linux (container support) |
| Best For | Infrastructure & vehicle telemetry | Mixed fleets, harsh environments, vehicle connectivity | Edge AI, OEM projects, critical infrastructure |
Software layer
Tailored embedded Linux: Debian and Yocto integration
We deliver more than hardware. We build the operating system beneath it: hardened Debian and Yocto images tuned to your application, so your team reaches production faster.
Custom board support packages
Hardened Yocto layers and Debian images tuned for ultra-fast boot and a minimal memory footprint, built reproducibly for your hardware variant.
Language ecosystems at the edge
Native support for C, C++, Python, Go, and Java applications running directly on the gateway, with the cross-compilation toolchains set up for your team.
Cybersecurity and trust
Hardware-rooted security with TPM 2.0 and secure boot for verified images and signed, controlled OTA deployment.
Field interfaces
CAN-FD / CAN 2.0B
RS485 / RS232
Ethernet
Analog and digital I/O
Field wiring
Owasys owa gateway
Debian or Yocto Linux
Your edge applications, J1939 decoding, store-and-forward buffering
LTE
Cloud and operations
Your cloud platform
owadm (optional) or your OTA
Optional Owasys platform for OTA and device health
owadm device management
owadm is an optional device management platform from Owasys for OTA updates and device health on OWA gateways. It is not part of Melqart's offering. For European customers, owadm helps contribute to a CRA-ready ecosystem. You can also use your own OTA platform, freely integrated with Owasys gateways.
ThingsBoard
Open-source IoT Platform
Optional, not mandatory
owadm provides remote monitoring, OTA updates, and device health management for deployed Owasys gateways. Choose it when it fits your fleet model, or integrate any OTA and device management stack you already run.
CRA-ready for Europe
For European customers, owadm contributes to a CRA-ready ecosystem around Owasys gateways. It remains optional: Melqart integrates Owasys hardware with the update and health tooling you choose, including your own OTA platform.
50K+ devices
120 countries
Keep devices current
Deploy scheduled delta updates for firmware, APIs, and your own software.
Accelerate network expansion
Add new devices, configure settings, and prepare deployments with a controlled onboarding workflow.
Strengthen network security
Use advanced management features to help safeguard your device network.
Reduce unnecessary site visits
Review the status of every gateway from a central workspace.
Support proactive monitoring
Receive real-time notifications for timely operational response.
Industrial fieldbus and telematics interfaces
From field wiring to cloud ingestion, custom Debian and Yocto software converts Modbus RTU over RS485 to MQTT for direct ingestion into AWS IoT Core, and bridges J1939 over CAN-FD into your data pipeline.
CAN and vehicle bus
- CAN-FD / CAN 2.0B
- Up to 4 channels depending on model, with high-throughput CAN-FD on owa5x.
- SAE J1939
- Full J1939 stack for off-highway and commercial vehicle telematics, decoded at the edge.
- OBD-II / ISO-TP
- Transport-layer support for diagnostic and proprietary PGN messaging.
Serial and wired
- RS485 / Modbus RTU
- Isolated RS485 with a Modbus RTU master, mapped to MQTT topics for direct cloud ingestion.
- RS232
- Legacy serial for meters, controllers, and industrial peripherals.
- Ethernet
- 10/100 Ethernet for Modbus TCP, local networks, and wired backhaul.
- 1-Wire
- Digital temperature and ID sensors over long cable runs.
Analog and digital I/O
- Analog inputs
- Voltage and current inputs, including 4-20 mA loops for industrial sensors.
- Digital I/O
- Isolated digital inputs and outputs for ignition sensing, alarms, and actuation.
- Power and ignition
- Wide-range vehicle supply with ignition-aware sleep and wake for battery-friendly operation.
ACCESSORIES
Antennas, power, and mounting matched to your gateway.
Factory-aligned parts for owa3x · owa4x · owa5x with stock and sourcing notes per SKU.
owa450 / owa4X / owa5X - IP67 Antenna LTE GNSS Fakra Screw Mount
ANT-100-9000#W02
owa4X / owa5X - 35 PIN Connector with 35 Cables
CAS-000-5135#35
owa5X - IP67 Cover with External USB
MES-000-5002#P02
Real-World Applications
Use Cases
Mixed construction fleets need telemetry without rewiring CAN-equipped machines.
owa4x bridges CAN bus to cloud with edge processing, enabling fleet-wide visibility without hardware modifications.
Temperature-sensitive cargo requires continuous monitoring with reliable data transmission.
Owasys gateways buffer and store-and-forward at the edge, avoiding data loss during cellular blackspots or coverage gaps.
Remote pumps and compressors need predictive maintenance data without frequent site visits.
owa4x bridges CAN/Modbus to MQTT with local analytics, supporting a 60% reduction in field service visits through remote diagnostics.
Agricultural equipment operates across vast areas with inconsistent cellular coverage.
Multi-band GNSS tracking with edge buffering and store-and-forward keeps operations connected even in remote fields.
A fleet platform needs a white-label gateway for its OEM customers, with custom branding.
owa5x with Melqart software ecosystem enables custom firmware builds, your branding, and full control over the telemetry stack.
Substations and remote sites require secure, unattended operation with maximum uptime.
owa5x with TPM 2.0 and signed OTA updates ensures critical infrastructure remains connected and secure.
Owasys gateways
01Who manufactures the hardware?
Owasys manufactures the gateways. Melqart is an authorized value-added reseller: we source genuine Owasys product, handle configuration and integration for your program, and stand behind deployments with engineering support.
02Is this a Melqart private label?
No. The industrial platform is Owasys owa3x · owa4x · owa5x. Melqart adds VAR services, provisioning, integration, tooling (including alloy-it where you want it), and operational support, without claiming a separate OEM identity for the hardware. owadm is an optional Owasys platform, not a Melqart product.
03Why buy through Melqart instead of sourcing hardware alone?
You get authorized supply plus a team that routinely bridges CAN/Modbus/cellular data to your cloud, hardens images, and documents handover. This reduces integration risk and accelerates time to market while keeping hardware provenance transparent.
04Can we run our own applications on the gateway?
Yes. Owasys open Linux gateways expose a standard runtime; you retain full ownership of your application code and can operate without Melqart-specific lock-in.
05How do OTA updates work?
owadm is an optional Owasys platform for OTA updates and device health. It is not required: you can use your own OTA platform, freely integrated with Owasys gateways. For European customers, owadm contributes to a CRA-ready ecosystem. Updates remain under your governance either way.
06What's the difference between owa3x, owa4x, and owa5x?
owa3x is compact for infrastructure and vehicle telemetry. owa4x adds edge computing and richer I/O for mixed fleets. owa5x is the high-performance model with optional NPU/GPU for edge AI workloads.
07Which cloud platforms are compatible?
Owasys gateways work with any MQTT/HTTPS backend including AWS IoT, Azure IoT Hub, ThingsBoard, and custom platforms. Device management is equally open: optional Owasys owadm for OTA and device health, or your own OTA platform freely integrated with the gateways.
08Can I run Docker containers on the owa5x?
Yes. The owa5x runs a quad-core i.MX8M Plus with a full open Linux userspace, so containerized workloads run natively. We provision a container runtime in the image and tune resource limits for the edge, which keeps your application portable while taking advantage of the gateway's NPU and GPU.
09Do you provide custom Yocto layer maintenance agreements?
Yes. We maintain your custom Yocto layer (Kirkstone and newer) under a support agreement: kernel and CVE updates, BSP rebases, reproducible image builds, and signed OTA delivery, so your fleet stays current and auditable for the life of the deployment.
Tell us what you are connecting
Share your protocols, target estate, and rollout timeline. We will return a scoped response within five working days.