Multiple researchers, one GPU workstation — collaborative access with individual accountability and no shared passwords circulating over email.
A university research group has one high-end GPU workstation for model training. Three PhD students need access. The current solution is a shared SSH password distributed over email — meaning any one of them can accidentally overwrite another's running job, and there is no way to tell who made which change when something goes wrong. When a student graduates or leaves the group, the shared password must be changed and redistributed. When two students try to run training jobs simultaneously, resource conflicts occur with no coordination mechanism in place.
A single shared SSH password means there is no way to determine who restarted a service, who terminated a running training job, or who modified a configuration file when something breaks.
When a student graduates or leaves the project, the shared password must be changed and re-distributed to every remaining team member — a process that is easy to forget and creates a recurring security gap.
awaBerry Anywhere's device sharing model gives each student their own authenticated access session — no shared passwords, no credential distribution over email. The device owner shares the workstation with each student's individual awaBerry account. Access can be granted and revoked instantly per person, providing both convenience and accountability.
awaBerry is deployed on the GPU workstation by the lab manager or device owner. One-time setup for the entire team's access lifecycle.
Each PhD student's awaBerry account is granted access individually. Access is revoked immediately when a student leaves the project — no password rotation, no re-distribution.
Students submit training jobs via SSH using their own individual sessions, with separate shell histories and complete audit trails — no shared password, no credential exposure.
A Web-to-Local tunnel to the local Jupyter server (port 8888) lets each student open their own notebooks in the browser without exposing Jupyter to the public internet.
One student monitors GPU utilization via a Web-to-Local tunnel to the local monitoring dashboard while another runs a training job via SSH — independently, without interfering with each other.
Shared research hardware should not mean shared credentials and shared accountability gaps. awaBerry Anywhere gives each team member their own secure, auditable access path — and gives the lab manager the ability to add or remove access in seconds, keeping the team agile and the workstation secure.
Industrial IoT deployments live or die by maintainability. awaBerry Anywhere replaces complex VPN infrastructure with a lightweight agent that turns every edge device into a first-class remotely manageable asset.
For young makers and students, the barrier between a working local project and a remotely accessible device has always been networking complexity. awaBerry Anywhere removes that barrier entirely — the focus stays on building, not on configuring firewalls.
Automate operations, manage fleets, and enable secure remote work for your entire team.
Access your home devices, automate personal tasks, and share access with family — for free.
Access lab hardware, automate data collection, and collaborate across institutions.