TroutTrout
Industrial remote access

Five ways to reach a machine, compared.

Access Gate controls remote sessions on your own network. Each session reaches one machine over one protocol, with no third-party service.

Last updated:

Robot arms and control terminals on a factory floor

What can the engineer reach once connected?

A VPN connects the engineer to the machine's LAN. The engineer can then reach every device that the network allows, which on a flat network is all of them. Access Gate limits each session to one machine and one protocol, and records it.

Reach any machine, securely.

Three questions before you choose.

Each product on this page puts a device at the machine and connects a technician to it. All of them handle this well. Ewon suits a machine builder who needs one connection without involving the customer's IT team. Three questions separate the options. The table uses public vendor documentation and marks what is not documented.

01

Who runs the service that connects the technician?

The vendor runs Talk2M and IXON Cloud, so your remote access depends on the vendor. A supply-chain security review will include questions about that third party. You can host Secomea and Siemens yourself. Access Gate needs no connection service outside your network.

02

What can the engineer reach once connected?

With Access Gate, the engineer reaches only the machine and protocol named in the session. Other devices on the plant network stay out of reach, and Access Gate records the session. You can keep your existing gateway and add Access Gate behind it.

03

If the internet drops, what still works?

If the internet drops, a cloud-brokered product loses its connection service and remote sessions stop. This is usually acceptable. The bigger question is whether your access policy also depends on that service. If it does, a vendor outage becomes a security incident at your plant. Access Gate enforces policy on site and keeps working in both cases.

Side by side

Industrial remote access options side by side.

Competitor cells come from each vendor's public documentation, linked below. If a vendor does not document a capability publicly, the cell says so.

CapabilityEwon + Talk2MSecomeaSiemens SINEMA RCIXONTrout Access Gate
Who operates the brokerHMS, via Talk2MYou or Secomea; GateManager offers bothYou; you run the SINEMA RC serverIXON, via IXON CloudYou; the gate controls sessions locally
Runs with no third-party serviceNo; Talk2M connects the user to the gatewayYes, with a self-hosted GateManagerYes; the server runs on your infrastructureNo; IXON Cloud connects the user to the gatewayYes; nothing leaves your network
What a session can reachThe machine LAN, over a VPNA registered device, reached via LinkManagerA device or subnet over the VPN tunnelA registered deviceOne user, one asset, one protocol
Session recordingConnection logsAudit logs of connectionsConnection logsConnection logs; session detail varies by planFull session recording and playback
Segments the plant behind itNoNoPartial; with Scalance firewalls deployed alongsideNoYes; controls who reaches what, no VLAN redesign
Automatic asset inventoryNoNo; you register what should be reachableNoPartial; the devices you onboardYes; automatic discovery of what is on the network
Detection and alertingNoNoNot part of the remote-access productNoYes; alerts on unusual traffic, sent to your SIEM
Compliance evidence (IEC 62443 / CMMC)Connection logs onlyAccess logs you assemble yourselfLogs you assemble yourselfConnection logsYes; mapped to IEC 62443 and CMMC
What a 15-machine site looks likeOne Cosy per machine, each managed on its ownOne SiteManager per machine or cellOne server plus a Scalance per enforced boundaryOne gateway per machineOne appliance for the site, one policy set

Sources: Ewon / Talk2M · Secomea · Siemens SINEMA RC · IXON

One-to-one comparisons: Access Gate vs Ewon · Access Gate vs Tosibox · Access Gate vs Secomea · Access Gate vs IXON · Access Gate vs Xage · Access Gate vs BeyondTrust PRA (Bomgar)

Before comparing, see how Ewon remote access and Talk2M work, and where the risk sits.

In production

Where Access Gate runs today.

Trout Access Gate secures defense manufacturers, research institutions and critical-infrastructure operators. These environments run legacy PLCs, SCADA and equipment that cannot take an agent. Customers include Thales, Millbrook Machine, Elna Magnetics, Irish Manufacturing Research, HUN-REN SZTAKI and STBMA.

See customer stories

Questions about industrial remote access.

Access Gate runs remote sessions on your own network. It also controls who reaches what behind them, with no third-party connection service.

Industrial remote access is how an engineer, an OEM or a contractor reaches equipment inside a plant without being on site. PLCs, HMIs and drives cannot run agents and often cannot be patched. A device in front of them handles the access instead: a gateway, a VPN concentrator or a proxy. The products differ mainly in who operates the connection point and in how much a session can reach.

An industrial VPN router provides the connection, but it does not control access. It places the engineer on a network segment. What the engineer can reach then depends on the network layout. For a single machine at a customer site, this is often acceptable. In a plant you own, a contractor working on one line can reach every other device on that segment. Attackers use this path to move laterally, and auditors ask about it. Keep the router for the connection and add a control point behind it.

All three use a gateway at the machine, a client for the technician, and a broker in between. They differ in who runs the broker. The vendor operates Talk2M (Ewon) and IXON Cloud. You can host Secomea's GateManager yourself, and Siemens SINEMA Remote Connect is a server you run yourself. If data sovereignty or a supply-chain security review matters to you, start from this difference.

Yes. Access Gate controls sessions on the appliance itself. No external connection service or vendor service is in the path. Like cloud-brokered products, it needs no inbound firewall rules, because it does not publish a service to the internet.

No. Machines keep their IP address, gateway and routing. Access Gate is added with one route on your existing switch or router. It represents each machine with an overlay twin. Nothing on the plant floor is reconfigured. You can stage the change and roll it back like any routing change.

Often you need more than one. These products are good at connecting a technician to a machine. On a site you do not own, a cloud-brokered gateway such as Ewon or IXON may be the only option you can deploy. Deploying the connection alone leaves a gap. One gateway per machine gives remote access into the plant, with no view of the traffic and no access control at an OT control point. We recommend using both. Keep the gateway where it is useful, and connect Access Gate to your existing network behind it. Every incoming session then goes through identity checks, protocol policy and recording. Each session reaches only the machine it names.

Ask an engineer about your plant.

One call with an engineer tells you if Access Gate fits your plant.