RF To Secure Radio
DMR traffic can appear inside dispatch and Android
A configured RF gateway publishes decoded radio audio into the same controlled media room as Secure Radio clients.
Platform
We built Secure Radio so the field team, the dispatch desk, and the admin owner can work from one connected system.
Clear comms. Live control. One operation.
Our view is simple: live communication only works well when the people speaking, the people coordinating, and the people governing the system are all properly supported.
Field voice
Dispatch control
Admin structure
QR onboarding
Operational telemetry
Optional live field video
DMR gateway interop
DMR Gateway Interoperability
Secure Radio can now bridge a configured DMR talkgroup into the same operational workflow.
This matters for teams that already have radio users but want browser dispatch, PoC handsets, identity-aware access, location, messaging, telemetry, and video request around the same live operation. It is especially relevant for remote sites, disaster recovery, temporary operations, and gateways connected back to the internet by LTE, Wi-Fi, broadband, or satellite.
Secure Radio To RF
PoC users can key the radio route when authorized
Secure Radio talkgroup TX can be routed to DMR through a gateway job governed by tenant and operator policy.
Operator UX
Clear wait and talk cues reduce clipped first words
Clients show RF keying and talk-now states so operators know when the radio side is ready.
Governance
Interop stays scoped to named talkgroups
DMR bridging is configured per gateway route, not as an uncontrolled open patch.
DMR interoperability is a guided module, not a standard self-service trial feature. It requires suitable RF licensing, gateway hardware, backhaul planning, coverage planning, audio tuning, and agreed operating procedure. It carries a recurring per-gateway module fee, typically from £250 per configured DMR gateway per month on annual terms; radios, RF estate, gateway hardware, and connectivity costs are separate unless agreed.
Provisioning Experience
New users can start from QR setup instead of manually copying credentials.
The free trial flow now provisions a small tenant and produces separate short-lived setup codes for dispatch and Android. Each client scans its own QR, receives the right device identity invisibly, and asks the operator to set a PIN during onboarding.
Dispatch Setup
Scan from the browser console
The dispatch login screen can scan or redeem the setup code, apply the device credentials, and prompt for the dispatch operator PIN.
Android Setup
Scan from the radio login screen
The Android app opens the camera from login, reads the setup QR, applies the radio identity, and asks the field operator to choose a PIN.
Security Model
PINs are not sent by email
Setup links are short-lived. Operator PINs are set during activation and stored server-side as hashes, not returned to the client.
Customer Trust
Android download includes version and checksum
The onboarding email and trial-ready page include a stable Android download link, app version, and SHA-256 checksum.
Compatibility
Choose the surface that fits the role and the moment.
We do not believe every user needs the same interface. Dispatch and admin work best in the browser. Field users work best in a native Android app. Lighter mobile access can still be useful on any phone, over Wi-Fi or LTE, when someone needs to step into the workflow away from a desk.
Dispatch
Best in modern desktop browsers
Dispatch and control workflows are best suited to current Chrome and Edge on desktop, where operations teams typically work all day and need map-led coordination without another thick client.
Admin
Browser-based admin and telemetry
The admin surface runs in the browser too, which keeps configuration, exports, and service visibility accessible without another client install.
Native Android
The main field experience for live operational use
Our native Android client is where field users get the strongest push-to-talk experience, role-led access, and day-to-day confidence.
Generic Mobile Client
Useful on any phone when someone needs lighter access on the move
This is useful for duty managers, roving supervisors, temporary users, or backup access on any phone over Wi-Fi or LTE. It is helpful, but not our primary operating surface.
Surface 01
For field operators: a native Android app built for live work, not a repurposed collaboration tool.
Today, many mobile teams are piecing communication together with calls, chats, or basic walkie-talkie apps. We built our field app to remove that hesitation and give operators something that feels direct and dependable.
What This Solves
A dedicated field workflow on Android
Instead of bouncing between consumer apps, operators get a native field surface designed around secure access and operational voice.
- Direct push-to-talk behavior for live work
- Controlled access by operator and role
- QR setup from the login screen for trial and managed onboarding
- Designed to work as part of the wider operation
Why It Matters
Field confidence under pressure
When a team is moving, responding, or escalating, the tool needs to feel obvious. That is the standard we designed this surface to support.
Secure sign-in
Named operator access from the handset.
Roster visibility
Operators can see team state and channel context.
Secure messages
Text updates stay inside the field workflow.
Video request
Dispatch can ask for visual context deliberately.
Surface 02
For dispatch and supervision: a real command surface, not just another user seat.
One of the biggest gaps in generic tools is the dispatch role. We built this surface for supervisors and control rooms that need an active working view of the operation, and sometimes a live look from the field, not a workaround inside the same interface the field uses.
What Teams Use Today
Improvised command-and-control
Supervisors often end up coordinating from calls, message groups, or a limited app view that was not really designed for active command.
Why Use Ours Instead
Designed for control, visibility, and speed
- Browser-based dispatch surface with map context
- Roster, channels, live comms, and alerts in one workflow
- Optional live field video request when extra visual context matters
Surface 03
For operations leads and admins: keep structure and quality under control.
A rollout can look fine in the first demo and still become unmanageable later. We treat governance and service visibility as part of the platform because customers need more than a launch-day success.
What This Solves
Post-launch control
Admins and operations owners need to know who is on the system, how talkgroups and permissions are structured, and whether the live service is behaving well.
Why Use Ours Instead
Administration that supports real operations
- Define users, talkgroups, and access around the operation
- Visibility into runtime health, activity, and degradation
- Supports disciplined onboarding, support review, and exports
- Helps the system stay reliable as usage grows
Surface 04
For lighter access on the move: a generic mobile client that works on any phone.
Sometimes the right person is away from the desk, carrying a non-primary device, or only needs temporary access. We support that too. The point is flexibility, not pretending every phone should become the main operating surface.
Where It Helps
Useful for roving supervisors, duty managers, and occasional users
A generic mobile client can be helpful when someone needs situational awareness, a quick response path, or a way to stay involved while moving across site.
- Works on any phone through a lighter client experience
- Useful over Wi-Fi or LTE depending on where the user is
- Helpful for backup access or lighter supervision tasks
What It Is Not
Not a replacement for the dispatch desk or the main field app
We are careful about this distinction. The generic mobile client is there to extend access where useful, while the native Android app and browser dispatch surface still carry the heavier day-to-day workflow.
Flexible Access
The right surface depends on the role.
A control-room operator, a field user, and a duty manager away from the desk should not be forced into the same interface. Secure Radio gives each role a surface that matches the moment.
The Platform Difference
Why customers choose this over the usual alternatives.
Instead of calls
Reach the right group immediately
Not one-to-one by default, and not dependent on manually dialing the right person at the right moment.
Instead of chat groups
Built for live coordination
Operational voice, dispatch workflow, and role separation are treated as the core job, not an add-on.
Instead of thin app-only PTT
Supports the wider operation
Field users, dispatchers, and admins all have a proper place in the system.
Instead of heavy hardware-first stacks
Software-led and easier to evaluate
We let customers start with the workflow and add hardware selectively where it truly improves the operation.
Feature Areas
The product goes beyond voice by supporting the structure around the operation.
Operator Control
Named operator access when governance matters
Useful when the right person, not just the right device, should carry the permission and accountability.
Talkgroups
Communication grouped around the job
Support operational separation by function, team, and incident, with talkgroups and access defined by admins instead of improvised during live use.
Selective Calling
Pull one person into focus without flooding everyone else
Useful for redirecting one operator, clarifying a task, or escalating one role quickly while the wider channel stays clean.
Dispatch Escalation
Turn field updates into cleaner control-room decisions
Built for operations where the real pain is not just hearing the update, but getting the right supervisor or dispatcher to act on it fast.
Runtime Health
Telemetry for support and review
Admin and operations owners can review live quality, reliability, and service behavior as usage grows.
Live Field View
Optional video when voice is not enough
Where enabled, dispatch can request a live field view without turning the whole product into a video-first workflow.