Home routers
Configure the exit once on a router that supports third-party firmware or a built-in client, and every device behind it is covered. Router CPU decides the throughput ceiling.
QuickQ on more devices · beyond phones and laptops
Some devices cannot run a client but can still use the QuickQ network. Two approaches cover almost every case: route the whole household through a router, or share the connection from a computer that is already connected. Below is what works per device type.
Setup by device type
Smart TVs and set-top boxes
Android TV systems install the Android client directly. Other systems are best served through a router-level exit.
Game consoles
Consoles have no native client. Use a router exit, or share the connection from a computer that is already connected.
Tablets
iPads and Android tablets install the matching client and occupy one device slot.
NAS and home servers
Any NAS with Docker can run the Linux client for offline downloads and remote access.
Dev machines and VMs
The Linux build ships as deb, rpm and AppImage, so it runs inside virtual machines and cloud instances.
Two general setup paths
Router-level exit
Configure the router once and everything behind it uses accelerated routes. Ideal for TVs, consoles and smart home gear that cannot install software.
Share from a computer
Turn a connected computer into a hotspot or bridge and attach the device to it. Good for temporary use with no router changes.
Check before you start
Router performance
Entry-level routers often manage only tens of Mbps of encrypted throughput, which caps the whole network.
Device slots
Three devices may be online at once. A router exit uses one slot but shares its bandwidth across the network.
Firmware risk
Flashing third-party firmware can brick hardware. Confirm the exact model and back up the stock image first.
Not sure whether your device can join? Send support the model and system version and we will reply with steps or an alternative.