Who's Actually Doing This, and Why
Across the conversations we have with people who reach out to HomeLink, a specific segment keeps showing up. Not the person planning a wine-country month in Portugal. Someone whose mother is in her seventies in Central America and whose sibling can't cover every appointment. Someone whose spouse is on a work visa in Karachi and can't come home for another eighteen months. Someone applying for a Digital Nomad Visa in Spain because the two-year residency clock is what leads to citizenship, and the passport is the point.
These are people with US jobs and US bank accounts and US tax obligations, who need to be somewhere else for a long time for a reason that has nothing to do with wanderlust. The framing is completely different from the lifestyle case. The person on a two-week vacation is optimizing for "don't get caught." The person on a two-year residency track is optimizing for "keep my job for the entire two years while I do this, without anyone getting nervous about how long I've been away."
The trigger for buying a tunneling setup is different too. The vacationer buys because they want to keep using Netflix and don't want their laptop to trip an employer alert during a specific known window. The long-stay person buys because they need a piece of infrastructure that will hold up for a year or more, through firmware updates, ISP outages, a home router replacement, and a partner or family member power-cycling equipment they didn't set up themselves. The failure mode of "the tunnel dropped for three hours on a Tuesday afternoon" is a bigger deal when it's month fourteen of a two-year stay and every dropped session is another line item in the pattern.
What Long-Term Stays Actually Break
On a two-week trip, most of the failure modes never show up. The home router doesn't get rebooted. The ISP doesn't rotate your public IP. Your laptop timezone drift doesn't accumulate. You aren't around long enough for any of it to matter. On a stay measured in months, those same things start compounding.
First, home internet reliability while you're gone stops being a background concern and becomes an active risk. Comcast or Spectrum or whoever provides the connection at your US address will have outages. They will push firmware updates that reboot the modem. They will do maintenance windows that drop the connection for six hours in the middle of the night. On a two-week trip you can just wait for it to come back. On a two-year stay you need either a person at home who can power-cycle things, or a setup that self-heals hard enough that they don't have to.
Second, the WiFi network you're operating on changes more often than you expect. Long-stay people usually don't sit in one Airbnb the whole time. They move between a family member's house, a coworking space, sometimes a longer-term apartment lease, sometimes back to a hospital-adjacent hotel for a rough week. Each network has its own captive portal, its own MTU quirks, its own firewall behavior. A setup that works at one address on day one might struggle at the next address six weeks later. Hotel captive portals aren't the problem anymore because you're not in hotels. Institutional networks (hospitals, university guest WiFi, government offices) are the ones that bite.
Third, the detection-window problem inverts. On a two-week trip, your employer's SIEM might not even catch a location anomaly before you're back. The impossible-travel rules average out. Nobody generates a quarterly review of a single-week signal. Over months, the signal has time to become a pattern. Every login gets logged. Every chart access gets logged. Every calendar invite gets stamped. What was noise at two weeks becomes signal at six months. The deep dive on how IT departments track remote workers covers the mechanics of that; the shift over time is what changes for long stays specifically.
Fourth, metadata drift. Slack, Google Calendar, Outlook, and every other work app slowly leaks the timezone your device thinks it's in. Small mismatches that would go unnoticed for a week or two become visible patterns over months. A calendar that consistently accepts meetings at times that would be 3am in your supposed home city, a Slack profile that shows your active hours shifted by nine, a Zoom account whose stored settings drift toward the local time zone every time you sign in from a new device. Any one of those in isolation is nothing. Stacked over six months, they start to add up. The timezone-apps breakdown gets into the per-app specifics.
Fifth, dynamic IP handling on the home side. Most residential ISPs give you a public IP that stays the same for months at a time, then quietly rotates it during a lease renewal or modem reboot. On a two-week trip you can ignore this. On a long stay your tunnel either handles IP changes automatically or somebody at home has to update a config file. Every DIY setup we see abandoned around month three fails at exactly this point. The person at home didn't sign up to be the SRE.
HR, Tax, and the "Occasional Remote" Window
The technical side is only one half of a long stay. The other half is the employer relationship, and it works differently when the stay is long enough that "I'm just working from a friend's place for a bit" stops being a plausible cover story.
Most US employers have a policy, written or unwritten, about occasional remote work outside the US. Sometimes it's an explicit "up to X days per year." Sometimes it's an unwritten understanding that the trip is fine as long as it stays inside a reasonable window. The two-year residency case blows through both of those. Once you're crossing the line from "occasional" into what HR would think of as "permanent relocation," the reasonable-notice policies actually start to matter. Some employers don't care as long as the work happens. Some care a lot because their tax exposure and their employment-of-record obligations change once an employee is really living somewhere else for real.
This isn't a guide on how to hide a long stay from HR. It's an article about the setup for long stays, and the honest version of that setup starts with knowing where your employer's line actually sits. Some people can just have the conversation and get formal approval. Some are in industries where the answer would be "no" but the practical reality is that nobody would ever detect it if the network setup holds. Some are in the middle, where the answer would be "we don't have a policy for this, please don't force us to write one." Knowing which of those three you're in is the piece that decides how much technical work you actually need to do.
The tax and visa questions are real and this article is not the place to answer either. If you're outside the US more than six months a year, you may create a tax nexus in the country you're in. Some countries have digital-nomad regimes that make this easier. Some have exactly the opposite. The money you'd spend on a tax attorney who knows the specific bilateral treaty is money that pays for itself, and no router setup substitutes for that conversation. Same with visa. The immigration attorney in the destination country has answers this article cannot provide. The technical piece is the smaller half of a long stay, not the bigger one.
Three Common Patterns from Our Customer Base
Rather than invent hypothetical characters, here are three patterns we actually see recurring in the people who reach out. Each one has a different center of gravity, and the setup work that matters most is different for each.
Healthcare Consulting, Parents in Central America
The parent is in their seventies. There's a sibling in the country who covers most days but not the medical appointments and not the paperwork. This person has a US healthcare consulting job that would in principle allow remote work but has never officially allowed remote work from outside the US. The realistic plan is somewhere between eight months and eighteen months of being physically in Guatemala or Honduras or Costa Rica while keeping the US role.
What matters most in this setup: reliability of the tunnel over long stretches (an outage during a call with a US-based client is a real problem, not a theoretical one), a clean residential IP that reads to the corporate SSO stack as "home," and a fallback plan for the weeks when the parent is in the hospital and this person is not near stable internet at all. The setup has to be resilient not just to network flakiness but to a family emergency that makes them unavailable to fix anything for a few days.
Chasing EU Citizenship on a Two-Year Track
The visa program (Spain's Digital Nomad Visa, Portugal's D7, Italy's various options) requires physical presence in-country for a defined number of days per year to keep the residency clock ticking. Two years of that clock gets you to permanent residency. Five gets you to citizenship. The person has a US job that pays enough to satisfy the visa's minimum income requirement, and the setup problem is keeping that job for the entire clock.
What matters most here: consistency over a very long period. The employer isn't going to detect anything in month one or month three. What generates risk is the pattern that shows up in month fifteen when an IT quarterly review pulls a report on egress-IP distributions per employee, and one employee's numbers look weird. The fix is to make sure the numbers don't look weird, month after month, without any manual intervention required. This is the population that benefits most from a setup that just works and stays working without them thinking about it.
Spouse on a Different Continent
The other spouse is on a work visa or family visa in Karachi, Manila, Lagos, Mumbai, wherever. Coming back to the US isn't practical for the next eighteen months. The US-based spouse can't take unpaid leave for the whole window without losing the job. The plan is to be with the other spouse for extended blocks (three months, four months, sometimes longer) while keeping the US job intact.
What matters most here: the tunneling infrastructure has to work with the specific network conditions of the destination country. Pakistan's ISPs treat traffic differently than Spain's. Some countries block UDP on non-standard ports. Some have periodic government-level throttling that catches VPN traffic. The setup that works effortlessly in Portugal might struggle in a country whose ISPs are more aggressive about traffic classification. This is the population where the honest answer sometimes is "yes, we can make this work, and you should also plan for occasional degraded periods that no setup will solve completely."
None of these three are lifestyle nomads. Each of them is going to be somewhere for a reason that would still exist even if the work-from-anywhere movement had never happened. The technical setup exists to protect the US job that pays for the family situation to happen. That's the frame the guide is written in.
What to Actually Plan for Before a Long Stay
For a stay measured in months to years, the pre-departure planning is more involved than a vacation, but not by as much as people think. The pieces that matter are the ones that can't be fixed once you're already there.
Someone at home who can power-cycle
Not every setup requires this, and any setup worth using tries to self-recover before asking. But some outages are physical. A modem that lost its config. A router that took a bad firmware update. A neighborhood ISP outage that resolved itself but left one device in a stuck state. Having a person who can walk over and unplug the modem for thirty seconds is worth more than any amount of clever software recovery. This person doesn't have to be technical. They just have to be reachable and willing to do the one thing.
Dynamic IP handling on the home side
If your setup depends on the home IP staying the same, you need to know what happens when it changes. Most residential ISPs will change your public IP eventually. Some do it every few months. Some do it on modem reboot. The tunnel needs to either use a coordinating relay that hides the home IP change from the travel side, or it needs a dynamic DNS setup that updates automatically. Anything that requires manual intervention to fix a routine IP rotation will fail on a long stay, guaranteed.
Firmware update behavior
Any router that stays plugged in for a year is going to get pushed a firmware update at some point. Sometimes those updates are silent. Sometimes they wipe custom configuration. Sometimes they change the WireGuard behavior in a way that requires a reconnect. A setup that survives firmware updates without human intervention is much more valuable than one that requires the person at home to know how to reload a config file after every update cycle.
Timezone metadata drift
Lock your operating system timezone to your US home timezone before you leave, and turn off automatic timezone detection. Do the same in the browser, in Slack, in Google Calendar, in Outlook. Every few weeks, spot-check that nothing has drifted. The specifics are covered in the timezone-apps guide and the location bubble overview. On a long stay this is the kind of thing that quietly regresses because a system update reset a preference, and by the time you notice, three months of meetings have been stamped with the wrong metadata.
Employer-side clarity, however you get it
Formal approval, informal understanding, or neither. Know which of those you have before you go. If neither, know what your fallback plan is if the situation surfaces. This is the piece that most technical people underweight because it isn't fixable with a tool. It's fixable with a conversation, or with a decision to not have the conversation and accept the specific risk that comes with that.
Local network unpredictability
Whatever specific country you're going to, the ISP behavior there will be its own thing. If it's Spain or Portugal or Mexico, most tunneling setups work fine. If it's Pakistan or the UAE or Saudi Arabia, the answer is nuanced and depends on which ISP you end up with and what transport protocol your tunnel uses. Do a small amount of research on the specific country before you leave, because "does WireGuard work here" is a question worth answering in advance.
Where HomeLink Fits and What It Doesn't Do
HomeLink is a pair of small routers, one that lives at your US address and one that goes with you. Every device you connect to the travel router routes through the home router before exiting to the internet. From your employer's perspective, the egress traffic looks like it came from your actual home residential connection on your actual residential ISP, because that's exactly what happened. There's no commercial VPN ASN in the middle, no mesh to bootstrap, no software to install on your work laptop.
For long stays specifically, three things about the setup matter more than they would for a vacation. The tunnel self-heals across firmware updates. The home router doesn't need a technical person to configure it (it arrives pre-configured and just needs power and ethernet at the US address). And the dynamic IP handling is done at the coordinating relay layer, so a change in the home ISP's public IP doesn't require any action at either end.
What HomeLink does not do: visa advice, tax advice, or endpoint control on an employer-managed laptop. If you're on a company-issued device with MDM software, the device itself can report its WiFi-derived geolocation back to your employer regardless of what network you're on, and no router-level setup addresses that. The location bubble guide is honest about that gap. HomeLink covers the network layer and the metadata layer that flows through it. The device layer is a separate conversation and sometimes a device-level answer.
The other thing HomeLink does not do is give you legal protection. If your employer's policy prohibits work from outside the US and you do it anyway, HomeLink doesn't change the policy or your exposure to the policy. What it changes is the technical footprint that would otherwise generate the detection event. Whether you should be relying on that footprint holding, given your specific situation, is a decision that involves more than the technical picture.
How Long-Stay Setups Usually Land
Across the long-stay conversations we've had, a common arc shows up. The person figures out early that a commercial VPN is not going to work, either because it exits on a datacenter ASN that any modern conditional-access policy flags, or because they tried it on a shorter trip and had login issues. They spend a while looking at Tailscale, hit either the bootstrap problem or the "who maintains the home node" problem, and start looking for something more hands-off.
By the time they reach out, they're usually not asking about network protocols. They're asking whether the setup will still be working in month twelve. That's a different question than a lifestyle nomad asks, and the answer involves less technical detail and more operational detail. Does the router self-recover from a firmware update. What happens if the home ISP rotates the public IP while the person at the US address is asleep. What happens in a country whose ISPs are aggressive about VPN detection.
The conversations usually end with a plan sketch: the router setup plus a small amount of employer-side hygiene, plus country-specific research on ISPs, plus contact info for whoever is going to power-cycle if needed. Not a purchase decision so much as a plan decision. The people who buy HomeLink for a long stay are usually the ones who worked through that plan first and found the router setup to be the least fragile part of the picture.
If You're Planning a Long Stay for the Right Reasons
Family, citizenship, and spouse-on-a-different-continent are legitimate reasons to be abroad for long stretches. The technical setup that makes it possible is one piece of a plan that includes conversations with your employer, an attorney, and probably a tax professional. The technical piece by itself doesn't solve the other pieces, and the other pieces by themselves don't survive a network layer that quietly breaks in month nine.
If you want to walk through your specific situation, Link (the agent on this page) can talk through what your network layer needs to hold, given your destination country and how long you plan to be there. Most of those conversations end with a plan sketch rather than a sale. If HomeLink is the right fit, we offer a 30-day free trial so you can validate the setup on a shorter stay before you commit to it for the long one. If you want to set it up with a human on the other end, Christian personally handles setup handoffs for the first month for anyone who wants it. No script. Just a conversation about what you're actually trying to do.
For the broader context on what a US employer's IT actually detects, the deep dive on remote-worker tracking covers the systems side. For the full-stack view of what has to line up in a long-stay setup, the location bubble overview ties network, OS, device, and MDM together as one model.
📋 Get the Pre-Travel Checklist
Every check from this guide, in one printable PDF.
Built for stays that outlast a vacation
HomeLink ships pre-configured. Plug the home node in at your US address, take the travel router with you, every device routes through home for as long as you need it to. 30-day free trial, personal setup handoff.