What can you do with a 512 MB VPS?

Part of the plan size series. See also the guides for 1 GB, 2 GB and 4 GB plans.

A 512 MB VPS is the smallest kind of server most people will rent. Half a gigabyte of memory sounds tiny, and for many jobs it is. But a minimal Linux server uses very little memory by itself, which leaves room for one or two light jobs that run quietly all day.

This guide lists twelve jobs that fit, how to set each one up, and what to watch for. It also says plainly what does not fit, because the cheapest plan is only good value if it can do your job.

What is in this guide

• The memory budget
• Five habits for small servers
• 1. A personal VPN
• 2. A static website
• 3. An SSH jump host
• 4. Ad-blocking DNS for your devices
• 5. A small chat bot
• 6. Scheduled scripts
• 7. Simple uptime checks
• 8. A Linux learning sandbox
• 9. Reaching a home server from outside
• 10. Private Git repositories
• 11. A small backup target
• 12. A second-location test point
• What does not fit
• When to step up

The memory budget

These figures are rough. Real use varies with the version, the settings and how busy the job is. Check your own server with free -h after setup.

What is running	Rough memory use
Minimal Debian or Ubuntu, idle	About 80 to 150 MB
WireGuard VPN	A few MB
nginx serving a static site	About 10 to 30 MB
A small Python bot	About 30 to 80 MB
Ad-blocking DNS such as Pi-hole or AdGuard Home	About 50 to 150 MB
MariaDB or MySQL database	Often 100 MB or more, and grows with use
Docker itself, before any containers	Often 50 MB or more

The lesson: after the operating system, you have roughly 300 to 400 MB to spend. One or two light jobs fit. A stack of services does not.

Small plans also tend to have less disk, one CPU core and a smaller bandwidth allowance than larger plans. Check those on the plan before you choose a job for it.

Five habits for small servers

1. Choose a minimal image. Debian or Ubuntu without extras. Remove anything you do not use.
2. Add a small swap file. Swap is a safety net when memory briefly runs out, not extra RAM. If you use it all the time, the job is too big for the plan. To add 512 MB of swap:

   sudo fallocate -l 512M /swapfile
   sudo chmod 600 /swapfile
   sudo mkswap /swapfile
   sudo swapon /swapfile
   echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

3. Skip Docker unless you need it. Installing a program directly from the package manager usually uses less memory than running it in a container.
4. Prefer light tools. nginx over Apache, SQLite over MySQL, a shell script over a web dashboard.
5. Secure it first. A tiny server is still a server. Follow securing your VPS and setting up SSH keys before anything else.

1. A personal VPN

What it is. A private, encrypted tunnel from your phone or laptop to your server. Your traffic leaves the internet from the server, which helps on public Wi-Fi.

Why it suits this plan. WireGuard runs in the Linux kernel and uses almost no memory. For one person or a small household, a 512 MB plan is usually plenty.

How to set it up. Install WireGuard from your package manager, or use a helper tool that creates the configuration for you. Setting up a VPN on a VPS walks through it.

Watch out for. Bandwidth. Streaming through the VPN uses your monthly allowance quickly on a small plan. A personal VPN is not the same as a commercial VPN service. See VPS vs VPN. Follow the provider's acceptable use policy for what you send through it.

2. A static website

What it is. A website made of plain HTML, CSS and images, such as a portfolio, a landing page or a site built with a static site generator.

Why it suits this plan. Serving static files is one of the lightest jobs a server can do. nginx can handle a small site with very little memory.

How to set it up. Install nginx from your package manager, upload your files to its web folder and add a free SSL certificate with a tool such as Certbot. Web servers explains the options.

Watch out for. Dynamic sites. WordPress needs PHP and a database, which is tight at 512 MB. If you want WordPress, see what does not fit. Large images and downloads also use bandwidth.

3. An SSH jump host

What it is. A small server you log in to first, and then use to reach your other servers. Only the jump host is open to the internet for SSH.

Why it suits this plan. SSH uses almost no memory. The job is about security and access, not power.

How to set it up. Secure the jump host with keys only. On your other servers, allow SSH only from the jump host's IP address. On your computer, use the -J option, for example ssh -J alex@JUMP_IP alex@OTHER_SERVER.

Watch out for. It becomes the key to everything, so protect it well. Use keys with passphrases, turn off password login and keep it updated. If it goes down, have another way in, such as the provider's control panel console.

4. Ad-blocking DNS for your devices

What it is. A DNS server that blocks known advert and tracking domains for every device that uses it. Pi-hole and AdGuard Home are two popular choices.

Why it suits this plan. For one person or a small household, the memory use is modest. It pairs well with the VPN in idea 1, so your phone gets ad-blocking anywhere.

How to set it up. Install it from the project's own documentation, using its package or official instructions rather than a piped install script. Make it listen only on the VPN interface, and point your VPN clients at it.

Watch out for. Never run an open DNS resolver on the public internet. Attackers misuse them, and it can break the acceptable use policy. Keep the DNS port closed in the firewall except over the VPN. Large blocklists use more memory, so start small.

5. A small chat bot

What it is. A bot for Discord, Telegram, Matrix or similar that answers commands, posts reminders or relays messages.

Why it suits this plan. A simple bot written in Python or Node.js often uses well under 100 MB, and needs to run all the time, which is exactly what a VPS does.

How to set it up. Install Python or Node.js from your package manager, copy your bot's code to the server and run it as a systemd service so it restarts after a crash or reboot. Keep the bot's token in a file only its user can read, such as one set with chmod 600.

Watch out for. Memory leaks. Some bots grow slowly over days. Check with free -h now and then. If your bot calls an AI service, read and test anything the AI writes before you rely on it, and keep the API key out of your code.

6. Scheduled scripts

What it is. Small jobs that run on a timer: fetching a report, cleaning up files, sending a daily email or checking a price feed you are allowed to use.

Why it suits this plan. Most scripts run for seconds and use little memory, so the server sits idle most of the time.

How to set it up. Put the script in your home folder, test it by hand, then schedule it with crontab -e. Send its output to a log file so you can see what happened.

Watch out for. Scraping websites can break their terms and the provider's acceptable use policy. Use official APIs where they exist. Do not let two runs overlap if a job can take a long time.

7. Simple uptime checks

What it is. A server that checks your websites or services every few minutes and tells you when one stops responding.

Why it suits this plan. Checking a site is a light job. Running the checker on a separate small server means it still works when your main server is down.

How to set it up. The lightest approach is a short shell script, run from cron, that uses curl to fetch each page and sends you a message if it fails. Dashboard tools such as Uptime Kuma are friendlier but use more memory, so check their current requirements first.

Watch out for. False alarms from brief network blips. Only alert after two or three failed checks in a row. Do not check other people's sites without permission.

8. A Linux learning sandbox

What it is. A cheap server for learning the command line, practising security settings or breaking things on purpose.

Why it suits this plan. Most learning tasks need very little memory. If you break it, you reinstall it from the control panel and start again.

How to set it up. Start with getting started and Linux server tools. Practise users, permissions, the firewall, systemd services and log files.

Watch out for. Treat it as a real server from day one. Even a practice box needs keys and a firewall, because it is on the internet. Do not keep anything important on it.

9. Reaching a home server from outside

What it is. A way to reach something at home, such as a media server or home automation, when your home internet does not let you open ports.

Why it suits this plan. The VPS only passes traffic along. It needs a public IP address and a little memory, not power.

How to set it up. Connect your home server to the VPS with WireGuard. Then either reach your home server through the VPN from your own devices, or, if you must make a service public, put a reverse proxy on the VPS that forwards to it. VPS vs home server covers the trade-offs.

Watch out for. Exposing home services is risky. Prefer VPN-only access. If something must be public, make sure it has a login, keep it updated and turn off open sign-up. Streaming media through the VPS counts against its bandwidth.

10. Private Git repositories

What it is. A place to keep your code, notes or configuration files under version control, without using a hosted service.

Why it suits this plan. Plain Git over SSH needs no extra software running. It uses memory only while you push or pull.

How to set it up. Install Git, create a bare repository with git init --bare ~/repos/project.git, and push to it from your computer using alex@SERVER_IP:repos/project.git as the remote. Web interfaces such as Gitea exist, but use more memory, so check their requirements first.

Watch out for. This is not a backup on its own. Keep another copy elsewhere. Never commit passwords or API keys.

11. A small backup target

What it is. An off-site place to keep copies of small but important files, such as documents, website files or config folders.

Why it suits this plan. Storing backups needs disk, not memory. Backup tools like restic use more memory while they run, but small backups are usually fine.

How to set it up. Create a separate backup user and send encrypted backups to it over SSH. Using a storage VPS for backups has the full steps.

Watch out for. Disk space. Small plans often have small disks, so check how much you have and how fast your backups grow. Test a restore. Do not rely on one copy.

12. A second-location test point

What it is. A server in a different city or country, used to test how your website loads from there, check DNS changes or measure network routes.

Why it suits this plan. Running ping, mtr, curl or dig uses almost nothing. The location matters, not the size.

How to set it up. Pick a location far from your main server. Choosing a VPS location helps. Install the tools with your package manager and run tests by hand or from cron.

Watch out for. Only test your own systems. Heavy or repeated testing of other networks can break the acceptable use policy.

What does not fit

Being honest about this saves you from a frustrating first week.

Job	Why it struggles	Better choice
WordPress or other PHP and MySQL sites	The database alone can use a third of the memory, and visits push it over	Shared hosting, or a 2 GB VPS
Several apps in Docker	Docker and each container add memory overhead	A 2 GB to 4 GB VPS
Game servers	Most need 1 GB or more just to start	VPS for game servers
Self-hosted AI models	Even small models need far more memory	Self-hosted AI on a 4 GB VPS
Your own mail server	Mail software, spam filtering and antivirus use a lot of memory, and running mail well is hard	A hosted email service, or shared hosting email
Control panels	Most web hosting panels need more memory than the whole plan	Shared hosting
Windows	Windows needs far more memory	A Windows VPS

Two more cautions. Unmetered does not mean unlimited: bandwidth and CPU are subject to fair use, and a small plan that runs at full CPU all day may be limited. And swap is a safety net, not extra RAM. A 512 MB plan with swap still behaves like a 512 MB plan.

When to step up

Step up to 1 GB when you want to run two or three of the jobs above at once, add a lightweight dashboard, or keep a small database. Step up to 2 GB for WordPress or a handful of Docker containers. Signs that you have outgrown 512 MB:

• free -h shows swap in use most of the time.
• Programs are killed with "out of memory" messages in the logs.
• The server feels slow even when you are the only user.

Compare the 512 MB and 1 GB plans in the lists on this page, when plans are in stock. For anything beyond one light job, a 1 GB plan can be the better buy.

To compare what is available now, start with the cheapest RackNerd VPS guide and check the sales page.