
Reach the machine by the addresses in its manual
No public IP address at the customer, no inbound rule in their firewall, no router to sell with every machine.

Every machine sits in someone else's network
Machine and plant builders with an installed base at customers, service technicians - and the customer's IT that does not want to open anything.
No public internet address, mobile routers
Many machines sit behind CGNAT (the provider gives no public internet address) or a mobile router.
No inbound rules
The customer's IT refuses them; a VPN into the plant needs approval for each job.
Hardware per machine
Dedicated remote-maintenance routers cost money for every unit you ship.

A small device in the machine dials out
- 1
Awacino in the machine
A Raspberry Pi or another ARM board, an industrial PC or a container runs the unattended client and dials out - headless, no admin rights.
- 2
The technician beams in
With your company account, or with a Beam-in code from the customer; the laptop gets a SituIP in the machine network.
- 3
The engineering tool just works
It reaches the PLC (the machine controller) at the address the manual gives. The code ends with the job; every connection is in the audit log.

Remote maintenance without the router
Software on hardware you choose; the devices behind it are not counted.
Addresses from the manual
The laptop is in the machine network; tools and documentation stay valid.
No change at the customer
No inbound rule, no public IP address. The device dials out like every remote-maintenance service.
Access per job
A Beam-in code per job: paused or revoked at once, owned by the first device that redeems it.
On any internet line, also 4G and 5G
Neither end needs a public address.
Controllers and panels are not counted
Only the device with Awacino counts as a Beam-in device; the PLCs and HMIs (machine controllers and control panels) behind it never count.
A record per machine
Every connection in the audit log: who, which device, when, from where.
Your network traffic goes directly between your devices - never through our servers.

Awacino and industrial remote maintenance
Software and a direct path - no router to sell with every machine.
| Awacino | TeamViewer | ewon / Talk2M (HMS) | IXON Cloud | Siemens SINEMA RC + SCALANCE M | |
|---|---|---|---|---|---|
| Hardware at the machine | Software on a Pi, an industrial PC or a container | Software on a PC or control panel | ewon router (Flexy, Cosy) | IXrouter (around £400 per unit, UK reseller) | SCALANCE M router or security appliance |
| Technician reaches | The machine network with a real local address | The screen of one PC or control panel | The machine network through an OpenVPN tunnel | The machine network through a VPN | The machine network through a VPN |
| Data path | Direct between the devices, never via our servers | Direct or via TeamViewer servers | Via the Talk2M servers (outbound UDP 1194 / TCP 443) | Via the IXON cloud | Via the SINEMA RC server (yours or hosted) |
| Inbound rule at the customer | None | None | None | None | None |
| Third-party access | Beam-in code per job, revocable | Session ID | Talk2M users and pools | Users and roles in the portal | Role concept per user and device |
| Setup and upkeep | One app or one small client per network; each device signs in with the user's account or a Beam-in code; users and codes managed in one place; nothing to configure on the router or per device | An agent on every computer; licences per seat or concurrent channel | A router per machine to install and configure; users and pools in Talk2M | An IXrouter per machine; users and roles in the portal | A SCALANCE M router per site plus the SINEMA RC server (own or hosted) |
Competitor facts: vendor pages and Awacino market research, November 2026.

What we offer machine builders
Each machine with the unattended client is one Beam-in device; the controllers, panels and drives in its network are not counted.
Technicians see only their machines
Access per technician and machine, with an end date for service partners.
Two-step confirmation before every connection
Required before anyone reaches a machine at a customer site.
Every access logged for your customers' audits
Who reached which machine, when and for how long - 12 months, with export.
A Beam-in code per service call
Your service portal creates the code for one machine or one port, and it ends on its own.
Machines registered from your production line
A one-time setup code per machine at the end of the line; the machine appears as a Beam-in device.
Fleet offer
Your installed base under one contract: we make you an offer.
Fleet offer - talk to us
Asked by machine builders
Does the customer have to change the firewall?
No inbound rule. The device needs outbound internet; strict networks allow it like any remote-maintenance service.
Can the technician use the vendor's engineering software?
Yes - the laptop has a SituIP in the machine network, so the controller answers at its usual address.
How do we control who is in a machine?
Beam-in codes per job, owned by the first device that redeems them, paused or revoked at any time; every connection is in the audit log.
Can a code be limited to one controller or one port?
Yes. A Beam-in code reaches exactly what you choose in one network: the whole network, one device, or one port on a device. Several networks? Use one code per network - side by side in the app.
Reach your machines, not just their screens
Show us one machine; we show you the technician in its network.