Skip to content
Respondr

Choose your Respondr architecture: cloud, on premise or hybrid.

At the centre of the infrastructure is Respondr Server, which can run in the cloud on AWS or on your own hardware. Radio gateways, consoles and apps connect to the server.

Schedule a demo
Front of a rack with the Respondr server: a black panel with the Respondr logo next to a rack-mounted mini PC, above a network switch with fibre and Ethernet cables.
01 — Deployment

Cloud, on-premise, or hybrid.

In the cloud, Respondr Server runs on AWS. On premise, it runs on your hardware and the data stays inside your network. In the hybrid model, the server is in the cloud and the radio gateways are at your sites.

Cloud — on AWS, encrypted storage
On-premise — your hardware, your data, air-gap friendly
Hybrid — local gateways, cloud server
02 — Dual LAN

Two LAN ports, two separate networks.

Some radio gateways, such as the FT636B and FT638, have two LAN ports. You can connect each port to a different network with its own IP addressing, and carry up to 8 links on each port.

Two LAN ports on FT636B and FT638
Separate IP addressing for each network
Links checked about every 10 seconds and restored by themselves
03 — Radio integration

Physical radios go through a gateway, apps connect to the server.

Each radio network connects to Respondr Server through a gateway, which turns the voice and signals of the radio into IP data. Console, app and PoC radios connect directly to the server instead. So the operator in the control room talks with the radios in the field on the same channel.

One gateway for each radio network
VHF, DMR, TETRA, NEXEDGE and P25
App and console without a gateway

What the platform guarantees

The architecture guarantees real-time voice, encrypted transport, controlled access and an audit trail behind every action.

Real-time voice

Instant push-to-talk across every connected network. Audio streams to the server and is forwarded to the rest of the channel while the talker is still speaking, the way professional radio behaves.

Encrypted transport

Voice and messages travel encrypted between the app, the console and the server: TLS 1.3 on every connection, and AES-128-GCM on audio sent over UDP.

Audit logging

Respondr tracks every action, so a compliance review, NIS2 included, starts from a record rather than a reconstruction.

OIDC SSO + MFA

Sign-in through corporate identity providers over OIDC, with TOTP multi-factor authentication on the accounts that need it.

Account lockout

After 5 failed sign-in attempts, Respondr locks the account for 15 minutes, so nobody can try one password after another.

Granular permissions

Admin and Operator roles, with access policies per channel, gateway and user, so each operator sees only what the job needs.

Frequently asked questions

Yes, with the Enterprise plan. The complete stack, server, database and recording, can run on your hardware inside your network, and the local radio gateways connect to it directly.

We’ll show you Respondr in a live demo.

We offer a 30-minute live demo built around your radio infrastructure.

Schedule a demoContact us
On-Premise or Cloud Dispatch Architecture | Respondr