Build your own VPN, or use a VPN app?

Let's follow the evening. Most people start by renting a small virtual server from a hosting company, which typically costs a few dollars a month and comes with its own address on the internet. You choose where it lives when you rent it: London, say, or Frankfurt.

Then the real work begins. Most home-built VPNs today use WireGuard, because it's small and simple to configure, and a typical setup runs roughly like this:

By midnight your phone has a working VPN, and it's a genuinely satisfying moment: you understand every piece because you put every piece there. Then the evening ends, and the job of running it begins.

The server needs security updates, and someone has to install them and restart it at a sensible hour. Your laptop needs its own keys and configuration, then your partner's phone, then the tablet. When a phone is lost or replaced, its key has to come off the server's list. If the hosting company has an outage, so do you.

A home-built VPN is a bit like owning a holiday flat. It's yours, it's in one city, and when the boiler breaks it's your weekend. Some people love that. Others discover they wanted the holiday, not the flat.

Your VPN lives wherever your server lives. If it's in Frankfurt, every website sees you arriving from Frankfurt. Want to appear in Singapore for a week? That's another server, another set of keys and another monthly bill.

The address is also yours alone, and that cuts both ways. Its reputation depends on nobody but you, but every site sees the same address on every visit, and the hosting company knows who rents it. With a VPN app, websites see the exit server's address, which everyone on that server shares, so your visits sit among other people's.

There's one place a home-built VPN can take you that an app can't: home. Run the server on a small computer in your own house, and while you're abroad, websites see your home connection, which your bank or a home-country service may treat as business as usual. If that's what you need, building your own is a strong option.

Building your own doesn't remove trust; it moves it. The hosting company can see how much traffic your server carries and where it goes, and it holds your payment details. You decide what your server records, and you're also the one responsible for keeping it secure.

With an app, you're trusting the company that runs it, so it's worth knowing exactly what it keeps. We keep connection records (your account, the time, the server and how long the session lasted) and hourly usage summaries that include the amount of data and the addresses and domain names reached, which can be linked to your account. Our privacy policy has the details, and you should expect the same specificity from any provider.

Either way, the protection on the local network is the same: the café, the hotel or your mobile provider sees sealed traffic going to a server and nothing more. Neither option makes you anonymous to the sites you sign in to.

Building your own makes sense when you enjoy the project, when you want to reach your home connection from abroad, or when one fixed place is all you'll ever need. It also suits anyone who wants to be their own operator and accepts the upkeep that comes with it. An app is the simpler answer when some of these are true:

If the project itself appeals, or you need your own home address while you're away, build your own: you'll learn a lot and own every part of it. If you simply want a private connection on every device, in a choice of places, without the upkeep, an app is the easier route. WrapVPN's free plan gives you three one-hour sessions a week, so you can try that route before deciding which camp you're in.