What GoodCloud actually lets you do
GL.iNet describes GoodCloud as a platform to simplify the remote deployment and management of connected devices. Batch tools aim at fleets, but a single home or travel router can be bound too. The features below come from GL.iNet's firmware 4 GoodCloud page. [1]
The practical difference from Tailscale or a WireGuard server is scope. Those tools put your phone or laptop on your home network. GoodCloud is a management console for the router itself: you see and change the router, and site-to-site is a separate add-on feature. [1]
| Feature | What it does | Catch |
|---|---|---|
| Status monitoring | Online or offline state, live RAM use and load average | Read-only, so low risk [1] |
| Modify Settings | Change wireless, Ethernet, security, port forwarding, LAN and system settings remotely | A mistyped LAN or Wi-Fi change can cut off devices at home [1] |
| Remote GUI and Remote SSH | Open the router's web Admin Panel or terminal through the cloud | Must be enabled on the router; on 4.10+ they are on by default after binding [1] |
| Client management | View connected clients, watch live traffic, block a client | Useful for spotting an unknown device [1] |
| Email alarms | Alerts for online or offline changes, new connections and block events | Individual users get one alert rule [1] |
| Site-to-site | Join networks in different places, such as home cameras or a NAS | Set up separately; GL.iNet lists it as a Tailscale conflict [1][3] |
| Batch reboot and firmware upgrade | Act on many routers at once | Bulk features and multi-account management need paid plans [1] |
Binding: the steps change with firmware
Every path needs a GL.iNet account. The menu location and defaults depend on firmware, so check your version under the Admin Panel before following any tutorial. [1]
Firmware 4.10 is where the remote-access default changed. GL.iNet says remote access for the web Admin Panel and terminal is enabled by default after binding on 4.10 and later. On 4.7 to 4.9 you enable Remote SSH, Remote Web Access or View Logs yourself after binding. On 4.6 and earlier, you choose those options and a data server before applying. [1]
| Firmware | Where to start | How the router binds | Remote GUI and SSH |
|---|---|---|---|
| 4.10 and later | CLOUD SERVICE, GoodCloud, Get Started | Bind GL.iNet Account via URL, confirm Device ID, model and MAC on the GoodCloud site, name the router, click Bind; a verification email may follow | On by default after binding [1] |
| 4.7 to 4.9 | CLOUD SERVICE, GoodCloud, Get Started, Enable | Binds automatically after you log in or register | Off until you enable Remote SSH or Remote Web Access [1] |
| 4.6 and earlier | APPLICATIONS, GoodCloud | Toggle on, pick a data server, accept terms, Apply, then add the device on the GoodCloud site (Auto Discover, Manually Add or Bulk Import) | Optional toggles before Apply [1] |
What GoodCloud stores, according to GL.iNet
GL.iNet's GoodCloud page does not give a full list of collected data or retention periods. Read it alongside the company's privacy policy, which says it was last updated on September 18, 2026 and covers GoodCloud. [1][2]
The privacy policy names controllers in Hong Kong and in Fairfax, Virginia, and says data may move to China, the EEA and the US. It does not name server locations. On firmware 4.6 and earlier, the GoodCloud page lets you pick a data server in Japan, Oregon or Ireland; it does not describe a server choice for 4.7 and later. [1][2]
The policy lists advertising networks and partners among the parties data may be shared with in one section. Another section says GL.iNet does not share data for targeted advertising. The policy does not explain the difference, so treat the stricter reading with caution and use the opt-out rights it describes if this matters to you. [2]
- Binding details shown on the platform: Device ID, model, MAC address, serial number, username and binding time. [1]
- Router statistics, connected-client lists and live traffic monitoring visible in the dashboard. [1]
- Logs: Activity, Device, Upgrade, Alert and Device Settings logs, plus API call logs for remote access. [1]
- Policy-level usage data for GL.iNet and GoodCloud: device performance stats, browser, OS and device type, network speed and latency, language and time zone, login times, page visits, feature use and error logs. [2]
- Retention: the policy says data is processed only for the minimum period necessary for its stated purposes, then deleted or anonymized. It gives no specific period for device logs. [2]
The security trade-offs to weigh
Binding moves trust from your local network to an account. With Remote GUI or Remote SSH on, anyone who gets into your GL.iNet account can reach the router's admin interface from anywhere. That is the point of the feature, and also the risk. [1]
Two quieter details matter for travel routers. First, GoodCloud bypasses the router's VPN client by default, so management traffic leaves outside the tunnel unless you turn on Services from GL.iNet Use VPN. GL.iNet warns that this option may reduce stability. Second, individual users get one email alert rule, so choose the one event you most want to know about. [1]
- Keep Remote SSH off unless you use the router's terminal from away; GL.iNet shows a grayed-out Remote SSH when it is disabled on the router. [1]
- Use your one alert rule on the event you care most about, such as the router going offline or a new connection appearing. [1]
- Check the Activity and Device Settings logs after any trip to confirm nobody else changed settings. [1]
- Decide whether management traffic should follow your VPN before you travel, not after. [1]
- If you later add Tailscale on the same router, do not run GoodCloud Site to Site alongside it. [3]
How to turn it off or unbind
Disabling and unbinding are separate steps. Disabling stops the router talking to the cloud. Unbinding removes the router from your account. If you are selling or lending the router, do both. You can also remove the router from Bound Devices on the GoodCloud site, and GL.iNet says the router syncs that status automatically. [1]
| Firmware | Disable cloud | Unbind |
|---|---|---|
| 4.10 and later | Cloud icon, gear icon in the Cloud Service pop-up, Disable | CLOUD SERVICES, GL.iNet Account, Unbind [1] |
| 4.7 to 4.9 | Cloud icon, gear icon in the Cloud Service pop-up, Disable | Cloud icon, Unbind [1] |
| 4.6 and earlier | APPLICATIONS, GoodCloud, toggle off, Apply | APPLICATION, GoodCloud, Unbind [1] |
GoodCloud, Tailscale or a home WireGuard server
These overlap but answer different questions. Pick by what you need to reach, not by which is easiest to switch on. Our guides on Tailscale on a GL.iNet router and on running a WireGuard server on Flint 2 or Beryl AX cover the setup of the alternatives.
| Question | GoodCloud | Tailscale on the router | WireGuard server on the router |
|---|---|---|---|
| What you reach | The router's dashboard, Admin Panel and terminal | The LAN, if you advertise subnets, or an exit node [3] | The home network through a VPN tunnel [4] |
| Account involved | GL.iNet account [1] | Tailscale account; Personal plan free for up to 6 users [5] | None; you hold the keys [4] |
| Public IP needed | Not stated in GL.iNet's GoodCloud page | Not listed as a requirement in GL.iNet's Tailscale page [3] | Yes, GL.iNet says the router needs a public IP [4] |
| Known conflicts | Site to Site conflicts with Tailscale [3] | OpenVPN client, WireGuard client, GoodCloud Site to Site, ZeroTier, AstroWarp [3] | Port forwarding needed on any upstream router [4] |
Worked example: a fictional travel kit
Priya has a Flint 2 at home on firmware 4.10 or later and a Beryl AX in her bag. She bound the Flint 2 to GoodCloud to see whether it went offline during a power cut. Binding turned on remote web and terminal access by default. She never uses the terminal from away. GL.iNet's 4.10 instructions do not spell out where to switch Remote SSH back off, so she looks for the toggle on the router's GoodCloud page, then confirms in the GoodCloud dashboard that Remote SSH shows as grayed out. She uses her one alert rule for the Flint 2 going offline. [1]
For reaching her NAS, she uses Tailscale on the Flint 2 with Advertise LAN Subnets, approved in the Tailscale admin console. Because GL.iNet warns against running Tailscale with GoodCloud Site to Site, she does not turn site-to-site on. [3]
She never binds the Beryl AX. It is a travel router she can reset at a hotel desk, and there is nothing on it she needs to manage remotely. If she sells the Flint 2 later, she will unbind it under CLOUD SERVICES, GL.iNet Account and disable the cloud from the cloud icon before resetting it. [1]
Questions before you decide
Do I need GoodCloud to use a GL.iNet router?
No. GL.iNet's documentation describes GoodCloud as a service you switch on from the router's web Admin Panel and bind to a GL.iNet account, with separate Disable and Unbind steps for each firmware generation.
Does GoodCloud traffic go through my VPN client?
Not by default. GL.iNet says that when GoodCloud and the VPN client are both on, GoodCloud bypasses the VPN. An option called Services from GL.iNet Use VPN routes it through the tunnel, though GL.iNet warns this may reduce stability.
Can I run GoodCloud and Tailscale on the same router?
GL.iNet advises against running Tailscale alongside GoodCloud Site to Site, along with the OpenVPN client, WireGuard client, ZeroTier and AstroWarp, because of possible routing conflicts. Its Tailscale page does not list GoodCloud's basic remote management as a conflict.
What happens if I delete my GL.iNet account?
GL.iNet says account deletion permanently erases all related services, data and personal information, and cannot be recovered. It asks you to leave any organizations before deleting. Unbind your routers first so each device's cloud status is clean.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- GL.iNet Router Docs (firmware 4): GoodCloud Accessed 30 Oct 2026
- GL.iNet: Privacy Policy (last updated September 18, 2026) Accessed 30 Oct 2026
- GL.iNet Router Docs (firmware 4): Tailscale Accessed 30 Oct 2026
- GL.iNet Router Docs (firmware 4): WireGuard Server Accessed 30 Oct 2026
- Tailscale: Pricing Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.