What do you actually do when the file you need is sitting on a machine three states away, and the only way to reach it is either a clunky cloud sync or drilling a hole straight through your router into the public internet? That question is what sent me down the NordVPN Meshnet rabbit hole in the first place, not long after my employer disclosed a third-party data breach — the kind of notice that makes you spend a Saturday reading AES-256 whitepapers instead of touching grass. I've tested more VPN subscriptions than I'd like to admit trying to answer file sharing and network security questions like that one, and the mesh networking approach NordVPN ships under the name Meshnet is the one I keep coming back to for remote access between my own machines.
Since then, the same handful of questions keeps landing in my inbox and in VPN subreddits: how this is actually different from a regular VPN, how many devices it can realistically hold, whether it's safe to hand a file share off to someone who isn't technical, and where it quietly breaks down. I'll answer those one at a time, with the parts that worked and the one thing that very much didn't. This isn't a full review of the provider — I've covered that ground with the NordVPN [Editor's Pick] link elsewhere — it's specifically about setting Meshnet up for file access without opening yourself to strangers.
What Actually Makes Meshnet Different From a Normal VPN Connection?
Most people picture a VPN as a way to borrow a foreign IP address and call it a day. Meshnet isn't that. It's a point-to-point network built on NordLynx, Nord's own implementation of WireGuard, and instead of routing your laptop through a data center it connects your laptop directly to your home machine. There's no central relay sitting in the middle, and it still works when both ends sit behind separate NAT firewalls — which is normally the whole reason people resort to port forwarding, poking a hole through the router for the entire internet to find, in the first place.
My friend Ezra — a backend engineer who used to sit two desks over before he left for a company in SoMa — cares about latency more than almost anyone else I know, and he's the one who pushed me to actually benchmark this instead of trusting the marketing page. The number that surprised me was the overhead: NordLynx doesn't carry the usual 20 to 30 percent speed penalty you get with older protocols, so reaching a home server over Meshnet feels close to local even from across town. I've run longer protocol comparisons before — the 30-day speed test results cover that in more depth — but for this specific point-to-point case, Meshnet held up better than any relay-based remote access tool I've tried.
How Many Devices Can You Actually Connect?
NordVPN caps Meshnet at 60 devices total, split into 10 personal devices tied to your own account and up to 50 external devices belonging to other NordVPN users you invite. Ten personal slots covers a full setup without much strain — a workstation, a laptop, a phone, a tablet, a media server — and the external slots are what make it useful for anyone outside your own household. If you need one static address instead of a flexible mesh, say for hosting something that has to stay reachable at a fixed point, that's a different problem, and it's worth reading about dedicated IP addresses for remote access before assuming Meshnet is the right fit.
Setup itself feels closer to pairing a Bluetooth speaker than configuring a VPN server: toggle Meshnet on in the NordVPN app on both devices, and each one gets a Nord-assigned name and an internal address automatically. I didn't have to touch my router's firewall rules or worry about my ISP handing me a new dynamic address overnight — the connection just re-establishes on its own. Traffic between the two ends is encrypted the entire way, so even though it technically crosses the open internet, nobody sniffing a shared network sees anything usable.
Secure File Sharing With Someone Who Isn't as Paranoid as You Are
My partner tolerates my home network the way you'd tolerate a roommate's aquarium — mildly, and with regular commentary about how many blinking lights one apartment needs. That tolerance got tested on a trip out of town, when we needed to pull photos off our local NAS, the one that isn't backed up to any cloud service. Inviting them onto the Meshnet took one step: an invite sent from my dashboard to their NordVPN account, accepted on their phone, and suddenly they could grab full-resolution images as if we were both on the couch.
Waverly — a regular in the VPN subreddit I help moderate, the kind of commenter who documents her test conditions better than most published reviews — asked me the version of this question that actually matters: is inviting someone onto your Meshnet safe if they're not technical, and does the connection hold up over home Wi-Fi instead of a wired one? Short answer: yes to both, with one caveat. The link itself performs the same whether it's Wi-Fi or ethernet, no meaningful difference in my testing, but "safe" only covers the tunnel, not whatever you're sharing at the other end of it.
If you're setting this up for a whole household rather than one partner, Surfshark [Budget Pick] is worth a look since it doesn't cap simultaneous devices, but for this specific point-to-point file scenario, Meshnet's workflow still beats anything relay-based that I've tested.
The Security Hole Nobody Mentions in the Marketing
That caveat is worth spelling out, because it's the part every glossy VPN landing page skips. Meshnet gives you an encrypted tunnel, but if you use it to reach a local file share that has no password because "it's only on the local network," you're betting your entire setup on your NordVPN login and nothing else. A compromised login stops being an inconvenience and becomes a direct, unauthenticated path to your files; an encrypted tunnel doesn't matter if the door at the other end was never locked.
I learned that the annoying way, not through Meshnet but through DNS. For a while I enabled DNS-over-HTTPS in Firefox and assumed that alone was enough to keep my requests private; it wasn't, and checking properly later showed how much was still leaking outside that one browser setting. The fix, for both that and for Meshnet, is the same habit: treat every connection as if it's still exposed to the open internet, put real passwords on local file shares, and turn on two-factor authentication for the account gating access to everything. I've written more about that layered approach in the no-logs VPN guide for developers — security here is a stack, not a single product.
When Meshnet Is the Wrong Tool for the Job
None of this makes Meshnet universal. If you need one static address that stays reachable no matter which device connects, or you're hosting something for people who'll never install NordVPN themselves, a full VPN server or a dedicated IP setup fits better. Meshnet earns its keep specifically for point-to-point access between devices you or people you trust already control — reaching a home workstation, syncing a photo library, grabbing a file mid-commute without opening a port to strangers.
The moment it actually clicked for me wasn't a benchmark chart — it was standing at a picnic table off the Green Lake Trail, pulling a 4K video file off my home server through a Meshnet link running clear across the country to a machine in New York, and watching it land without a single stutter or dropped frame. That's a harder test than any speed screenshot, because it's exactly the kind of transfer that falls apart first when a connection is actually struggling.
If you're the kind of person who reads encryption whitepapers for fun (no judgment, we've all been there), or you just want your home network reachable without leaving a port exposed to the internet, Meshnet is worth setting up before you reach for anything more complicated. I'd start with NordVPN [Editor's Pick] — it's the most polished version of this particular feature I've tested, and it costs a lot less than cleaning up after a breach.