My £5 Per Month Server Is Running Five Income Streams — Here Is How
When I tell people that my entire automated investment operation runs on a server costing less than a fancy coffee each month, they usually assume I am exaggerating. I am not. Right now, as you read this, a tiny virtual computer sitting in a London data centre is quietly managing my portfolio rebalancing, tracking dividends, scanning for arbitrage opportunities, generating content, and keeping itself maintained — all for exactly £5 per month.
This single server is the backbone of PocketBots. It runs twenty-four hours a day, seven days a week, and it has transformed what would have been hours of manual work into something that happens automatically while I sleep, eat, or spend time with family. Today I want to pull back the curtain and show you exactly how this works, because I genuinely believe anyone can set up something similar in under an hour.
What Is a VPS Server in Plain English
Before we dive into the specifics, let me explain what a VPS actually is, because the terminology can be intimidating if you have never encountered it before.
VPS stands for Virtual Private Server, but that does not really tell you much. Here is how I explain it to friends: imagine a massive, powerful computer sitting in a secure, climate-controlled building somewhere. That computer is so powerful that it can be split into dozens of smaller, independent computers — each one completely separate from the others, each one with its own operating system, its own storage, and its own resources.
When you rent a VPS, you are essentially renting one of these smaller virtual computers. It is like having your own personal computer that never turns off, never loses its internet connection, and sits in a professionally managed facility with backup power and security you could never afford at home.
The beauty of this arrangement is that you do not need to worry about hardware failures, electricity bills, or your home broadband going down at a crucial moment. Your little rented computer just keeps running, executing whatever tasks you have set up for it.
Why I Chose DigitalOcean
There are dozens of VPS providers out there — Amazon Web Services, Google Cloud, Linode, Vultr, and many others. After trying several over the years, I settled on DigitalOcean for PocketBots, and I have never looked back.
The reasons are straightforward. First, the setup process is genuinely simple. When I say you can have a server running in under an hour, I mean it — and most of that time is spent configuring your bots, not wrestling with the hosting platform. DigitalOcean’s interface is clean and intuitive, designed for people who want to get things done rather than navigate endless menus of enterprise options.
Second, they have a London data centre. This matters because my bots interact with UK financial services and markets. Having the server physically located in London means lower latency and faster response times when connecting to UK-based APIs. It also means my data stays within a jurisdiction I understand.
Third, the pricing is transparent and predictable. The £5 per month plan (they call it a Droplet) gives you exactly what you need for running automated bots, with no hidden costs or surprise charges. What you see is what you pay.
Finally, reliability has been excellent. In over a year of running PocketBots on DigitalOcean, I can count the minutes of unexpected downtime on one hand. For something managing my investments, that reliability is non-negotiable.
If you want to try it yourself, you can use my referral link at https://m.do.co/c/4fbd00f5fabd which gives you free credit to get started — enough to run a server for a couple of months while you experiment.
The Exact Server Specification
Let me be completely transparent about what I am running. My server has the following specifications:
- Operating System: Ubuntu 22.04 LTS
- RAM: 1GB
- CPU: 1 vCPU
- Storage: 25GB SSD
- Monthly Cost: £5
If you know anything about computers, those specs probably look modest. One gigabyte of RAM is less than most smartphones have these days. But here is the thing that took me a while to truly understand: running automated bots is not like running video games or editing video. Bots spend most of their time doing absolutely nothing, waiting for their scheduled moment to spring into action.
When a bot does run, it typically needs to make a few API calls, do some calculations, maybe update a database, and then go back to sleep. This takes seconds, not hours, and uses a tiny fraction of the available resources. The server spends 99% of its time essentially idle, ready and waiting for the next scheduled task.
Ubuntu 22.04 LTS is the operating system of choice because it is stable, well-supported, and has a long-term support window that means I do not need to worry about major upgrades for years. It is also what most tutorials and documentation assume you are using, which makes troubleshooting much easier.
What Actually Runs on This Server
This is where things get interesting. Here is the complete list of what my £5 server handles:
Portfolio Rebalancer — Monday at 9am
This bot analyses my investment portfolio, compares current allocations against my target percentages, and either executes rebalancing trades automatically or sends me a detailed recommendation. It connects to my broker’s API, pulls current positions, runs the calculations, and takes action — all in about thirty seconds.
Dividend Tracker — Monday at 10am
One hour after rebalancing, the dividend bot wakes up. It checks for any upcoming dividend payments, logs historical dividend data, calculates yield trends, and updates my tracking spreadsheet. This helps me understand the passive income my portfolio generates without manually checking dozens of holdings.
Arbitrage Scanner — Every 5 Minutes
This is the most active bot. Every five minutes, around the clock, it scans for price discrepancies across different platforms. When it spots an opportunity above my threshold, it alerts me immediately. Most scans find nothing interesting, but when they do, the speed matters.
Content Bot — Monday at 8am
Before the financial bots even start their Monday routine, the content bot has already been working. It analyses market data, generates insights, and prepares content drafts that I can review and refine. This saves me hours of research and writing time every week.
Maintenance Bot — Daily at 7am
Every morning at 7am, this bot runs system health checks, clears temporary files, rotates logs, checks disk space, and sends me a brief status report. If anything looks concerning, I know about it before it becomes a problem. Think of it as a daily health check-up for the server itself.
How Cron Jobs Work — Your Server’s Built-In Alarm Clock
The magic that makes all this scheduling possible is something called a cron job. If you have never heard of cron before, here is the simplest explanation I can offer: it is an alarm clock for your code.
Just like you might set an alarm on your phone to wake you up at 7am, you can set a cron job to run a script at any time you specify. Want something to run every Monday at 9am? There is a cron expression for that. Every five minutes? Easy. First day of every month at midnight? No problem.
The syntax looks intimidating at first — it uses five numbers to represent minute, hour, day of month, month, and day of week — but there are free online tools that generate the correct expression for you. You just select when you want something to run, copy the expression, and paste it into your server’s cron configuration.
Once set up, cron jobs run with absolute reliability. They do not forget, they do not oversleep, and they do not get distracted. At exactly the moment you specified, your code executes. This reliability is what makes automated investing actually work.
Managing a Server From Your Phone With Termius
One concern people often raise is whether managing a server requires sitting at a desktop computer. The answer is no, and this surprised me when I first discovered it.
I use an app called Termius on my phone. It is a mobile SSH client, which means it lets me connect to my server securely from anywhere with an internet connection. If a bot encounters an issue while I am out for dinner, I can pull out my phone, connect to the server, check the logs, and fix the problem — all from the restaurant table.
Most of the time I do not need to do this because things run smoothly, but knowing I can intervene instantly from anywhere gives me peace of mind. The app stores my server credentials securely and connects in seconds. It has genuinely changed how I think about running remote infrastructure.
The Numbers That Still Amaze Me
After running this setup for months, I regularly check resource usage because I find it fascinating. Here is what I typically see:
- RAM Usage: Around 200MB out of 1024MB available — roughly 20%
- CPU Usage: Negligible most of the time, brief spikes when bots run
- Disk Usage: About 8GB out of 25GB — plenty of room for growth
This means my server is running at a fraction of its capacity. I could easily add more bots, more complex operations, or more frequent scans without coming close to the limits. The £5 plan is genuinely more than enough.
Let that sink in for a moment. For less than the cost of a single sandwich at Pret, I run a fully automated investment operation every single month. Over a year, that is £60 total. The bots have already generated returns that make that cost look almost irrelevant — but even if they had not, the time savings alone would justify the expense many times over.
Your Quick Start Guide — Server Running in Under an Hour
If you want to set up your own server, here is exactly how to do it:
- Create a DigitalOcean account using this referral link to get free starting credit.
- Click Create Droplet from your dashboard once logged in.
- Select Ubuntu 22.04 LTS as your operating system from the available options.
- Choose the London data centre (listed as LON1) for UK-based operations.
- Select the £5 per month plan — the basic Droplet with 1GB RAM, 1 vCPU, and 25GB SSD.
- Set up SSH authentication — DigitalOcean will guide you through creating a secure key pair.
- Click Create Droplet and wait about sixty seconds for your server to provision.
- Connect via SSH using Terminal on Mac, Command Prompt on Windows, or Termius on mobile.
- Install Python and required packages using apt-get and pip commands.
- Upload your bot scripts to the server using SCP or an SFTP client.
- Configure cron jobs by running crontab -e and adding your schedule expressions.
- Test everything manually first before relying on scheduled execution.
The entire process genuinely takes under an hour if you follow these steps methodically. The first time I did it, I was