We carry the connection and check that devices answer.

This page says what Relayant is and is not, where we make it, who we built it for, and the rules we build to.

What it is

It carries connections and watches devices. Nothing more.

Our product is not a video management system. It is the part that reaches the site, keeps the address steady, and says when a device stops answering.

What it does

A Relayant box at the site connects out over an encrypted WireGuard tunnel. Nothing is opened or forwarded on the site's router.

Each device you choose gets one address and port. Any monitoring software that connects by address and port uses it, and it stays the same when the device moves on the site's network.

The box checks every device every minute and reports when one stops answering. Alerts go to the portal, email, Slack, Microsoft Teams and webhooks, and as alarm signals into your monitoring software.

What it is not

It is not a video management system. The box relays video encrypted. We do not store, transcode or inspect it. We count bytes, nothing more.

We hold no device logins and do not sign in to a device. So video content, picture quality and recording are not checked; only that the device answers.

It is not a cheaper static IP. What it removes is the looking-after: the site visit, the router password, the port forward that stops working.

Where

Made in New Zealand

We are a New Zealand business. We make the software in the box, the portal and this site here, for sites that are often a long way from anyone.

Who it is for

Built for control rooms first

We built Relayant for alarm receiving centres first. The same box now serves anyone with a site they cannot reach.

Alarm receiving centres first
We built Relayant for alarm receiving centres (ARCs). It is in use at a control room today for remote access, alarm signals and local relays.
Then anyone with a site they cannot reach
A farm on Starlink, a quarry on 4G, a building behind someone else's IT. Sites on mobile and satellite connections are almost always behind CGNAT. CGNAT is carrier-grade NAT: the site shares a public address with many others, so nothing can be forwarded to it. The same box serves them all.
See who Relayant is for

Principles

Three rules we build to

We have written them down, and we build the product to them.

The box is built to run without a person

Once a box is plugged in, nobody on site needs to touch it again. When the site has internet and power and our servers are reachable, the box is connected.

In every other state it keeps trying, by itself, until it is. A box that needs looking after has removed nothing.

Nothing opens at the site

The box connects out, and nothing opens at the site. The relay reaches only the device-and-port pairs you chose, and only from the addresses you list.

We hold no device logins. No setting opens the site's router or lets the relay reach beyond the pairs you chose. Where a choice is less safe, the portal says so.

This site describes the product as it is

Nothing on this site is a plan. A feature described here is in the product today, and if it needs setting up, the page says so.

Tell us about your sites

Email us with how many sites you look after, how they connect and what monitoring software you use. We reply by email.

Email [email protected] Sign in

Security reports go to the same address. The contact page says what to include.