Your servers. Your rules.
Run the O-LINK relay on your own servers, and manage every phone from one console. Long-distance traffic stays on your infrastructure, the relay only ever carries end-to-end encrypted packets, and no vendor can switch your team off.
// your own relay
The long-distance path, on your infrastructure.
O-LINK phones talk directly whenever they can: phone to phone, over Wi-Fi, LoRa or the internet. When two phones can't reach each other directly, the relay carries their encrypted packets and keeps them for a phone that is away. By default that is GOTEAM's relay. Your organisation can run its own instead.
// 01 · run it
One small server
The same relay GOTEAM runs: Node.js, no other dependencies and nothing to configure for messages. Put it behind your usual TLS reverse proxy, on-premises, in your data centre or in your own cloud account.
// 02 · point the team at it
One address in the console
The admin enters the relay's address (
wss://relay.example.org/mesh) in the console. Every phone in the organisation switches to it within seconds; one tap switches back.// 03 · what it sees
Ciphertext only
Messages, voice, pictures and positions are encrypted on the phone. The relay sees which phones exchange packets, when, and how much, and that information stays on your servers too.
// limits, plainly
Phones on your relay reach people outside your organisation directly (Wi-Fi, Bluetooth, radio, the internet peer to peer), not through a relay. Waking a closed phone with a notification needs the O-LINK app's push credentials, which only GOTEAM's relay holds: on your own relay, Android phones stay connected through O-LINK's background service, and an iPhone collects its messages when O-LINK is opened. Your team can also be kept off every relay, so nothing leaves your network at all.
// admin console
Every phone, under your control.
The console runs in a browser or on a phone, and talks to the team over the same mesh, so it keeps working when the internet doesn't. It never sees message content: only what the phones report about themselves.
// enrol
Join by QR code
Create join codes with a number of uses, an expiry and a label (night shift, contractor crew). A phone scans one and joins the organisation; nobody else can.
// team rules
One policy for every phone
Routing mode, internet sharing, battery saver, how often phones report, PIN checks, fall detection and no-movement alarms for lone workers, kiosk mode, and which relay the team uses, or none.
// devices
Who is out there
Each phone's battery, links, app version and, if you allow it, last position, from its regular status report.
// lost phones
Revoke and wipe
A lost or stolen phone is cut out of the organisation and wiped when it next connects; teams re-key, so it can't read anything new.
// duress
A silent alarm
A distress code typed at the PIN prompt unlocks the app normally and silently sends you an alert with the phone's position.
// audit
A log of who did what
Joins, rule changes, revocations and alerts, as a hash-chained log that shows if anything was altered. Metadata only, never content, and it stays with your organisation.
// connectors
The console is also where your own systems come in: syslog alarms from firewalls, SCADA gateways and UPSs, SAPIENT drone detections, and team positions to ATAK / TAK. See O-LINK for critical teams.
Run O-LINK on your own terms.
We'll set up a pilot with you: the console, your phones, and the relay on your servers if you want it there from day one.