.webp){kind=small}
Your Laptop Is Not a Backup Strategy
Most developers find out their backup strategy has a hole in it at the worst possible time. A laptop gets stolen out of a co working space in Lisbon. A hard drive dies somewhere in Southeast Asia with no local Apple store for three hundred miles. A hotel wifi throttles the one sync job that was supposed to protect six months of client work.
If you have a fixed office, this is annoying but survivable. Someone on the team has a NAS, IT has a backup schedule, and there is a physical location where things live. If you are working out of a backpack across four countries a year, none of that safety net exists by default. You are your own IT department, and most nomads only realize this after something has already gone wrong.
This guide is not about cloud backup services, although they have a place. It is about owned infrastructure, the kind TechStop generally prefers over renting your entire operational continuity from a third party subscription. The goal is a setup that keeps working even when your internet connection, your location, or your hardware does not cooperate.
Why Cloud Only Backups Are Not Enough on the Road
Services like Dropbox, Google Drive, or GitHub are useful, but treating them as your only backup layer creates three specific problems for people who move around a lot.
The first is bandwidth. A lot of countries popular with digital nomads still have inconsistent upload speeds. Syncing a large repository or a client's full project directory over hotel wifi at two megabits per second is not a backup plan, it is a bottleneck you discover at the worst time.
The second is account risk. If your Google account, GitHub account, or cloud storage account gets flagged, locked, or compromised while you are in a country where support is slow to respond, you can lose access to your only copy of everything with no physical fallback.
The third is cost creep. Storage tiers on major cloud providers get expensive fast once you are backing up full project histories, client assets, and local development environments across multiple projects. TechStop's philosophical stance on this is simple. Rented infrastructure should support your workflow, not be the only thing standing between you and total data loss.
The Core of the Setup: A Portable NAS
The single most useful piece of hardware for a nomadic developer is a small, portable network attached storage device. Think of it as your own private cloud that travels with you or stays parked at a home base while you sync to it remotely.
A compact NAS from a brand like Synology or QNAP, running two or four drives in a mirrored configuration, gives you redundancy on day one. If one drive fails, which happens more often than people expect with drives that travel or sit in humid climates, the mirror keeps your data intact while you replace it.
You do not need to carry the NAS itself if you set it up at a home base, a family member's house, or a small colocation service in your home country. What matters is that you have one authoritative physical location where a real copy of your work lives, separate from any single laptop.
For developers actually traveling with hardware, a smaller single drive NAS or even a rugged external SSD with a Raspberry Pi running backup software can work as a lightweight version of the same principle. The point is not the specific hardware. The point is having a device you control, that is not dependent on a subscription staying active or a company staying in business.
Encrypted, Automated, Offsite: The Three Non Negotiables
Whatever hardware you choose, the backup process itself needs to hit three requirements or it is not actually protecting you.
Encrypted means your backups are useless to anyone who steals a drive or intercepts a sync. Tools like restic and Borg Backup are built specifically for this. Both support client side encryption, meaning your data is encrypted before it ever leaves your laptop, and both are efficient enough to run over slow connections because they only transfer changed data, not full copies every time.
Automated means the backup does not depend on you remembering to run it. A scheduled job, whether it is a cron task on Linux and macOS or a scheduled task on Windows, should run in the background every time you connect to a trusted network. If your backup strategy requires willpower, it will eventually fail, usually right before you needed it.
Offsite means your backup is not in the same bag as your laptop. This sounds obvious but it is the rule nomads break most often, because it is genuinely harder to maintain when you do not have a fixed office. A common setup is your portable NAS at a home base as your primary offsite target, with a secondary encrypted copy pushed to a cheap object storage bucket, like Backblaze B2 or Wasabi, as a tertiary layer. Two independent offsite locations means one bad event, whether that is theft, fire, or a service outage, does not wipe out everything.
Syncing Between Devices Without Relying on a Middleman
If you work across multiple devices, a laptop and a secondary machine, or collaborate with a small team that is also distributed, tools like Syncthing are worth setting up instead of defaulting to a cloud sync service for everything. Syncthing does peer to peer synchronization directly between your devices, encrypted in transit, with no third party server sitting in the middle reading or storing your files.
This matters for two reasons. It removes a dependency on a company's uptime and pricing decisions, and it means your sync speed is only limited by the connections between your own devices, not a shared service under load from millions of other users.
For actual code, Git remains the backbone, but the habit worth building is not relying on GitHub or GitLab as your only remote. Running a lightweight self hosted Git server, something as simple as Gitea on a small VPS or on the same NAS mentioned earlier, gives you a second remote that is entirely under your control. Push to both. It costs almost nothing and removes a single point of failure that a lot of developers do not think about until a platform has an outage during a client deadline.
Offline First Development: Building for Bad Connectivity, Not Around It
A nomad proof setup is not just about backups, it is about making your actual development workflow resilient to bad connectivity in the first place.
This means running local versions of anything you depend on rather than assuming constant access to a hosted service. Local databases instead of always hitting a remote dev database. Local package caches, using tools like a local npm or pip mirror, so a fresh install does not depend on a stable connection to a package registry in the middle of nowhere. Containerized local environments with Docker so your entire stack can spin up identically whether you are on fiber in Berlin or spotty 4G in rural Vietnam.
The practical test is this. Could you keep working productively for a full day with no internet at all, then sync everything once you are back online. If the answer is no, that is the gap to close before the next trip, not during it.
What This Actually Costs
The instinct is to assume owned infrastructure is expensive compared to just paying for more cloud storage. In practice, a decent two bay NAS is a one time cost in the range of most people's monthly SaaS stack for a single quarter, and it keeps working for years. A small VPS running a self hosted Git server and backup target runs a few dollars a month. Object storage as a tertiary backup layer is priced by usage and stays cheap unless you are storing enormous amounts of data.
The real cost of skipping this is not measured in dollars. It is measured in the week you lose rebuilding a client project from scratch because a laptop got stolen in an airport, or the trust you lose with a client when you cannot recover their work at all.
The Bottom Line
Digital nomadism removes the fixed office, but it does not remove the need for real infrastructure. It just means you have to build it yourself instead of inheriting it from an employer's IT department. A NAS you control, encrypted and automated backups pushed to at least two offsite locations, sync tools that do not depend on a third party middleman, and a development workflow that assumes bad connectivity rather than fighting it. None of this is complicated. It just has to be set up once, before the trip where you actually need it.
