Connect your devices.
Reach your phone, laptop, or server over an encrypted connection. Go direct when possible; stay connected through a relay when needed.
Explore device connections
airmshIN PRACTICE
Five ways to connect and share. You choose which ones to use.
Reach your phone, laptop, or server over an encrypted connection. Go direct when possible; stay connected through a relay when needed.
Explore device connectionsGive approved people a private Endpoint for one internal website, Web API, database, or tool. Set access by user, group, or device. Other services stay private.
Explore scoped accessChoose a drive size that fits your storage plan. Give multiple people folder-level access.
Explore AirFSGive one local web service a public HTTPS link for a demo or callback. Public sharing is separate from your private network and can be turned off.
Explore public linksConnect named agents across devices. Each request is checked so the right agent can do only what you allow.
Explore trusted agentsGET STARTED
Download Airmsh for your computer or phone. Installing on a Linux server? The CLI installer can keep it running for you.
FAQ
Install Airmsh on your devices, sign in, and turn on your private network. Add Endpoints, drives, or agents only when you need them.
Airmsh can use a relay as a fallback. Both devices still need to be online and authorized to connect.
Create an Endpoint for that service, then choose which users, groups, or devices may reach it. Other services stay private.
Yes. AirFS lets you give multiple people folder-level access to a shared drive. Check the setup guide for current preview availability.
Yes. Name the agent on its destination device and allow the specific devices, actions, and resources it may use.
Yes. Install it through the App Store or Google Play, then allow the system VPN permission when asked. Check your installed version for feature availability.
Each person uses their own Airmsh account. Invite them in People & access, then grant access to the specific Endpoint or AirFS folder they need.
Check that its server is online, Endpoint access is connected, and you copied the full name and port from Endpoints. Then check the service on the server.
No. Your devices connect in a private network with identity and access checks. Public links are optional and separate from that network.
No. An Endpoint opens one selected service. It does not open other ports, Terminal, Files, or an entire subnet.
Yes. Allow the specific users, groups, or devices that need the service. Other access stays closed.
No. Drive and folder access are separate from Terminal and other files on the owner’s device.
Yes. Public links are separate from the private network and can be disabled or deleted.
New Endpoint connections should be blocked. Drive access changes may take a short time to expire, and files already copied cannot be recalled.
The destination checks the authenticated source device, target device ID, and agent tag. A network address alone is not accepted as identity.
No. Remote callers send requests; database passwords and MCP tokens stay on the destination device for local authentication.