Can we run Respondr with no connection to the internet?

Yes. 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?

Wherever you deploy. On-premise it never leaves your building, on encrypted disks. In the cloud it stays in the AWS region you choose — the Europe (Milan) region for European operators — on volumes encrypted with EBS and KMS.

Can we use our own single sign-on?

Yes. 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.

Communications you can put in front of an auditor.

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.

The same platform runs three ways. Keep the whole stack inside your own facilities, host it in the AWS Europe region, or split it — gateways on site, core in the cloud. Nothing about the feature set changes between them.

On-premise — your hardware, your network, your disks

EU cloud — AWS Europe region (Milan), EBS encryption with KMS

Hybrid — radio gateways on site, Respondr Core in the cloud

On-premise disks encrypted with LUKS / dm-crypt

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

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 hashed with PBKDF2; API keys for scripted integrations

The Respondr user administration screen, listing accounts with their roles and assigned channels.

03 — Evidence

Every transmission leaves a record.

Channel audio is recorded and searchable, and 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

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 Respondr history screen, showing recorded transmissions with their channel, time and duration, filtered by date.

The controls, one by one

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

TLS 1.3 everywhere

Every client and gateway connection is encrypted in transit. Voice and control traffic never cross the network in the clear, on any deployment model.

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.

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
On-premise	Your hardware, inside your network. Disks encrypted with LUKS / dm-crypt.
EU cloud	AWS Europe region (Milan). Volumes encrypted with EBS and KMS.
Hybrid	Radio gateways on site, Respondr Core in the cloud.
Transport	TLS 1.3 on every client and gateway connection, Nginx-terminated.

Standards and frameworks

Where Respondr sits against the frameworks European operators are assessed on. Read these as the posture the platform is engineered to, not as certificates held by a third party — if your procurement needs the evidence file, ask us in the demo and we will walk through it.

IEC 62443 SL2

Respondr is built to Security Level 2 of the industrial automation security standard: authenticated users, enforced access control, encrypted transport and an audit trail.

NIS2 alignment

The controls the directive expects of essential and important entities are implemented in the platform: strong authentication, access management, logging, and incident-relevant records.

GDPR data residency

Cloud deployments run in an AWS region you choose. For European operators that means European soil, with no transfer built into the product.

Operational continuity

Clients and gateways hold redundant server connections and fail over automatically, so a single fault does not take dispatch down.

Frequently asked questions

Respondr is engineered to IEC 62443 SL2 and aligned with NIS2. That is a design posture, not a certificate issued by a third party — we will not claim otherwise on a public page. What we can do is walk your security team through exactly which controls implement which requirement.

See Respondr on your networks.

A 30-minute live demo with your radio infrastructure in mind.

Schedule a demo Contact sales