Intercoms and access control panels you can reach, at sites with no static IP.

For intercom and access control remote access, a Relayant box on the site's network connects out and relays only the device ports you choose. It also checks that each intercom, door controller and panel still answers.

Your situation

The controller is at the site, and the way in is not

No static IP
The site's internet has no fixed public address, so there is nothing steady to point your software at.
CGNAT
On 4G, 5G and Starlink the site almost always shares a public address with many others (carrier-grade NAT), so a port forward does nothing. CGNAT in plain words.
Someone else's network
The building's IT will not open ports on their router, and a port forward would put the panel's own login on the internet.
A device gone quiet
An intercom or door controller that drops off the network can stay that way until someone at the site notices.

What changes

Each device port you choose gets one steady address

A Relayant box plugs into the site's network and connects out over an encrypted WireGuard tunnel. The box finds the devices on the network, door controllers among them, and you choose which ports your software needs.

  • Each device port you choose gets one address and port on Relayant that stays the same when the device changes address at the site.
  • Only the internet addresses you list can reach it.
  • The box checks every minute that each monitored device answers, and you can point the check at a controller's own port.
  • Nothing is opened or forwarded on the site's router.

What stays the same

Your software. Any software that connects to a device by address and port uses the address we give it.

The device. We hold no device logins and do not sign in to a device.

The site's network. The relay reaches only the device-and-port pairs you chose, never the site's whole network.

Why nothing needs to be forwarded in First, devices at a site behind carrier-grade NAT with no box: the control room's packets reach the carrier's shared address and are dropped. Then a Relayant box is added at the site beside the devices. It dials out through the same address, a tunnel opens to the cloud relay, and traffic flows in both directions. Site Carrier NAT shared public address Camera Recorder Controller Control room Controlroom Nothing gets in no box yet Cloud relay Cloudrelay Relayant box Relayantbox Tunnel opened from the site box added
Behind carrier-grade NAT the site has no public address of its own, so a connection from outside is stopped at the carrier. The box at the site connects outward instead, and traffic to the ports you chose then flows both ways.

The features that matter most

What an access control installer uses

Remote access

One address and port per device port you choose, reachable only from your listed addresses. The relay reaches nothing else on the site's network.

Read more

Device health

Every minute the box checks that each intercom and controller answers, from ping to its own port. A single missed check raises no alert.

Read more

Alerts

Email, Slack, Microsoft Teams and webhooks, with an Acknowledge link, and alarm signals to a control room's monitoring software.

Read more

How it fits

It fits the sites and control rooms you already work with

A box, or the agent, at the site
A box on a LAN port of the site's router, or the software agent on a Linux PC or a router you own. Either dials out.
The building's IT
The box needs only outbound internet. It works on fibre, DSL, 4G, 5G and Starlink, and asks for no open port. Why CGNAT stops a port forward, and remote access without a static IP.
The control room
A control room can reach the devices through the cloud relay or through its own local relays, and receive device faults in its monitoring software over SIA DC-09.
Supplementary signalling
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.

A day with Relayant

What an access control installer's day looks like

An example, not a customer's story.

  1. Morning

    A door controller at one site stops answering. After the checks confirm it, the alert reaches your team by email with the device's name and site.

  2. Mid-morning

    A technician acknowledges the alert from the email. The site's own staff find the controller's power supply off and switch it back on.

  3. Afternoon

    You connect to another site's intercom through its Relayant address from the office, using your own software, without a visit.

Which plan

Relay, or Relay + Alerts, per box at a live site

Remote access and device checks are in every plan; alerts, alarm signals, webhooks, acknowledge links and monthly reports are in Relay + Alerts. See the plans.

Tell us how many sites you look after, which intercoms and controllers are at them and how each site connects.

Email hello@relayant.net Sign in