Can we run Respondr with no connection to the internet?

Yes, with the Enterprise plan. The complete stack, core, database and recording, runs on your own hardware inside your network. Local radio gateways keep working with no external connection at all.

Where is our voice data stored?

With Free, Essential and Business it is hosted by AWS in the European Union, on encrypted volumes. With Enterprise the server is dedicated: on premise the data never leaves your building, and on AWS it stays in the country you choose, on volumes encrypted with EBS and KMS.

Can we use our own single sign-on?

Yes, with Business and Enterprise. Respondr connects to external identity providers over OIDC, configured per organization, so accounts are created and removed where you already manage them.

Are recordings and logs kept forever?

No. Application, gateway and hub logs each have their own retention window, and recording retention is a deployment setting. Keeping everything indefinitely is a liability, not a feature.

How is Respondr different from a consumer push-to-talk app on this?

Consumer PTT services are hosted for you, in a region they choose, with one account model. Respondr can run entirely inside your infrastructure, authenticates against your identity provider, grants access per channel, and logs what happened.

Secure push-to-talk you can run on premise.

Respondr is built for operators who have to prove how their communications work, not just describe them. Encrypted transport, identity you already run, permissions per channel, and a record behind every action.

Schedule a demo

A row of server racks in a data centre aisle, patch cabling dressed down the front of each cabinet.

01 — Data sovereignty

Your data stays where you decide.

Free, Essential and Business run on Respondr Cloud, hosted by AWS in the European Union. With Enterprise the server is dedicated: you can keep it in your own network or on AWS in the country you choose, and connect your radios through gateways on site.

Respondr Cloud: AWS Europe region, encrypted volumes

Enterprise on premise: your hardware, your network, disks encrypted with LUKS / dm-crypt

Enterprise on AWS: a dedicated instance in the country you choose, encrypted backups in the same region

Enterprise on AWS: radio networks linked over a dedicated encrypted tunnel

A Respondr local server unit, front view, installed on site.

02 — Access control

Identity you already run, permissions per resource.

Users sign in through your corporate identity provider over OIDC, with TOTP multi-factor on the accounts that need it. Access is then granted per resource — which channels a person can hear, which gateways they can touch, which settings they can change.

OIDC single sign-on, configured per organization (Business and Enterprise)

TOTP multi-factor authentication, Google Authenticator compatible

Granular permissions: channels, gateways, users, settings, map

Five failed sign-ins lock the account for 15 minutes

Passwords stored as PBKDF2 hashes

The Access policies page lists three access policies, Airport ramp tablets, Field phones: harbour and Control room consoles, each with a description and the controls to edit or delete it.

03 — Evidence

Every transmission leaves a record.

With Business and Enterprise, channel audio is recorded and searchable, and on every plan the platform keeps separate logs for application events, gateway communication and the real-time hub. When a review asks what was said and who did what, the answer is a query, not a reconstruction.

Channel recording with search, playback and filters (Business and Enterprise)

Separate application, gateway and hub logs, with retention windows

Every administrative action tracked

Email alert when an account signs in from a new device, IP or country

The activity log lists eight sign-ins with user, device, IP address and date, including one attempt that failed on a wrong password.

The controls, one by one

What is enforced by the platform rather than by policy. These are the mechanisms a security questionnaire asks about.

Encrypted voice and messages

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. Recordings and saved messages are encrypted at rest with AES-256.

Multi-factor authentication

TOTP, compatible with Google Authenticator and any standard authenticator app. Enabled per account, so the roles that need it carry it.

Account lockout

Five failed sign-in attempts lock the account for fifteen minutes. A brute-force attempt against a dispatcher account stops at five tries.

OIDC single sign-on

Connect the identity provider you already operate. Joiners and leavers are handled where you already handle them, not in a second directory.

Per-resource permissions

Access is granted per channel, gateway, user, setting and map, not by a single blunt role. An operator hears the channels assigned to them and no others.

An excerpt of the gateway log: timestamped rows record the accepted control connections and the links to the VHF Marine 12, VHF Marine 16, TETRA Ops 1 and Apron VHF channels, including two failed attempts followed by a successful connection.

Audit logging

Application, gateway and hub events are logged separately with their own retention windows, so a compliance review starts from a record.

Where your data lives

Deployment	Storage and encryption
Respondr Cloud	Free, Essential and Business. AWS Europe region, encrypted volumes.
Enterprise on premise	Your hardware, inside your network. Disks encrypted with LUKS / dm-crypt.
Enterprise on AWS	A dedicated instance in the AWS region of the country you choose. Volumes encrypted with EBS and KMS.
In transit	TLS 1.3 between the app, the console and the server; AES-128-GCM on audio sent over UDP.
At rest	Recordings and saved messages encrypted with AES-256.

Standards and frameworks

Where Respondr sits against the frameworks European operators are assessed on. None of these is a product certificate issued by a third party; the NIS2 and IEC 62443 page explains what each one means for Respondr.

IEC 62443

The architecture is designed with reference to ISA/IEC 62443, targeting Security Level 2. Respondr holds no IEC 62443 certification from a third-party body.

Read NIS2 and IEC 62443

NIS2

NIS2 certifies no products. Respondr helps your organization meet its obligations: access control, two-factor authentication, logs, encryption and supplier documentation.

Read NIS2 and IEC 62443

GDPR data residency

Respondr Cloud is hosted by AWS in the European Union. With Enterprise the dedicated server sits in the country you choose or in your own network.

Operational continuity

FT636B and FT638 gateways can link over two separate networks, and dropped links reconnect by themselves, so a single network fault does not take dispatch down. Respondr’s servers on AWS had 99.9% availability over the last 12 months, measured by AWS status checks.

Frequently asked questions

No. Respondr holds no IEC 62443 certification from a third-party body. The architecture is designed with reference to the standard, targeting Security Level 2, and NIS2 certifies no products: Respondr helps you meet its obligations. We can walk your security team through which controls answer which requirement.

We’ll show you Respondr in a live demo.

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

Schedule a demo Contact us