The frustration that started awaBerry was embarrassingly simple: I couldn't SSH into my own computer from outside my home network without punching a hole in my firewall or expensive remote desktop software. Every solution I found required either a VPN, a cloud relay I didn't control, or exposing a port to the public internet. None of those felt acceptable for devices I was deploying in the field. So we started with one core constraint: the device must never have an open port. Everything — SSH, remote desktop, file transfer, database tunnels — had to work through an outbound-only encrypted tunnel the device initiates itself. That became our zero-trust foundation. The problem got harder when we started deploying to SoC hardware. Setting up a fresh Raspberry Pi in a remote location meant someone had to be physically present with a monitor and keyboard. We built the Bespoke Installer to solve that: a cloud-compiled OS image with awaBerry Connect and your WiFi credentials pre-baked in. Flash it, power it on, it phones home. True zero-touch deployment. The biggest evolution was realising that remote access is only half the story. Once you can reliably reach any device, you want to automate things across your fleet. That led us to build the Agentic API and MCP server — so AI agents (Claude, GPT, Gemini) can programmatically control your devices, execute tasks, read sensor data, and orchestrate workflows, all through the same zero-trust tunnel. No new attack surface. No new credentials to manage. We built awaBerry for the maker who installs a Pi in a remote greenhouse, the developer who needs to reach a staging server at 2am, the IT team managing a fleet of edge devices they've never physically touched. The common thread: they all need access without compromise.

awaberry

Control and automate devices - zero-trust, no VPN & inbound

Control and automate devices - zero-trust, no VPN & inbound