Shipowners & Fleet Managers

Standardize cyber-resilient practices across newbuilds and refits. MG Core helps you implement the controls and documentation class societies now expect under E26/E27, while keeping day-to-day operations practical for crews.

Bridge & Nav/Comm OEMs

Integrate cleanly into a 460-Network with gateway roles (460-Gateway / 460-Wireless Gateway / 460-Forwarder) and a documented internal DMZ for applications. You get a predictable way to separate controlled from uncontrolled networks and demonstrate “direct communication” behavior via VPN.

IT/OT Security & Integrators

Run approved services inside a governed environment, apply least-privilege for management, and maintain an audit trail for change. When paired with a type-approved Robustel gateway, you have a single, class-friendly platform to deploy and sustain.

Built to support UR E26/E27 adoption

The OS, roles and workflows are designed to align with the cyber-resilience expectations now mandatory for new ships (design/build contracts signed 1 July 2024 or later). MG Core helps you implement what E26/E27 ask for at the ship and system level without reinventing your processes. 

IEC 61162-460 aware networking

MG Core supports the architectural patterns used in a 460-Network—including the concepts of controlled vs uncontrolled networks, 460-Gateway / 460-Forwarder, and a protected DMZ for onboard services—so nav and radio systems can exchange data securely.   

Internal DMZ for onboard apps

Run customer services (e.g., antivirus, logging, approved app services) in an internal DMZ on the gateway. This helps segregate exposure while reducing extra boxes, power bricks and cabling on the bridge. 

Direct communication via VPN

When IEC 61162-460 calls for “direct communication” to unmanaged/external networks, MG Core supports VPN-based access controlled on the vessel, so crews can enable, observe, and revoke access in line with procedures. 

Router-grade base, marine-grade hardware

You keep deterministic routing, firewalling and diagnostics under a clear WebUI/CLI. When MG Core runs on a Robustel MG460 or other supported maritime gateway, you add marine interfaces (GbE, serial, DI/DO), conformal coating and class-relevant type approvals. 

Take your Local Workflow to the Cloud

Everything you do on the device can be mirrored in RCMS with the same menus and logic. Schedule upgrades, push configurations, monitor health, and run diagnostics across one site or thousands without changing how you work locally.

Your crew and integrators control who can do what on the box; Robustel hardens the platform and demonstrates process maturity expected by class and owners.

Secure from Ship to Shore
  • Role-based access & encrypted management: Lock down Web Manager and shells, bind to shipboard certificates, and keep logs suitable for audit and incident reviews. 
  • Signed software delivery: Run approved applications inside an internal DMZ and use signed, governed installs so changes are deliberate and traceable. 
  • Structured updates & third-party testing: Robustel maintains a formal security update program and independent testing cadence; our secure development lifecycle is aligned to IEC 62443-4-1 and audited. 
  • Designed for class evidence: MG Core + Robustel gateways map cleanly to the evidence owners and yards need when demonstrating E26/E27 cyber-resilience during design, commissioning and operation. 

Maritime Gateways for MG Core

Run MG Core on hardware built for the bridge. Robustel marine gateways pair router-grade networking with the I/O ships rely on, so your applications run on the same device that secures and connects them. Choose the form factor and interfaces you need; validate on a single vessel; standardize across the fleet.

Power events, intermittent links, and long service life are normal at sea. MG Core is engineered so changes are predictable and recovery is fast.

Resilience Highlights
  • Predictable upgrades & rollbacks: Test on a few units, then roll out; revert cleanly if behavior or trials demand it.
  • Layered filesystem & journaling: Protect base OS operation during updates and reduce corruption risk after hard power cycles.
  • Multiple reset paths: From service restarts to “reset-to-default,” you have a clear path back to known-good.
  • Marine-optimised gateway portfolio: When MG Core runs on an MG-class gateway, you add physical ports, conformal coating and type approvals appropriate to SOLAS environments.

Start with a single gateway, add the services that matter for the vessel, and scale when approved. MG Core gives you two delivery paths—containers for portability, native apps for deeper integration—so you can pick the right control model.

Containers for Navigation/Bridge Services

Package data collection, protocol bridging, or approved utility services as containers inside the internal DMZ. You reduce attachment points while keeping clear boundaries between controlled and uncontrolled networks.  

Native apps when you need tighter coupling

Where latency or device integration demand it, deliver signed native apps governed by MG Core. You keep a predictable upgrade/rollback story that fits class processes.

Typical onboard workloads
  • ECDIS integrations and secure forwarding between 460-Networks and other controlled domains.
  • Logging, antivirus updates and shipboard utility services inside the internal DMZ.
  • Store-and-forward for data that must survive link loss or satellite outages. 

Work with IoT Experts who Respect your Industry Knowledge

You know your industry best. We bring deep expertise in IoT device development and deployment, turning your goals into stable designs, repeatable profiles, and smooth rollouts. Together we build a long term partnership that supports scale, growth, and efficiency.


New to IACS UR E26/E27 or IEC 61162-460 and how they translate into a real shipboard network? The answers below explain what MG Core is, how it supports a 460-Network architecture (including an internal DMZ), what you can run on the gateway, and where RCMS Stack Marine helps (router operations and controlled VPN access) versus what remains managed on the device (Debian apps and containers). Note: MG Core is designed to help implement the practices those standards expect; final compliance depends on your vessel design, documentation, and class approval. If your question is not covered, Talk to a Maritime Gateway Specialist and we will map the best path for your project.

Does MG Core make my vessel “compliant” by itself?

No operating system can guarantee compliance on its own. MG Core is designed to help implement cyber-resilient practices aligned with IACS UR E26/E27 and support an IEC 61162-460 network; final compliance depends on your overall design, documentation and successful class approval. 

What is IEC 61162-460 in plain terms?

It’s the maritime standard for secure Ethernet interconnection among navigation and radio systems—multiple talkers/listeners—with defined roles like 460-Gateway/Forwarder and requirements for controlled networks, DMZ, and secure interconnection to other networks. 

What is IACS UR E26 vs UR E27?

E26 sets ship-level minimum cyber-resilience requirements across design, commissioning and operation; E27 sets requirements for on-board systems/equipment (IT and OT). Both are now mandatory for in-scope newbuilds. 

Can MG Core run on a type-approved gateway?

Yes—MG Core runs on Robustel’s maritime gateways. When deployed on, for example, the MG460, you benefit from marine interfaces, an internal DMZ, and class-relevant type approvals documented by DNV. (Hardware approvals remain at the device level.)   

How is “direct communication” handled?

IEC 61162-460 specifies that connections to uncontrolled networks must be secured via VPN. With RCMS Stack Marine, crews can enable on-demand VPN for controlled access, observe status, and revoke when work is complete. 

What documentation/evidence can MG Core help produce?

Role/privilege settings, audit logs, software inventories, and change records (updates, signed installs) align with the evidence owners, yards and class surveyors typically request under E26/E27 programs. Final documentation packages are project-specific.