Field Users
Fast radio-style operation
Android-first PTT, roster, map, messages, call alerts, and dispatch video requests for mobile teams.
Product And Technical Documentation
Documentation for buyers who need to understand the product before trusting it in live operations.
Clear comms. Live control. One operation.
This page summarises the customer-facing product documents and the public technical posture. Detailed implementation docs, endpoint contracts, and deployment runbooks are reviewed in the right technical evaluation context.
Customer Overview
Secure Radio supports the roles needed to run a live communication workflow.
The platform is designed around field users, dispatch operators, tenant administrators, and operational stakeholders. Each role gets a surface that matches the work rather than forcing everyone into the same generic interface.
Dispatch
Control-room visibility
Browser dispatch for roster awareness, talkgroups, messages, live status, selected-unit context, and supervision.
Admin
Operational governance
Tenant structure, device and operator control, permissions, telemetry, and support visibility.
Stakeholders
Rollout confidence
A phased path from starter trial to Guided Evaluation, with clear ownership for operations, support, and administration.
Free Trial Mechanics
The free trial proves the core workflow without making the first setup heavy.
A verified trial request can automatically provision one dispatch console and one Android radio with mandatory operator authentication, one OPS channel, one OPS talkgroup, and time-limited access.
Email Verification
Confirm before provisioning
The trial starts only after the requester confirms their work email address.
Onboarding Email
Everything needed in one place
Dispatch setup, Android setup, Android app download, version, checksum, and basic instructions.
QR Activation
Separate setup codes by surface
Dispatch scans a dispatch QR. Android scans a radio QR. Each applies only the credentials intended for that surface.
Operator PIN
Chosen during onboarding
PINs are not sent by email. The operator chooses the PIN after scanning the setup QR, then uses it to log in.
Technical Evaluation
The public technical model is deliberately clear without exposing proprietary implementation details.
Control Plane
Identity, policy, signalling, and coordination
Device auth, operator auth, tenant policy, talkgroup state, dispatch requests, and runtime coordination are handled centrally.
Media Layer
Real-time voice and optional video
Media sessions are short-lived and tied to authenticated runtime state, with voice remaining the operational default.
Telemetry
Observable operation
Runtime health, connected clients, media state, and support-relevant events are surfaced for diagnosis and service review.
Status
Public service health
The website status page checks marketing delivery, product API health, trial onboarding storage, and Android release availability.