Set up a self-hosted device fleet.
Run Bonk's device fabric on infrastructure you control. A node shares connected Android and iOS devices with other members of the fabric, through the fabric's WireGuard network.
For rented hardware, use Bonk Cloud. Self-hosting starts with your own machines, devices, and network setup.
What you need
- A self-hosted Headscale control server and an appropriate access policy.
- A pre-auth key for each member; node keys use the
tag:bonk-nodetag. - Bonk on the development machine and the machine serving devices.
- Android devices attached to a node with adb access, or iOS devices paired with the node.
Bonk runs its own tailscaled in userspace networking mode. It does not need a network adapter or admin rights for that process, and it does not change an existing Tailscale installation. Provisioning your server, firewall, or device can require separate privileges.
Join the fabric
Get the server address and pre-auth key from your fabric administrator. Replace the example values before running:
bonk fabric join --login-server https://headscale.example.com --auth-key YOUR_KEY
bonk fabric status
The join command starts the background connection. After rebooting, use bonk fabric up. Use bonk fabric down to stop it.
Share devices from a node
Join the node using a key tagged for nodes, then serve its devices:
bonk fabric join --login-server https://headscale.example.com --auth-key NODE_KEY --hostname lab
bonk node serve
The node exposes a filtered adb proxy on port 5038, a device listing on port 5039 and a usbmuxd proxy for iOS devices on port 5041 through the fabric. The adb server itself is not exposed directly.
The fabric access policy lets users reach nodes on ports 5038, 5039, and 5041 only, so nodes aren't reachable over SSH through the fabric. Configure your policy before exposing a node, including restrictions on node-to-node and node-to-user access.
Use your remote hardware
bonk devices
bonk run --device lab/adb:SERIAL
bonk adb-bridge lab/adb:SERIAL
Local devices, and Windows, Linux and macOS devices paired with bonk pair, keep working without the fabric, over your local network. Remote Android devices support forwarded ports, but do not currently support adb reverse.
Keep a node running
The upstream guide includes a systemd user service for Linux, a launch daemon for macOS, and Task Scheduler instructions for Windows. Use --skip-update in unattended services so the updater does not wait for input. On SteamOS, use the systemd service so the node survives logout. The macOS launch daemon's local-network exemption remains untested upstream.
Read the complete device fabric guide for service files, networking, and operational details.