A remote.it alternative for camera and alarm sites
remote.it gives people secure sessions to machines behind CGNAT, cellular and Starlink, through software on a computer at the site. We built Relayant for a control room that reaches every device at a site by a standing address and port, and is told when one stops answering. Here is where each fits.
What it is good at
remote.it reaches machines behind CGNAT without opening a port
remote.it provides secure remote access to equipment, for operations, OT security, automation and IT teams. Its software on the site's network reaches out and stays in touch, so it works behind firewalls, CGNAT, cellular and Starlink. No port forwarding, firewall rule or static public address is needed.
A small agent registers a device to your organisation. Access is authorised per service, against your policies and single sign-on, and remote.it brokers an encrypted tunnel. For cameras and recorders, which do not accept software, it is installed once on an always-on computer on the same network, which passes connections on to them (a "jump" service).
The person connecting signs in at app.remote.it, picks the service and connects. A Personal plan is free for non-commercial use with up to five devices.
Where it falls short
A session for a person, not a standing address for software
Each of these is from remote.it's own pages, read on 16 October 2026.
- The address works on one machine
- A connection gives a local address and port, such as 127.0.0.1:33000, that works only on the connecting person's own machine. Monitoring software in a control room connects to each device by address and port, from its own PCs. We give each chosen device one address and port that stays the same, and only the addresses you list can reach it.
- A computer at the site has to stay on
- For cameras and recorders, remote.it runs on an always-on computer on the same network. Our box plugs into a LAN port of the site's router and does that job itself; no computer at the site is needed.
- Online and offline, not how a device is
- remote.it's webhooks report when a device, or a service registered to it, goes online or offline. Its pages do not describe telling a hung camera from an unplugged one, asking a printer or UPS how it is, alarm signals to a control room, or a monthly report per site.
Side by side
Eight things a control room asks, answered for both
| The question | Relayant | remote.it |
|---|---|---|
| Behind CGNAT, 4G and Starlink | Works: the box connects out over an encrypted WireGuard tunnel, and nothing is opened on the router. | Works: its software reaches out, with no port forwarding, firewall rule or static public address.docs.remote.it, 16 October 2026 |
| What has to be at the site | Our box on a LAN port of the router, or our software agent on a Linux PC or a router you own. | Its software on one always-on computer on the same network as the cameras, which passes connections on to them.docs.remote.it, 16 October 2026 |
| Finding the devices | The box finds the devices on the site's network and names the maker and model where it can. | Each camera or recorder is reached as a service of the always-on computer, which passes the connection on.docs.remote.it, 16 October 2026 |
| How the control room connects | One standing address and port per device, from any monitoring software that connects by address and port, from the addresses you list. Through our cloud relay or your own local relays. | A person signs in at app.remote.it, picks the service and connects. The local address and port it gives work only on that person's own machine.docs.remote.it, 16 October 2026 |
| Checking each device | Every device, every minute: working, on the network but not answering, or down. SNMP, Modbus and BACnet devices are asked how they are. | Webhooks report when a device, or a service registered to it, goes online or offline.docs.remote.it/developer-tools/webhooks, 16 October 2026 |
| Alarm signals to the control room | Into your monitoring software over SIA DC-09, as supplementary fault signalling. | Not described on the pages checked.The four pages linked on this page, 16 October 2026 |
| A monthly report per site | A PDF per site on the first of the month, covering the devices at the site. | Not described on the pages checked. Activity logs are kept for a period that depends on the plan.remote.it/pricing, 16 October 2026 |
| How it is paid for | Per box at a live site. A software agent counts as a box. | Personal is free for non-commercial use, with five devices. Paid plans are priced per licence; each licence adds devices and user accounts.remote.it/pricing, 16 October 2026 |
"Not described" means exactly that: the vendor's pages, read on the date shown, do not mention it. It does not mean the product cannot do it.
About alarm signals
Our alarm signals are supplementary fault signals. They tell your control room that a device has stopped answering, has a fault, or that a site’s network is down. They do not replace the alarm panel’s own communicator.
When to choose it anyway
Engineers reaching machines, one session at a time
Choose remote.it when the people connecting are engineers and technicians, each opening a session to a machine's web page, SSH or remote desktop. Access authorised per service against single sign-on suits that work. It also suits a site that already has an always-on computer, and personal projects on the free plan.
Our box suits a control room whose monitoring software must reach every camera and recorder at a site, all day, at an address that does not change. It suits a device that stops answering being told to the right people, or sent to the monitoring software as an alarm signal, and one report a month per site. The box does not look at video; it relays the device ports you choose.
Tell us how your sites connect
Say how many sites you look after, how they reach the internet and what monitoring software you use. We reply by email.
Checked against remote.it's published information on 16 October 2026. Tell us if something has changed: hello@relayant.net.
Product names belong to their owners.