Devices you can send into the field — and trust

The moment one of our devices leaves for a customer site, it’s on its own. No one is watching the rack. It might sit unattended for months, on a network you don’t control, somewhere anyone could reach it. The field is where a device’s security is really tested — and it’s exactly where most devices are weakest.

So we design for the field first, not the lab. When you deploy an ASTRID POD, the point is that you can stop worrying about it.

What “the field” actually throws at a device

• Physical access. Someone can pick it up, open it, pull the storage, plug into it. A device that assumes it’s in a locked room is already beaten.
• Untrusted networks. It reports over whatever connection is available. That path has to be safe even when the network isn’t.
• Time. It runs for months without a visit. Whatever protects it has to keep working with nobody watching.

How the device is built to cope

These aren’t features on a datasheet — they’re the things that hold when the device is out of your sight.

• Secure boot. The device only runs software we signed. Nobody can swap a card or slip in modified firmware in the field and have it start. What you deployed is what keeps running.
• Encrypted storage. Its data and configuration are encrypted at rest, tied to that specific unit. Pull the storage out on site and it’s ciphertext, not a copy of your data walking out of the door.
• Per-device identity. Every unit carries its own keys, not a shared secret copied across the fleet. One compromised device on one site doesn’t hand over every other device you’ve deployed.
• Hardened reporting. Data comes home with the device’s identity attached, over channels built to resist tampering — so you can trust that a reading really came from that unit, on that site, at that time.

Match the hardware to the risk

POD Lite is the compact, low-cost platform for lighter-touch sites. It still handles credentials carefully and reports over hardened channels.

POD Pro adds the stronger assurances as standard — secure boot, encrypted storage and per-device keys — for demanding, regulated environments where a device in the field has to meet a real assessor’s questions.

The point: deploy with confidence

Sending equipment into the field is an act of trust. We build the security in so that trust is well-placed — so that when your devices are out there doing their job, the things that could go wrong have already been designed out.

We’re also honest about where we are: we’re actively building our formal security and cyber accreditations, and we’ll list each as it’s in place. If you have a specific assurance requirement for field deployment, ask us and we’ll tell you plainly where we stand today.