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.
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.
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.
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.
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
Multi-factor authentication
Account lockout
OIDC single sign-on
Per-resource permissions
Audit logging
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
NIS2 alignment
GDPR data residency
Operational continuity
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.
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.
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.
Yes. Respondr connects to external identity providers over OIDC, configured per organization, so accounts are created and removed where you already manage them.
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.
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.
See Respondr on your networks.
A 30-minute live demo with your radio infrastructure in mind.