When choosing a VPN router, start with the devices that need a shared connection—not the hardware. TVs and game consoles that can't easily run apps may benefit from a gateway for international services. If only your work computer needs a connection, a device app is usually simpler. A whole-home setup is about centralized management, not routing all traffic through a proxy.
The limits of whole-homeacceleration: coverage, network exits, and devices
A router-based setup handles eligible connections at your home network's gateway. Devices using that gateway may not need separate apps, but that won't improve their Wi-Fi signal. Weak signal through walls, wireless interference and access point placement still need to be addressed on your local network. You can adjust access point placement in a larger home; whether the gateway also handles proxy traffic is a separate decision.
“No app needed on every device” comes with a caveat: traffic must pass through the designated gateway and match its rules. Guest networks, separate subnets and devices using another gateway may not be covered. Devices also won't keep using your home gateway rules when you leave; you'll need another connection method on the go.
Web research, video streaming and remote work place different demands on a connection. Video needs consistent throughput, while interactive apps are sensitive to latency spikes. Routing every app through the same gateway can slow access to local services or interfere with a company network. Decide which devices and services need international routes before setting up whole-home coverage.
Compare setups: primary router, secondary gateway and device apps
| Setup | Best for | Trade-offs | How to revert |
|---|---|---|---|
| Device apps | Mostly computers and mobile devices, each with different needs | Each device needs its own configuration; some TVs and game consoles can't easily run apps | Turn off the app on that device without affecting anyone else |
| Routing through the primary router | Many stationary devices and a preference for centralized rule management | Gateway issues can affect the whole network; performance and firmware compatibility matter | Disable the proxy rules to restore the original route |
| Separate secondary gateway | Keep the current primary router and try the setup with selected devices first | More complex gateway, return routing and DNS configuration | Restore the test device's gateway and DNS settings to their original values |
| Separate network segments | Keep everyday home devices separate from devices used for international services | Network equipment must support the required subnets or routing policies | Move devices back to the original network, checking access permissions between segments |
A secondary gateway isn't a plug-and-play box that automatically speeds things up. Devices must send the relevant traffic through it, and the return route must also be correct. Misconfiguration can cause intermittent connections, DNS failures or routing loops. If you're unfamiliar with gateways and address assignment, test with selected devices first rather than changing the network settings for the whole household.
Network segmentation can reduce unwanted impact, but different Wi-Fi names don't automatically mean different routes. Separate routing depends on the actual subnets, gateways and policies. If a work device already uses a remote access app, follow your organization's requirements and don't route work traffic through a home proxy without permission.
Hardware and subscription compatibility: check before replacing anything
Consider processing power and maintenance
Wi-Fi specifications don't tell you how well a router can handle encrypted traffic. A gateway processes protocols, connection state, DNS and routing rules; performance depends on the processor, available memory, cooling and software implementation. Look for tests that match your protocol, firmware and connection method. A router's advertised Wi-Fi speed alone can't tell you its proxy throughput.
Check whether the exact model and hardware revision are supported by the firmware, whether you can back up the configuration and how to recover if something goes wrong. Flashing firmware can make a device unusable and may affect its warranty. If you don't want the maintenance overhead, keep your existing router and use device apps instead of rebuilding your whole network.
A VPN menu doesn't mean you can import a subscription
Traditional VPN settings and proxy subscriptions use different formats. A subscription may include protocol details for Shadowsocks, VMess, Trojan or VLESS; Hysteria2 and TUIC also require compatible transport support. Whether a client can use them depends on its core, version and supported configuration fields. Seeing a protocol name in the interface doesn't mean every optional parameter is supported.
Check whether your router software accepts a node subscription, a full configuration or another import format, then compare it with what the service provides. Seeing server names only confirms that some information was read; it doesn't mean DNS, routing rules and the connection are working. Check VPNUrban's guides or support responses for compatibility with a specific router and firmware—don't assume that support in a desktop app guarantees router compatibility.
Routing and DNS: send the right traffic through the right route
Most home networks work best with split routing: keep local network traffic local, connect directly to everyday local services and use the appropriate route for services accessed internationally. This isn't a list you can import and forget. An app may rely on different domains for login, images and media. Routing only some of them can leave a page open while its content fails to load.
DNS translates domain names into addresses, so its resolution path needs to be part of the setup. Forwarding an app's connection while sending its DNS queries to an unsuitable resolver may expose those queries or return inappropriate addresses. However, seeing a local resolver on a test page doesn't necessarily mean there's a leak: if the rules are meant to route local services directly, that result may be expected. Check the result against your intended policy, not just the resolver's location.
A browser's encrypted DNS may bypass the resolver configured on the gateway. IPv6 traffic may also use the original route if it isn't included in the policy. Confirm that your software fully supports the relevant traffic and check the actual routes. Don't assume everything is configured correctly just because a webpage loads, and don't disable network-wide features without understanding the impact.
Server labels aren't a substitute for testing, either. Direct connections, relays and IEPL dedicated lines describe different routing arrangements: relays forward traffic through intermediate nodes, while IEPL refers to a dedicated transport network. None guarantees that a particular app will work or eliminates home Wi-Fi congestion or server-side restrictions. Test the route with the service you want to use instead of choosing by label alone.
Setup steps: test with a few devices before expanding coverage
- Record your current network settings. Save the primary router configuration and note the current gateway, DNS and address assignment method. Know how to restore the original network before making changes.
- Test the subscription first. Import it into a supported device app, refresh the server list and test the services you need. Accessing the subscription requires signing in; rule out account status, traffic allowance and subscription format issues first.
- Check gateway compatibility. Make sure the firmware, core and subscription format are compatible. Import the subscription and check for errors before proceeding. Don't replace the primary router before confirming compatibility.
- Connect a test device. Route only the test device through the new gateway. Check local network access, target websites, video playback and access to other devices on your network. Verify that DNS and the actual route match your rules.
- Test rollback and recovery. Disable the proxy and confirm that everyday network access returns. Then check that the rules still work after a restart and subscription update. Save the verified configuration.
- Expand gradually. Add devices that need the setup and observe performance when they're in use at the same time. Keep a clear direct route available so a failure doesn't leave the whole household without normal internet access.
Client apps and configuration permissions differ across Windows, macOS, iOS, Android and Linux. You can't simply apply desktop instructions to a router. VPNUrban's clients for other platforms are available after signing in; the iOS download link also requires an active plan. Platform support doesn't guarantee compatibility with every router firmware. See the Guides to check what's covered.
Troubleshooting and costs: diagnose the issue before deciding whether to keep the setup
If no one in the household can connect, disable the proxy first and check the broadband connection, local gateway and DNS. If only the test device is affected, check its network settings. If device apps work but the router setup doesn't, focus on core compatibility, routing rules and DNS. If only a particular service fails, check the route, its domain rules and the service's own restrictions. Avoid repeatedly resetting the entire network.
If speeds fluctuate, compare wired and Wi-Fi connections first, then check whether simultaneous use is straining the gateway. If the setup stops working after a subscription update, check the error log and any changed fields—but remove credentials before sharing logs. For help, use Troubleshooting to describe the issue and share configuration details without sensitive information.
Factor in hardware, maintenance time and data usage. VPNUrban monthly plans cost ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data resets monthly on the activation date; mid-cycle upgrades are prorated for the remaining days. Data packs cost ¥158/300GB, ¥358/1000GB and ¥658/3000GB; they last until used and never expire. See the Plans page for details.
No device limit doesn't mean unlimited data, and it doesn't mean a home gateway has unlimited processing capacity. Devices routed through the proxy share the plan's data allowance; background updates and video playback count too. The service offers 110+ countries and 170+ routes, but access still needs to be tested for the destination service. You can request a full refund within 7 days of your first payment, no questions asked.
- ✅ You have stationary devices that can't easily run apps and are willing to maintain a gateway: test the setup with a few devices.
- ✅ Your Wi-Fi coverage is already reliable and you only need a shared route for selected services: adjust the routing policy before replacing Wi-Fi equipment.
- ❌ Only your work computer needs a connection, or you often travel with your devices: apps are easier to manage.
- ❌ You don't want to maintain the network and have no clear rollback plan: leave the primary router as it is for now.