I spend a lot of my time talking to enterprise IT teams about zero-trust security and CI/CD pipelines. But some of the most satisfying awaBerry stories come from much smaller stakes — and are no less illustrative of why the technology matters.
Let me tell you about Lisa.
The Raid Night That Went Wrong
Lisa hosts a World of Warcraft private server for her guild. Twenty-three people, a scheduled raid night, and — fifteen minutes before start time — the server goes unresponsive. Log files filling up. A plugin throwing errors she has never seen before. The chat channel filling with impatient messages from guildmates.
Lisa is a competent sysadmin, but she is not a World of Warcraft server expert. Her friend Jamie, however, absolutely is. Jamie has helped her before, but the usual approach — sharing SSH credentials, walking through firewall configuration over voice chat, hoping Jamie's home IP is not blocked — is slow, messy, and makes Lisa genuinely uncomfortable from a security standpoint. She does not want to hand over permanent SSH access to anyone, even a trusted friend.
With awaBerry, she had a better option.
Secure, Scoped Access in Under Two Minutes
Lisa opened the awaBerry dashboard and navigated to the Agentic API section. She created a new project, named it "Jamie — WoW Server Emergency," selected her server from her registered devices, and chose the Shared Device Access mode — which grants a guest direct access to the device using awaBerry's secure tunnel infrastructure, without requiring them to have an awaBerry account or any prior configuration.
Under the project settings, she enabled:
- Standard user terminal access (SSH via the awaBerry browser interface)
- Allow start/stop of Web-to-Local Ports — so Jamie could reach the server's management interface directly in a browser
She chose not to enable Remote Desktop — Jamie did not need the full graphical environment, just the terminal and the management web interface. She clicked Create Project, and the system generated a Project Key and Secret.
Lisa used the built-in email draft feature to send Jamie the credentials. Total time from "server is broken" to "Jamie has secure access": under two minutes. No firewall changes. No SSH key exchange. No VPN credentials.
Troubleshooting via Web-to-Local
Jamie received the Project Key and Secret and connected to Lisa's server using the awaBerry Connect client. Through the browser-based SSH terminal, he could inspect the log files, check running processes, and identify the conflicting plugin. But the more powerful tool for this particular problem was Web-to-Local.
The World of Warcraft server ran a lightweight admin web panel on a local port — a management interface that Lisa had never thought to expose publicly, and which had no authentication layer robust enough for internet exposure. With Web-to-Local, Jamie activated a tunnel through awaBerry and reached the admin panel directly in his browser, over an encrypted zero-trust channel, without that panel ever touching the public internet.
From the admin panel, Jamie could see the plugin load order, identify the conflict, disable the problematic plugin, and queue a clean server restart — all through the browser UI. The whole troubleshooting session took twelve minutes. The server came back online. The raid started twenty-seven minutes late, which is apparently not bad by guild standards.
When the Work Is Done
After the raid — and after profusely thanking Jamie — Lisa opened the awaBerry dashboard and deleted the project. Access terminated immediately. No credentials to revoke. No SSH keys to remove. No firewall rules to tidy up. The access Jamie had used for those twelve minutes ceased to exist.
The audit trail in the dashboard showed exactly what had happened: when Jamie connected, which commands were run, when Web-to-Local was activated, and when it was closed. Clean, complete, immediately available for review.
The Broader Pattern
Lisa's story is a gaming story, but the pattern it illustrates — securely granting a trusted person scoped, temporary access to troubleshoot a specific problem, then cleanly revoking it — applies across dozens of professional contexts. A software developer granting a contractor access to debug code on a specific device. A small business owner letting a support technician into a server to fix a configuration issue. A researcher sharing access to a compute node with a collaborating team.
The awaBerry Agentic API was designed for exactly this kind of access delegation: precise, auditable, time-bounded, and with instant revocation when the job is done. Total provisioning time under two minutes. Zero residual exposure after deletion.
No open ports. No VPN. Just secure, direct access — exactly as scoped as you need it to be, and gone the moment you choose. Explore the Agentic API →
