Wetin You Fit Use VPS Do? 20 Real Examples

Wetin You Fit Do with a VPS?

A VPS (virtual private server) na Linux machine wey get public IP address and dey run whether your laptop dey on or not. So, anything wey suppose remain reachable fit dey there. For real use, this mean websites, private VPN, your own file and photo storage, media, game servers, scheduled scripts, and plenty AI tooling wey dey increase. Below na twenty things wey people really dey run. We arrange dem roughly based on how often dem be the main reason person rent server.

Each entry talk wetin the job be, how much memory e go use, and where the complete guide dey. If you want wider catalogue of applications instead of the jobs, the companion list of apps wey worth self-hosting for 2026 dey explain each app one by one.

The 20 things wey people really dey run

1. Host website or web app. Na still the commonest answer be this. One small server fit run nginx or Apache, PHP, and database well with 1 GB of RAM, and the usual starting point na LAMP stack for Ubuntu 24.04. Add free certificate with Certbot and Let's Encrypt for nginx, because bare IP address for port 80 go make browsers show warning wey fit make every visitor comot.

1. Run many sites and apps for one box. One server fit serve twelve names if something for front sort requests by hostname. Reverse proxy dey do this work and e dey renew certificates too. Na why Traefik for front of many Docker apps dey usually be the second step. The saving dey real: five projects for one 4 GB server cost less than five small servers, and backup dem dey easier.

1. Your own VPN. VPS dey give you exit IP wey you control, so public Wi-Fi no fit read your traffic and your home services stay away from open internet. WireGuard dey use less than 50 MB of memory and e dey run for kernel, so server hardly notice am. The self-hosted WireGuard VPN guide cover handshake and DNS problems wey dey catch people. People dey often confuse the two products, so e good make you first spend one minute for VPS versus VPN comparison.

1. Password manager wey belong to you. Vaultwarden dey speak Bitwarden protocol, so every official app and browser extension connect to your server instead of company own. E need about 150 MB of RAM and almost no disk, so Vaultwarden for a VPS na the best first project for this list. This box hold every password wey you get, so treat the certificate and backups as part of the installation, no be later task.

1. Cloud file storage and calendars. Nextcloud replace paid Drive or Dropbox plan with sync clients for every desktop and phone, plus calendar and contacts. Plan 1 to 2 GB of RAM plus the size of your files, and install am with PostgreSQL from the beginning. The Nextcloud with Docker, TLS and backups guide explain why moving the database later na the commonest way people spoil instance.

1. Photo library with phone upload. Immich dey upload your camera roll automatically and e dey search faces and objects. Na this feature finally dey make people comot from Google Photos. E dey use the most resources here because of machine-learning container, so read the self-hosted Immich guide before you buy the smallest plan. Pin one version instead of pulling latest, because breaking changes still dey enter between releases.

1. Media server for your own library. Jellyfin stream your films and shows to TV app, browser, or phone without account and without paywall for remote playback. E dey idle around 1 to 2 GB of RAM. The thing wey decide whether e go work na transcoding. Jellyfin for a VPS show how to keep files for format wey clients fit play directly, so server only move bytes.

1. Game server for friends. Minecraft server for small group of players need 2 to 4 GB of RAM and machine wey stay online when the host player go sleep. Na exactly wetin VPS be for. The Minecraft server for a VPS guide cover Java memory flags and how to run am under systemd, so crash go restart am by itself.

1. Scheduled scripts, scrapers, and bots. Anything wey must run for 3 in the morning need machine wey dey awake for 3 in the morning. Write the job as systemd service with timer instead of cron line, because you go get logs, failure status, and clean way to test am. systemd services and timers for a VPS get the unit files. Discord or Telegram bot na the same pattern, but e use long-running process instead of timed one.

1. Automation workflows. n8n give you visual builder for work wey Zapier dey charge per task, and running am yourself remove both the bill and limit on how much data fit pass through. E dey use around 500 MB of RAM. Set encryption key explicitly, as self-hosted n8n with HTTPS show, or container rebuild go make every saved credential unreadable.

1. Run language model yourself. Ollama serve open-weight models through local API, so prompts and documents no go leave your server. For CPU-only VPS, expect few words per second instead of instant answers, and plan about 8 GB of RAM for 8B model. Running Ollama to self-host an LLM get honest numbers. For workflow platform on top of the model, Dify for a VPS add UI and retrieval.

1. Give coding agent somewhere to live. AI coding agent wey work for one hour useless if e die when you shut your laptop. So people dey put am for server inside terminal multiplexer and reconnect later. Claude Code for a VPS with tmux na the setup, while running a coding agent for a VPS cover the general pattern. Give am own unprivileged user and directory wey e no fit escape from.

1. Host MCP servers for your assistants. MCP (model context protocol) servers na small always-on processes wey expose tools and data to AI client. Always-on na the part laptop no fit provide. MCP servers for a VPS explain how to run dem behind TLS with authentication. This matter because open MCP endpoint na tool anybody fit call.

1. Monitor your other servers. Uptime Kuma dey ping your sites and alert you through almost any channel, and e dey run with about 200 MB. The rule wey people dey miss be say: monitor production from another machine. Uptime Kuma status monitoring wey run for the box wey e dey monitor no fit tell you when that box die.

1. Real metrics, no be only up or down. When you get fleet instead of one server, you go want CPU, disk, and service metrics with history and triggers. A Zabbix monitoring server dey do this with agent for every host, and e need 2 GB of RAM plus own database. Start with simple uptime check and move up when you get something wey need the next level.

1. Offsite backups for everything else. Backup wey dey on the same disk with the data no be backup. Cheap VPS with large volume fit be good destination, and restic backups for a VPS give you encrypted, deduplicated, versioned snapshots with restore wey you fit really test. Test am every month, because untested backup na hope.

1. Your own CI runner. Hosted build minutes dey finish, while self-hosted runner keep your caches warm and your secrets local. A self-hosted GitHub Actions runner show the installation and isolation. This matter most for public repositories where pull request fit run code for your machine.

1. Team chat wey you control. Rocket.Chat cover threads, calls, and integrations for team wey no want pay per seat. E need 2 GB of RAM and more because MongoDB na the heavy part. Rocket.Chat with Docker Compose explain the version ladder, because skipping MongoDB major version during upgrade fit leave the database stranded.

1. Private network across all your machines. Once you get many servers and laptop, mesh network easier to manage than one hub. Headscale as self-hosted Tailscale control server keep coordination for your own box. Join am with the habit of treating hosts as group, which na wetin managing many Linux servers dey explain.

1. Lab, and mail server if you insist. VPS na safe place to break things. Try a FreeBSD 15 server, or run virtual machines inside your server where the plan allow nested virtualization. Email dey last intentionally because most providers block outbound port 25 and deliverability na long fight. So read self-hosted email with Mailcow with full understanding.

How much server each one need?

Memory na be the limit, no be CPU or disk. A 1 GB plan fit run one small thing: a website, a VPN, a password manager, or a bot. A 4 GB plan na the comfortable option to run some services behind one proxy. Na so most people for this page dey use am.

2 GB na the awkward size. Na for there person go add third container, the kernel go kill am quietly, and nothing for the application log go explain why. Run sudo dmesg | grep -i "out of memory" and you go see the Out of memory: Killed process line wey the container runtime swallow. AI workloads no follow this rule: an 8B language model need roughly 8 GB before e fit load at all, and photo machine learning dey similar.

Disk dey depend on your data. Photos, media, and backups na the only things for here wey need hundreds of gigabytes. Everything else go fit inside the 20 to 50 GB wey small plan include.

Before you run any of it

Every time you use the things above, e base dey the same: a machine wey you fit reach, one user wey no be root, and a firewall.

sudo apt update && sudo apt upgrade -y
sudo adduser deploy
sudo usermod -aG sudo deploy
sudo ufw allow OpenSSH
sudo ufw enable
sudo ufw status

sudo ufw status suppose print Status: active with one line wey dey allow 22/tcp. Open second terminal and confirm say you still fit log in before you close the first one, because if firewall lock you out, you go need console rescue from your provider's panel. the first ten minutes for new VPS explain everything from start to finish, and SSH hardening dey turn off password login so the regular background brute-force attempts no longer matter.

Almost every application above dey ship as container, so install Docker once and the rest of the list go become copy and paste:

curl -fsSL https://get.docker.com | sudo sh
sudo usermod -aG docker "$USER"
newgrp docker
docker run --rm hello-world

If reading permission denied while trying to connect to the Docker daemon socket fail, e mean say the group change never reach your shell yet, so log out and log back in. Docker Compose basics explain the file format wey all the guides above dey use.

Wetin VPS no good for

Make we talk about some honest limits. Heavy graphics work and model training need GPU, but standard VPS no get am. So inference for CPU go remain slow, no matter how much RAM you add. Anything wey five minutes of downtime fit cause real harm, like home alarm or medical alert, no belong for hobby server wey you dey upgrade Sunday night. One server na also one single point of failure. So service wey must never go down need second box and tested way to switch go there.

Email need special warning, even though e dey on the list. Most providers block outbound port 25. Even when dem open am, new IP address wey no get reputation go enter spam until DNS records correct and the address don build reputation. Email na real ongoing job, no be something wey you fit finish for weekend.

FAQ

Wetin be the most common use for VPS?

To host website or web application. Small server wey dey run nginx or Apache with PHP and database fit handle personal site, client site, or small product with 1 GB of RAM. Na the cheapest way to get real public IP address with full control of the stack. The second most common use na private VPN, because server wey you own gives you exit address wey nobody else dey share.

How much RAM I need for the things wey dey this list?

For one small service, 1 GB dey work. For some services behind one reverse proxy, 4 GB na comfortable size, and na the plan wey most people dey choose. AI workloads na exception: 8B language model needs roughly 8 GB before e loads, and photo machine learning needs similar amount. Disk only matter if you dey store media, photos, or backups.

I fit run more than one of these for the same server?

Yes, and na normal thing. Put each application inside e own container, publish nothing directly to the internet, and make one reverse proxy handle the names and certificates. Memory na the limit, no be the number of applications. Add the real figures above together, then leave at least 25 percent headroom so upgrade or backup run no trigger out-of-memory kill.

I need to know Linux before I fit use VPS?

You need the basics: connecting over SSH, editing file, and reading log. Everything else for these guides na copy, paste, and check the output against wetin the guide say you suppose see. If you prefer to click instead of type, control panel fit manage the applications for you, and the comparison of Cloudron, CasaOS and Coolify explains wetin each one costs you for flexibility.

VPS cheaper pass to pay for these services?

Usually, once you dey run more than one. One 4 GB server fit replace file sync subscription, password manager plan, photo storage plan, and automation tool bill at the same time. The cost wey you take on instead na your own time: updates, certificates, and backups now na your responsibility. So the saving only real if you actually do them.