OpenVPN Hosting on Your Own VPS
Your own VPN server with a dedicated address and nobody else on it.
Size a server for OpenVPN
Every stop is a real configuration you can deploy. Priced per 30 days, billed by the hour, exclusive of 18% GST.
What OpenVPN is
Running your own OpenVPN server is a different proposition from subscribing to a commercial VPN, and the difference cuts both ways.
What you gain: a dedicated IP address that is not shared with thousands of strangers and therefore not blocklisted by the services you use; certainty about logging, because you configure it; and a fixed endpoint you can allow-list on other systems — which is the common business use, letting staff reach an internal service from one known address.
What you do not gain is anonymity. A commercial VPN gets its crowd from having many users share an address. A personal VPN has one user, so all traffic from that address is yours by definition, and the server is registered to you. It is excellent for privacy from the network you are sitting on — a hotel, an airport, an ISP — and for secure remote access. It is not a tool for being unidentifiable.
Why run OpenVPN on a VPS
A dedicated IP that is yours alone, and not on the blocklists shared VPN ranges collect.
Root access, so the logging policy is one you set rather than one you are promised.
Choose the region, which decides your apparent location.
A stable endpoint that other systems can allow-list.
OpenVPN features
OpenVPN with certificate-based authentication
Clients for Windows, macOS, Linux, iOS and Android
Split tunnelling for routing only chosen traffic
Per-user certificates that can be revoked individually
Optional DNS resolution through the tunnel
WireGuard can be installed alongside if preferred
Recommended server
A starting point for OpenVPN, not a hard floor — size it on the sliders.
| Memory | 2 GB is plenty — VPN is not memory-hungry |
|---|---|
| CPU | 2 vCPU; encryption throughput scales with clock speed |
| Storage | 40 GB |
| Operating system | Ubuntu 22.04 LTS or Debian 12 |
How deployment works
OpenVPN is installed with its own certificate authority, client configuration profiles generated per user, and firewall rules for the tunnel. Bandwidth is the resource to watch — all tunnelled traffic counts against the server's transfer, so a VPN used for heavy browsing consumes real allowance.
What people run it for
Remote access to internal systems
Staff reaching private services without exposing them publicly.
A fixed source address
One address to allow-list on systems that restrict by IP.
Untrusted networks
Encrypting traffic on hotel, café and airport wifi.
Linking sites
Connecting an office network to cloud infrastructure.
OpenVPN hosting questions
Related applications
Home Assistant Hosting Automation with a fixed public address, long history and no subscription for remote access. 
Nextcloud Hosting File sync, sharing and collaboration on storage you own, without per-user pricing. 
Portainer Hosting A web interface for Docker — containers, images, volumes and networks, without living in the CLI. 
Immich Hosting A self-hosted photo library with mobile backup and search, on storage you own. 
Jitsi Hosting Video conferencing with no participant cap, no time limit and no account required. Deploy OpenVPN on your own server
Root access, your choice of size, and no container between you and the application.