I have spent the better part of my career helping organisations bring innovative technology to market. And in conversations with IT leaders, security teams, and distributed workers across dozens of industries, the same frustration comes up over and over again: remote access is painful, risky, and expensive. It should not be.

The Problem with "Good Enough"

For years, VPNs have been "good enough." They work, mostly. They are familiar, mostly. And they are — frankly — a security nightmare that the industry has collectively agreed to ignore.

Think about what a VPN actually does: it grants broad network-level access to a user, often to an entire subnet, with minimal granularity. Once someone is on the VPN, they can typically reach hundreds of services they have no business accessing. A compromised VPN credential does not give an attacker access to one thing — it gives them access to everything on that network segment. We saw this play out in a series of high-profile breaches over the past few years, and yet the default answer for "we need remote access" is still "set up a VPN."

Open inbound firewall ports are equally problematic. Every open port is an attack surface. Every open port must be monitored, patched, and defended. For organisations with dozens of devices or locations, this becomes a full-time job in itself — and most teams simply do not have the bandwidth to do it properly.

Zero-Trust Is Not Just a Buzzword

Zero-trust remote access means something specific: no implicit trust, ever, for anyone or anything. Every connection is authenticated. Every action is scoped. Nothing is assumed to be safe by virtue of being on the "inside" of a network.

With awaBerry, your devices never expose inbound ports. The device agent establishes an outbound HTTPS connection to our relay infrastructure. To connect remotely, you authenticate through the awaBerry dashboard, receive a scoped access token, and tunnel through to exactly the service you need — and nothing else. Your firewall does not change. Your network topology does not change. You do not need to deploy VPN concentrators or manage complex access control lists.

What This Unlocks for Distributed Teams

When remote access is genuinely secure and genuinely simple, behaviour changes in ways that compound over time:

  • Engineers access development devices from anywhere without waiting for IT to configure VPN split tunnelling or whitelist their home IP address.
  • Support teams connect to customer systems in seconds — with a documented, auditable trail of exactly what they accessed and when.
  • Executives access their office desktops from a hotel lobby without asking IT to open a firewall rule that will inevitably be forgotten and left in place for years.
  • Onboarding new remote employees means adding them to the awaBerry dashboard, not submitting a ticket to configure VPN access, waiting three days, and hoping everything is right the first time.

The Future Is Borderless

The office is no longer a place. Your device fleet is global. Your workforce is distributed. The infrastructure that connects people to the tools they need should be as seamless and secure as the web itself — not a patchwork of legacy tunnelling protocols held together by institutional inertia.

awaBerry is built for how teams actually work today. If you are ready to leave the VPN era behind, start for free →