Summary
A shell on a remote machine, opened without opening a port.
The usual price of letting an agent touch a remote box is SSH keys, a VPN or an exposed port. Here the device connects out through awaBerry and the session runs over that, so nothing on your side has to listen.
What it is
A remote-access server for machines enrolled in the awaBerry platform. Your client talks to awaBerry, awaBerry talks to the device, and the terminal session stays open across calls so state survives between commands.
What you get
- A connection to a named Mac, Linux, Windows or Docker device in your project, returning a session token and the device's status
- Terminal commands executed on that device inside one long-running session
- File management and database access on the connected machine over the same session
- Generated results written back to the device, not just read from it
- Demo credentials and a demo device, so the connection can be tried before anything of yours is enrolled
Requirements
An awaBerry account with at least one device registered to a project, plus that project's key and secret — supplied in the environment, or passed on the call. Node.js runs the server.