For newsrooms and field teams
Protect a whole team
Deploy GuardTalk across field staff with fleet provisioning, central monitoring, and shared threat intelligence — without a central point that can read anyone's messages.
Fleet provisioning
Deploy many devices, hold no one's keys.
Provision a fleet from one place: flash GuardTalkOS, pair gateways, and enrol devices on a repeatable path. The mechanism is centralised provisioning of configuration and policy; the limit is that provisioning never extends to message contents or to the keys each device holds — see the threat model.
Repeatable enrolment
A documented path to flash, pair, and enrol each device the same way, so a field team isn't assembling a system by hand.
Policy, not contents
Push configuration and security policy to the fleet. The keys that protect messages stay on each device, with the holder.
Separate custody
Gateways and biometric keys are distributed to staff so no single intercepted shipment carries a whole team's system.
Admin dashboard & companion app
Manage devices, never messages.
An administrator can see fleet posture — which devices are enrolled, which are up to date, which have flagged a threat. The mechanism is device-level telemetry and policy; the limit is firm and structural: there is no central point that can read anyone's messages, because the keys are not held centrally.
The companion app gives field staff the same posture view for their own device, so each person can confirm their protections are live without phoning an administrator.
What an admin can and cannot see
- Can see: enrolment, update status, device health, threat flags.
- Cannot see: message contents, contacts, or keys — by design, not by policy alone.
Threat intelligence
Shared defence, pushed and pulled.
When one device in a fleet sees a documented spyware pattern, the whole fleet can be hardened against it. The mechanism is distribution of indicators and detection rules; the limit is that a novel, well-resourced 0-day may evade signatures it has never seen — stated plainly in the threat model.
IOCs & rules
Indicators of compromise and Suricata detection rules for documented spyware families, pushed to deployed devices.
Blocklists
Known command-and-control endpoints and bad infrastructure, distributed to every gateway in the fleet.
Field signals
Devices report threat flags — never message contents — so a pattern seen once becomes defence for everyone.
Support & onboarding
Built for non-technical staff.
Field teams are not all engineers. Onboarding is structured for people who need protection, not a research project: guided setup, plain-language documentation, and a support path for the inevitable real-world question.
- Guided setup for each staff member, with verification taught as a first-class step.
- Plain-language docs covering daily use, duress procedures, and what to do on seizure.
- A support channel reachable privately, so questions don't force anyone onto an exposed surface.
Procurement note
Private payment in Monero: $300 per device one-time, plus $50 per device each month. The same minimal collection as individual access, and a kit that ships in separate parcels.
Availability is via the waiting list while the OS is in alpha, stated honestly rather than promised away.