Eziwan vs. Ewon Flexy — A Comprehensive Comparison
Ewon Flexy (HMS Networks) is the leading solution for industrial remote access in Europe. Eziwan is a newer solution designed for large-scale cloud-native deployments with built-in monitoring.
This comparison is objective: both solutions have distinct strengths, and the right choice depends on your specific situation. We also include a 3-year TCO calculation and a migration guide for teams switching from Ewon.
Overview of the Two Solutions
Ewon Flexy (HMS Networks)
Origin: HMS Networks (Sweden), founded in 1988. Ewon is the industrial IoT division, which has been in operation since 2004. The Ewon Flexy was launched around 2013–2014.
Architecture: Modular industrial router with a motherboard and expansion cards (WAN, LAN, protocols). This modularity is Ewon’s main strength—it allows for the combination of numerous industrial protocols (Profibus, EtherNet/IP, DF1, CAN, BACnet) on a single device.
Ecosystem:
- Talk2M: a cloud-based VPN platform hosted by HMS, with servers in Europe and North America
- eCatcher: a Windows/Mac VPN client for remote access
- DataMailbox: a cloud-based data collection service
- Flexy Designer: dashboard creation tool
- AWB (Action When Box): rules engine for alerts and automations
Market Position: A widely used solution in Europe, with a large community of trained integrators and an installed base of several hundred thousand devices.
Eziwan
Origin: A French startup founded in 2020. Designed from the outset for large-scale industrial deployment.
Architecture: All-in-one DIN-rail gateway, designed for zero-touch provisioning and cloud-native monitoring.
Ecosystem:
- Eziwan Cloud: a unique SaaS platform (monitoring, VPN, alerts, history, fleet management)
- Universal OpenVPN client for remote access
- Open REST API for integration with third-party tools
- iOS/Android mobile app
Market Position: A newer solution, experiencing rapid growth in the multi-site monitoring and OEM deployment segments.
Detailed Comparison Table
| Criterion | Ewon Flexy | Eziwan |
|---|---|---|
| Hardware | ||
| Architecture | Modular (expansion cards) | All-in-one |
| Dimensions | Varies by configuration | Compact DIN rail |
| Temperature range | -25°C to +70°C | -40°C to +75°C |
| Certifications | CE, UL, cUL, ATEX (optional) | CE, FCC, RoHS |
| Network Connectivity | ||
| Integrated 4G LTE | Optional (4G WAN card) | Yes, native |
| Dual SIM | Depending on model | Yes, native |
| SIM included with subscription | No | Yes (multi-carrier) |
| Automatic failover | Yes | Yes (< 8 seconds) |
| Wi-Fi | Optional (Wi-Fi card) | No |
| Ethernet LAN | 1 port (base) | 1 port |
| Industrial protocols | ||
| Modbus RTU / TCP | ✓ | ✓ |
| OPC-UA | ✓ (optional) | ✓ |
| MQTT | ✓ | ✓ |
| Profibus DP | ✓ (HE205PB card) | ✗ |
| Native EtherNet/IP | ✓ (HE205EIP card) | ✗ (Allen-Bradley Modbus TCP) |
| DF1 (Allen-Bradley) | ✓ (HE205DF1 card) | ✗ |
| BACnet | ✓ (HE205BAC card) | ✗ |
| CAN | ✓ (HE205CAN card) | ✗ |
| Deployment | ||
| Zero-Touch Provisioning | Partial (pre-configured file) | Full (QR code) |
| Commissioning time | 30 min to 3h | < 5 minutes |
| Network intervention required | Depends on configuration | No |
| Mass deployment | Manual | Automated |
| Remote access | ||
| VPN Protocol | Talk2M (proprietary/OpenVPN) | OpenVPN / IPSec |
| VPN Client | eCatcher (Windows/Mac) | OpenVPN (universal) |
| Inbound Ports Exposed | No | No |
| MFA | Talk2M Pro (paid option) | Included |
| Exportable audit logs | Yes | Yes |
| Reconnection after 4G disconnection | 15–30 s | < 2 s (OpenVPN) |
| Cloud and Monitoring | ||
| Multi-site dashboard | Talk2M (VPN-focused) + Flexy Designer | Native, comprehensive |
| SMS/email alerts | Via DataMailbox/AWB | Native |
| Data history | DataMailbox (paid option) | Native |
| Automatic reports | No (via AWB scripts) | Native |
| Map view | No | Yes |
| Mobile app | Unofficial | Yes (iOS/Android) |
| REST API | Limited | Complete and documented |
| Fleet management | ||
| Remote firmware update | Yes | Yes (automatic) |
| Connectivity status view | Yes (Talk2M) | Yes |
| 4G signal quality | No | Yes (RSRP, RSRQ, SINR) |
| Pricing | ||
| Model | Hardware + Talk2M (subscription) + DataMailbox (optional) | Hardware + all-inclusive subscription |
| SIM included | No | Yes |
| Price transparency | Upon request | Public price list |
3-Year TCO Analysis — 50 Sites
Calculation Assumptions
For 50 industrial sites with Modbus TCP monitoring (M340 or S7-1200), VPN access for maintenance, and historical data collection.
Ewon Flexy Costs (typical 50-site configuration):
| Item | Calculation | Amount |
|---|---|---|
| Equipment (Flexy 205 × 50) | 50 × 850 € | 42,500 € |
| Talk2M Corporate (50 sites) | 50 × 35 €/month × 36 months | 63,000 € |
| DataMailbox (data collection) | 50 × 15 €/month × 36 months | 27,000 € |
| Orange SIM (50 × 1 SIM) | 50 × 8 €/month × 36 months | 14,400 € |
| SFR SIM (50 × 1 SIM for redundancy) | 50 × 8 €/month × 36 months | 14,400 € |
| Deployment (30 min/site × 50) | 50 × €37.5 (30 min at €75/hour) | €1,875 |
| SIM administration (2 hours/month) | 2 hours × €75 × 36 months | €5,400 |
| eCatcher / Flexy Designer Training | Flat rate | 2,000 € |
| 3-Year Total (Ewon) | ~170,575 € |
Eziwan Costs (configuration equivalent to 50 sites):
| Item | Calculation | Amount |
|---|---|---|
| Hardware (Eziwan Gateway × 50) | 50 × X € (price per quote) | Variable |
| All-inclusive subscription × 50 | 50 × Y €/month × 36 months | Variable |
| SIM included in subscription | 0 € additional | 0 € |
| ZTP deployment (20 min/site × 50) | 50 × 25 € (20 min at 75€/h) | 1,250 € |
| SIM administration | Included | 0 € |
| Training (2 hours online) | 0 € (included in partner program) | 0 € |
Note: Eziwan rates are available upon request. The exact total cost of ownership (TCO) depends on commercial negotiations and volume.
What TCO Doesn't Tell You
Beyond the cost itself, two factors set these solutions apart:
Deployment Time Cost: An Ewon deployment that takes 3 months (network coordination, training, testing) versus an Eziwan ZTP deployment that takes 3 weeks results in 2 months of unavailable monitoring—an opportunity cost that is difficult to quantify but very real.
Administrative costs: Managing 100 SIM lines (50 Orange + 50 SFR) involves a significant administrative burden: tracking invoices, handling carrier issues, and canceling contracts when relocating.
When to Choose Ewon Flexy
Use Cases That Benefit Ewon
1. Protocols not supported by Eziwan: If your system includes older Allen-Bradley controllers (DF1, DH+), active Profibus networks, or BACnet (smart building) equipment, the Ewon modular architecture with expansion cards is often the only viable option without an additional gateway.
2. Existing Fleet with Trained Technicians: If your team has been using eCatcher for years and 20 technicians are familiar with the Ewon system, the cost of migration (training, transition) may outweigh the benefits of a change, especially for a medium-sized fleet.
3. ATEX Environments: Ewon offers ATEX-certified versions for potentially explosive areas. Eziwan does not yet have ATEX certification.
4. Integration with Ewon-certified systems: Some SCADA and MES systems on the market have Talk2M-certified connectors. If your existing infrastructure is tightly integrated with the Ewon ecosystem, migration will incur costs.
When to Choose Eziwan
Use Cases Suitable for Eziwan
1. Deployment of 10+ Modbus TCP/RTU sites: Zero-Touch Provisioning and the included multi-carrier SIM card make Eziwan the most efficient choice for large-scale monitoring projects involving Siemens, Schneider, Wago, or Modbus-compatible PLCs.
2. Cloud-native monitoring (not just VPN): If your priority is to have a multi-site monitoring dashboard with historical data, alerts, and reports—and not just VPN access for troubleshooting—Eziwan offers these features natively without any additional configuration.
3. OEMs Integrating Remote Maintenance as Standard: The comprehensive REST API, ZTP, and included SIM card make Eziwan the natural choice for machine manufacturers who want to integrate connectivity into their standard offerings.
4. Fleets with 20 or more sites and rotating technicians: Eziwan’s centralized account management, audit logs, and integrated MFA meet the traceability requirements for teams with multiple technicians.
Guide to Migrating from Ewon to Eziwan
If you manage an existing fleet using Ewon Flexy and would like to migrate to Eziwan, here are the recommended steps.
Phase 1 — Compatibility Audit (Week 1)
-
Protocol Inventory: Verify that all your PLCs are supported by Modbus TCP/RTU or OPC-UA. Ewon’s proprietary protocols (DF1, DH+, BACnet, Profibus) require special attention.
-
Configuration Inventory: Document the collected variables, alert thresholds, and VPN access by site. This documentation will be used for reconfiguration in Eziwan.
-
Inventory of Integrations: Identify the systems that communicate with Talk2M (SCADA, ERP, reporting tools). These integrations will need to be reconfigured to use the Eziwan API.
Phase 2 — Pilot at 5 sites (weeks 2–5)
Select 5 sites that are representative of the diversity of the network:
- Different types of devices
- Sites with and without specific network constraints
- Geographically dispersed sites (multi-operator 4G coverage test)
Deploy the Eziwan gateways at these 5 sites in parallel with the existing Ewon devices, without taking the latter offline. Verify:
- Modbus data collection on each type of PLC
- The quality and relevance of the alerts
- VPN access from TIA Portal / EcoStruxure
- Data export for existing integrations
Phase 3 — Phased Migration (Weeks 6–N)
Remove the Ewon units and deploy the Eziwan units in waves of 10 to 20 sites. The pace depends on the availability of maintenance technicians for the physical installations.
What's changing for users:
- The VPN client is switching from eCatcher to OpenVPN (a universal, lighter client)
- The dashboard is switching from Talk2M + Flexy Designer to the Eziwan platform
- SIM subscriptions are being consolidated into a single subscription with Eziwan
What remains the same:
- The PLCs' IP addresses (no network changes)
- The PLC program (no code changes)
- VPN access from TIA Portal / EcoStruxure / eCatcher (the SCADA software still sees the PLCs at their local IP addresses)
Key Considerations During Migration
Variable Reconfiguration: Eziwan cannot automatically import Ewon configurations (incompatible formats). Use the documentation created during the audit to reconfigure the variables in the Eziwan dashboard.
SIM Contracts: Ewon SIM contracts may have minimum commitment periods. Check the cancellation terms before planning your switch.
Team Training: Schedule a 2-hour training session for the driving teams and a 2-hour session for the maintenance technicians.
Other Alternatives to Consider
For the sake of completeness, the industrial IoT router market includes other players:
| Vendor | Strengths | Weaknesses |
|---|---|---|
| Moxa (EDR series) | Very rugged hardware, ATEX-certified, wide range | Limited cloud interface, no SIM included |
| Cradlepoint (Ericsson) | Excellent for enterprise IoT fleets, SD-WAN | IT-oriented, not native OT |
| Teltonika (RUT series) | Very good value for money, open source | Fewer industrial integrations, no ZTP |
| Sierra Wireless (ALEOS) | Solid, established in the energy sector | Acquired by Semtech, future developments uncertain |
None of these alternatives natively combine ZTP, a multi-carrier SIM, OT cloud monitoring, and industrial protocols the way Eziwan does.
Are you evaluating both options for a specific project and looking for technical advice?
Tell us about your situation (types of PLCs, number of sites, protocols), and we'll help you determine whether Eziwan is right for your use case—even if it isn't.
See also the quick start guide to test Eziwan on your first site.
Frequently Asked Questions
Is Eziwan compatible with devices already connected to an Ewon Flexy?
Yes: The same interfaces (Ethernet, RS-232/RS-485 serial, Modbus, and manufacturer-specific protocols via VPN passthrough) are supported. The migration involves only replacing the device and importing the configuration.
Is it possible to migrate an existing Ewon system in phases?
Yes, site by site: the two systems operate side by side during the transition, and Zero Touch Provisioning allows Eziwan gateways to be deployed without a network technician on site.
Is a SIM card included with the Eziwan plan?
Yes, multi-carrier M2M SIM connectivity is included in the subscription: there’s no need to manage a separate carrier contract, and data usage is monitored from the same console as the device fleet.
What's the difference between the pricing models?
Eziwan charges a all-inclusive subscription fee (hardware, SIM card, platform, support), whereas the traditional approach involves separate charges for the device, the Talk2M/M2Web license, the carrier’s SIM card, and monitoring. The 3-year TCO comparison above details the calculation.
Related Resources
- Ewon Alternative for IIoT — the dedicated solution page
- Industrial 4G Router — Eziwan hardware specifications
- Industrial IoT Gateway — Modbus, RS-485, and cloud data collection
- Industrial Router vs. Internet Box — another useful comparison
- Pricing — details of the all-inclusive subscription