Products · open Linux industrial LTE gateway

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.

Choose your gateway

Owasys owa3x · owa4x · owa5x

Three form factors, one unified platform. Select the gateway that matches your deployment.

Feature
owa3xCompact
owa4xMid-Range
owa5xEnterprise
ProcessorARM Cortex A7 @ 792MHzARM Cortex A8 @ 800MHzQuad A53 @ 1.6GHz (optional NPU/GPU)
RAM / Storage512 MB / 512 MB NAND512 MB / 1 GB NAND (up to 2 GB)2 GB LPDDR4 / 8 GB eMMC (up to 32 GB)
CellularLTE Cat 1 bisLTE Cat 4 (IP 67) / Cat 1 (IP 40)LTE Cat 4
CAN Interfaces2x CAN (344A variant only)Up to 4x CAN (2x CAN 2.0B, 2x CAN FD)Up to 4x CAN-FD
Power9-48V DC input9-36V DC (IP 67) / 9-48V DC (IP 40)9-36V DC input
Ingress ProtectionIP40IP67 / IP40IP67/IP6K9K
Edge AppsEmbedded Linux (Yocto)Debian Linux (C/C++, Python, Java, Lua)Debian/Yocto Linux (container support)
Best ForInfrastructure & vehicle telemetryMixed fleets, harsh environments, vehicle connectivityEdge 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 High Assurance Boot (HAB) for verified images and signed, controlled OTA deployment.

Fleet operations for Owasys gateways

owadm device management

The Owasys owadm device management tool streamlines remote operations and reduces manual configuration effort. Teams can access and manage deployed gateways from any authorized location. Melqart Systems provides value-added integration, onboarding, and support to reduce time to market and development effort.

ThingsBoard
OpenRemote

ThingsBoard

Open-source IoT Platform

Robust and secure management

owadm is the Owasys device management platform built for remote monitoring, management, and secure updates of deployed gateways.

Enterprise ready

Need a custom or on-premise deployment? Melqart Systems can deliver owadm on your infrastructure and bundle it with Owasys gateways, tailored to your requirements and data sovereignty needs.

+50K devices

Managed globally

120 countries

Active deployments

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 interfaces

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.

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.

Fleet platform needs white-label gateway solution for 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, signed OTA updates, and dual-SIM failover ensures critical infrastructure remains connected and secure.

FAQ

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 owadm and alloy-it where you want them), and operational support, without claiming a separate OEM identity for the hardware.

— 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?

You can use your own update path or adopt Melqart patterns (including owadm) for signed, controlled rollouts. 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 enterprise-grade 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. Melqart can optionally operate owadm for fleet management alongside your integration.

— 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.