Complete guide, 2026
What can you do with a VPS? 22 self-hosted apps, sized and ready to run.
Most “things to do with a VPS” lists stop at a sentence per idea. This one tells you what each project needs, what fits together on one server, and how to have it running today.
- Minecraft Java server2 GB
- Password manager1 GB
- Ad-blocking DNS512 MB
- Uptime monitor256 MB
- WireGuard VPN128 MB
- Static website128 MB
- Ubuntu Server1 GB
One server, six jobs
6.3 GB of 8 GB
5 GB of software, plus 25% spare
A VPN, ad blocking, a password manager, a website, an uptime monitor and a Minecraft world, sized from each project’s own published requirements, with 25% spare.
The short answer
A VPS is a computer that never sleeps, with its own public address and full admin rights. That makes it good at anything that must be reachable all the time: your own VPN, websites, file and photo storage, password managers, automations, bots, game servers and crypto nodes.
Most of these are light. A VPN, an ad-blocking DNS server and a small site together fit on a Lite 2. A few are heavy: photo backup and mail servers each want at least 6 GB. Our free planner below adds up any mix you pick and names the LiteKeep plan that holds it.
Here’s something most people never see.
We logged in to one of our own servers after three days online and asked it how much memory it was using. The answer: 129 MB out of 8 GB. A fresh server is almost entirely empty space, waiting for a job.
So the real question isn’t “what can a VPS do?” It can run almost anything Linux runs. The question is what’s worth running, what it needs, and what fits together on one machine.
Here’s the problem. Most lists give you ideas, then stop. No memory figures, no disk sizes, no word on what fits together.
So we sized 22 projects, from WireGuard to Bitcoin Core, and built a planner that adds them up for you and points at the plan to run them on.
In this guide you’ll learn
- 22 projects across privacy, building, automation, storage, games and crypto
- What each one needs: RAM, disk and ports
- A free planner that shows what fits on one server, and which ports clash
- How to run many apps on one server without them fighting
- What to keep off your server, and what LiteKeep allows
- VPS, home server or hosted app? Where each one wins
Chapter 1
The short answer
Nearly every good VPS project falls into one of six groups. Here they are, with the best-known example of each.
| Goal | Typical projects | What you get |
|---|---|---|
| Privacy | WireGuard VPN, Bitwarden, Pi-hole, a Tor relay | Your traffic, passwords and DNS on a machine you control |
| Build and publish | Websites, WordPress, Coolify, Git, analytics | Sites and apps with no platform rules or per-seat fees |
| Automate | n8n, bots, uptime checks, AI agents | Jobs that run every minute, even when your laptop is shut |
| Store and stream | Nextcloud, Immich, Jellyfin, backups, mail | Your files and photos, stored where you choose |
| Play | Minecraft, Valheim | A world that stays up for your friends |
| Crypto | Bitcoin node, trading bots | Verify your own transactions; trade around the clock |
Each chapter below takes one group, explains what the projects do, and gives you the RAM and disk each one needs, so you can pick a plan with confidence.
Chapter 2
What a VPS gives you that your laptop can’t
You could run most of these projects on an old laptop at home. People do. A VPS earns its place by giving you four things a home machine struggles with.
- It never sleeps. It sits in a data centre with backup power and cooling, so your VPN works at 3 a.m. and your bot never misses a message.
- It has its own public address. Home connections often share addresses or block incoming connections. A VPS can be reached directly by anyone you allow.
- It has a data-centre connection. Upload speed is often the weak spot of home internet, and serving anything is all upload.
- You choose where it lives. Put it near your players, near an exchange, or in a country whose laws suit you. We offer 15 countries at one price.
And you get full administrator (root) access. It’s your machine: install anything, configure anything.
How much of the server is really free?
More than you’d think. Here’s our own server, measured, after three days on the internet:
- fail2ban (blocks password guessers)33.9 MB
- systemd journal (logs)25.5 MB
- automatic security updates22.3 MB
- host’s guest agent15.2 MB
- SSH, one session9.6 MB
The biggest process on it is the tool that blocks password guessers, which we wrote about in our VPS security guide. Our planner counts 1 GB of RAM for Ubuntu to be safe. In practice a bare server uses far less.
Chapter 3
Privacy: your own VPN, passwords and DNS
These are the projects most people start with. They’re light, useful every day, and they move your data from someone else’s servers to yours.
WireGuard: a VPN you own
WireGuard is a modern VPN built into the Linux kernel. Connect your phone and laptop to it and your traffic on hotel and café Wi-Fi travels encrypted to your server, then out to the internet from there. It listens on port 51820/udp by convention and barely needs any resources at all. Our WireGuard tutorial sets it up with ufw on, tested step by step.
What you get: your internet provider and the café Wi-Fi no longer see what you visit, and the sites you visit see your server’s address instead of yours, in the country you picked. On LiteKeep, VPNs are allowed in every country, and you pay in crypto with no ID.
Bitwarden or Vaultwarden: your password manager
Bitwarden’s self-hosted server needs 2 GB of RAM and 12 GB of disk at minimum, 4 GB and 25 GB for comfort. Many people run Vaultwarden instead, which works with the same apps and is much lighter. Either way, it needs HTTPS before browsers will trust it.
Pi-hole or AdGuard Home: ad blocking for every device
A DNS server that refuses to look up ad and tracker domains. Pi-hole needs 512 MB of RAM and 2 GB of free disk. Pair it with WireGuard and your phone blocks ads everywhere, with no app. With ufw on, allow DNS on the VPN interface: ufw allow in on wg0 to any port 53.
A Tor relay: give something back
A middle relay passes encrypted Tor traffic between other relays. It needs at least 512 MB of RAM below 40 Mbit/s and 100 GB of outbound traffic a month. Tor relays, exits included, are allowed on LiteKeep; a middle relay is the easy way to start, because exit relays carry other people’s traffic to the open internet and draw more complaints. For a busy relay, a Traffic Lite with 32 TB a month is the natural home.
Chapter 4
Build and publish: sites, apps and code
Hosting websites is the most common reason people rent a server. A VPS lets you run as many as fit, on any software you like.
Static sites and WordPress
A static site is just files served by Nginx or Caddy: tiny, fast and almost impossible to hack. WordPress needs PHP and a database. A typical site needs 256 MB per PHP process, so a site with four PHP workers wants about 1 GB, plus room for the database. Busy shops need more workers.
Coolify: your own app platform
Coolify gives you a dashboard to deploy apps straight from Git, with HTTPS handled for you, much like a hosted platform but on your server. It needs 2 CPU cores, 2 GB of RAM and 10 GB of disk for itself. Your apps come on top. If you run lots of small side projects, one Lite 6 with Coolify can replace several paid hosting accounts.
Git, analytics and an editor
- Forgejo or Gitea give you private Git hosting with issues and pull requests. Small teams run them on very little.
- Plausible is cookie-free analytics. It needs at least 2 GB of RAM and a CPU with SSE 4.2.
- code-server runs VS Code in your browser. It needs at least 1 GB of RAM and 2 CPU cores.
Want several sites on one server? You can, and chapter 9 shows how they share ports 80 and 443 without stepping on each other. To size the server, use our VPS size picker or the planner below.
Chapter 5
Automate: workflows, bots and AI agents
Automation is where an always-on machine really pays off. Anything that must react at any hour belongs on a server, not a laptop.
n8n: workflows on your own server
n8n connects apps the way Zapier does: “when a form is filled in, add a row and send a message.” Memory grows with the data your workflows handle, so start with 1 GB free for light use and give heavy workflows up to 4 GB.
Bots and scheduled jobs
Telegram and Discord bots, price trackers, scrapers, nightly reports. Most are small scripts that need no open ports at all, because they call out to the service rather than waiting for calls in. That also makes them easy to secure.
Uptime monitoring
Uptime Kuma checks your sites every minute and alerts you when one goes down. It runs on Node.js 20.4 or newer and needs local disk, which every LiteKeep server has. Run it on a different server from the sites it watches, ideally in another of our countries, so it can still tell you when they’re down.
AI agents
An AI agent is a program that takes a goal and works on it: reads email, writes drafts, runs tasks, calls tools. Projects like OpenClaw run the agent on your server and call an AI model online. We offer one-click OpenClaw hosting and templates for other AI apps. The agent itself is light; the thinking happens at the model provider.
OpenClaw needs 1 GB of RAM at minimum and runs well on 2 GB with swap, which is why Lite 2 is enough. One firm rule: keep the agent’s gateway on loopback, and reach it through an SSH tunnel, not the open internet.
- Give every bot its own API keysHow to check: Create one key per bot in each service’s dashboard, so you can revoke one without breaking the rest.
- Set spending limits on paid APIsHow to check: Set a monthly cap in the provider’s billing settings, if it offers one. An agent stuck in a loop can make thousands of calls overnight.
- Keep dashboards off the public internetHow to check: Bind them to 127.0.0.1 and reach them through WireGuard or an SSH tunnel.
- Log what your agents doHow to check: Write every action to a log file and read it the next morning. You want to know what happened at 3 a.m., not guess.
Chapter 6
Store, stream and back up
These projects hold your data, so they need more disk and, for some, a lot more memory. Get the size right before you start.
Nextcloud: your own file cloud
Files, calendar, contacts and sharing links, synced to your devices. Nextcloud needs about 512 MB per PHP process, so four workers plus a database is about 2.5 GB. Add your files as data, or put them on a Vault.
Immich: photo backup from your phone
The closest self-hosted match to Google Photos. It’s also one of the hungriest projects here: Immich needs at least 6 GB of RAM and 2 CPU cores, 8 GB and 4 cores for comfort. Give it a Lite 8.
Jellyfin: your own films and music
Jellyfin streams media you own to any device. It runs on about 4 GB of RAM with 100 GB of fast disk for the system and cache. Converting video on the fly is heavy work, so keep files in formats your devices can play directly, or run it on a Forge GPU server for transcoding. Streaming sends a lot of data, which is what Traffic Lites are for.
A backup target
The simplest storage project of all: a server that holds encrypted copies of your other servers. Tools like restic send only what changed. It needs almost no memory, just disk, which is why our Vaults pair a small CPU with 700 GB to 3 TB.
Your own mail server
Possible, satisfying, and the hardest project on this page. mailcow, a popular all-in-one suite, needs at least 6 GiB of RAM plus 1 GiB of swap and 20 GiB of disk before any email, and it only runs on full virtualization: every LiteKeep server is KVM.
Memory is the easy part. Sending mail needs outbound port 25, and many hosts block it by default. On LiteKeep, port 25 is open and you can set reverse DNS yourself. Add SPF, DKIM and DMARC records and your mail is ready to go.
Chapter 7
Play: game servers
A game server on a VPS stays up when your PC is off, doesn’t share your home connection, and can sit close to where your friends live.
Minecraft
A small Minecraft server needs 1 GB at the very least, 2 GB for a small group and 4 GB for the best experience, and very little disk for world saves. Mods and more players push memory up fast. The default port is 25565. Our Minecraft RAM calculator adds it up from measured figures.
Valheim and others
A Valheim dedicated server listens on 2456 to 2457 over UDP. Memory depends on your world and your mods, so start on a Lite 6 and check free -h after a busy evening.
Not sure about traffic? Game servers are usually modest, and every Lite includes 1 TB or more a month. Run a traffic counter for a day, as our bandwidth guide explains, and multiply by 30. And because game servers get attacked, every LiteKeep server has DDoS filtering at the network edge.
Chapter 8
Crypto: nodes and trading bots
Crypto users were self-hosting long before it was fashionable. Two projects make the most sense on a VPS.
A Bitcoin node
Running your own node means your wallet checks transactions against your own copy of the rules instead of trusting someone else’s server. A node needs 2 GB of RAM and an upload of at least 400 kilobits a second, and typically downloads around 20 GB a month.
Disk is the decision. A full node keeps the whole chain, which now takes over 750 GB and keeps growing: that’s a Vault job. A pruned node keeps only recent blocks, cutting disk to around 7 GB, and still verifies everything.
Monero nodes support pruning too, and crypto nodes of every kind are allowed on LiteKeep.
A trading bot
Freqtrade, a popular open-source bot, runs well on 2 GB of RAM, 1 GB of disk and 2 vCPU: a Lite 2. Put it in the country closest to your exchange. It also needs an accurate clock, so keep time sync on.
And yes, you can pay for the server in the same coins. Our crypto payment guide walks through it.
Chapter 9
Run many projects on one server
Most people end up running several projects on one server. Tick everything you want below. The planner adds up what each project needs, flags port clashes, and finds the cheapest LiteKeep plan that holds all of it, ready to deploy.
3 projects on one server need about
1.9 GB RAM, 32 GB disk, 1 vCPU
- Ubuntu
- WireGuard VPN
- Static website (Nginx)
- Uptime monitor (Uptime Kuma)
Bar = share of the Lite 2’s 2 GB, with 25% headroom included.
- 2 of these want ports 80 and 443. Put one reverse proxy in front (Caddy, Nginx, or Coolify’s own) and give each app its own domain or subdomain.
How we added it up
| Ubuntu Server (cloud image)Ubuntu needs 1 GB of RAM; 25 GB is a comfortable disk. | 1 GB 25 GB |
|---|---|
| WireGuard VPNNo official figure needed: WireGuard runs inside the Linux kernel and is very light. It listens on 51820/udp by convention. | 128 MB - |
| Static website (Nginx)No official figure needed: Nginx serving files fits easily in what the OS leaves free. | 128 MB 1 GB |
| Uptime monitor (Uptime Kuma)No official figure; it needs Node.js 20.4 or newer and a local disk, which every LiteKeep server has. | 256 MB 1 GB |
| Your dataFiles, photos, backups and mail you expect to store. | - 5 GB |
RAM total includes 25% headroom. CPU is the largest single minimum, because idle projects share cores well.
Try ticking Immich next to a few light projects and watch the plan jump. Then try a full Bitcoin node and see the planner switch to a storage plan.
Rule 1: one port, one program
Only one program can listen on a port. Web apps all want 80 and 443, so you put a reverse proxy in front: it takes every visitor and hands each domain to the right app.
- example.comWebsite
- cloud.example.comNextcloud
- status.example.comUptime Kuma
- git.example.comForgejo
Rule 2: Docker can open ports behind your back
Many of these projects ship as Docker containers, and published container ports bypass your firewall rules, including ufw. Publish ports only to 127.0.0.1 and let the reverse proxy face the internet. Our Docker tutorial shows the install, our ufw test and a server-wide fix.
Rule 3: separate what can hurt each other
Keep mail, and anything that strangers can log in to, apart from your private tools. A second small Lite costs little, bills by the hour, and keeps one mistake from reaching everything.
- Secure the server before the first appHow to check: SSH keys, a firewall and automatic updates. Our security guide generates the commands.
- Put every web app behind the reverse proxyHow to check: Run
ss -tlnp: only the proxy should be listening on ports 80 and 443. - Give each app its own user or containerHow to check: Run each app as its own system user or in its own container, so a bug in one can’t read another’s files.
- Back up to a different serverHow to check: Preferably in another country. Restore one file from it to prove it works.
- Watch memory for a weekHow to check: Run
free -heach day. If swap is in use, move a project or size up.
Chapter 10
What to keep off your server
Good news first: LiteKeep allows far more than most hosts. Here’s what you can run, what we don’t allow, and what simply runs better somewhere else on our network.
Allowed on LiteKeep
Crypto mining, crypto nodes, Tor relays including exits, proxies and VPNs, torrents and mail servers, within the law, in all 15 countries. Many hosts ban several of these. Our acceptable use policy spells it out in plain words.
Not allowed anywhere
- Spam, phishing, malware and botnets. They poison the IP ranges everyone else depends on, so we shut them down in every country.
- Scanning other people’s networks. Scan only what you own.
- Open relays and resolvers. Open mail relays, open proxies and open DNS servers get found and abused by strangers. Lock them to your own users.
- Illegal content. Hosting offshore doesn’t change what’s illegal. Our offshore hosting guide explains what choosing a country does for you.
Better on a different plan
Chapter 11
VPS, home server, Raspberry Pi or hosted app?
Here’s how a VPS compares with the alternatives for the projects on this page.
| VPS | Home server or Pi | Hosted app (SaaS) | |
|---|---|---|---|
| Reachable from anywhere | Yes, public address | Depends on your connection and router | Yes |
| Always on | Data-centre power and cooling | Your power, your internet | Yes |
| Upfront cost | None | The hardware | None |
| Running cost | Monthly or hourly fee | Electricity | Subscription per app or seat |
| Big storage | A Vault: 700 GB to 3 TB of NVMe | Your own disks | Plan limits |
| GPU work | A Forge GPU server, by the hour | Your own graphics card | Built in, if offered |
| Upkeep | You maintain the software, never the hardware | You maintain everything | They maintain it, on their terms |
| Where your data lives | The country you choose | Your home | Wherever they choose |
A home server is fine if your power, router and upload speed never let you down. A hosted app means paying per app or per seat, on someone else’s rules. A VPS gives you one bill, every app you want, reachable all the time, in the country you pick.
Chapter 12
Your first project, step by step
Whatever you pick, the order is the same. Do it in this order and you’ll avoid the classic mistakes.
Pick one project
Start small. WireGuard, a static site or Uptime Kuma are good first projects: light, useful, and quick to see working.
Size the server
Tick it in the planner above, plus anything you’ll add soon. Hourly billing on our Lites means a test server costs only the hours it exists.
Pick a location
Near your users or players, or in the country whose laws suit the project. See all 15 locations.
Secure it first
Before any app: SSH keys, a firewall, automatic updates. Our security guide builds the commands for you.
Install and test
Install the project, or use one of our one-click templates. Check it works from another device.
Back up and monitor
Set up a backup to another server and an uptime check. Then add your next project.
Quick answers
Is a VPS worth it for personal use? If you’ll run something every day, such as a VPN, password manager or bot, yes. One Lite 2 can replace several monthly subscriptions.
Can I run several websites on one VPS? Yes. A reverse proxy shares ports 80 and 443 between them; memory is the real limit.
Can I use a VPS as a VPN? Yes. WireGuard needs almost no resources, protects you on public Wi-Fi, and gives you an address in the country you choose.
How much RAM do I need? It depends entirely on the mix. A VPN and a small site fit in 2 GB; photo backup or mail needs 6 GB or more. Use the planner.
Now it’s your move
A VPS is a blank computer that never sleeps. What you put on it is up to you.
Start with one project you’ll use every day. Size it from the real requirements, not a guess. Secure it before anything else. Then build from there.
Ready to start? Our Lites bill by the hour, so your first project can be running, usually within 15 minutes, for cents, and you can delete it any time.