You’ve scheduled a script. It runs every morning, cleans up a folder, sends a summary — exactly what “real automation” should feel like.
Then you close your laptop to head out, and the script doesn’t run. Nothing sends. The next morning it’s like the automation never existed.
This is the point where a lot of beginners assume they’ve done something wrong. You haven’t. Your laptop simply isn’t built to be a server — it sleeps, it shuts down, it goes offline the moment you disconnect from home Wi-Fi. If you want automation that runs whether or not you’re near your computer, the script needs to live somewhere that’s always on.
This post covers the realistic options for beginners, from free and simple to more capable, so you can pick the right one for what you’re actually automating.
Why “Just Leave Your Laptop On” Doesn’t Really Work
It’s tempting to think the fix is simple: disable sleep mode, leave the laptop plugged in, done.
In practice this runs into real problems fast:
- Laptops aren’t designed to run unattended 24/7 — updates, restarts, and power cuts will eventually break your schedule
- You can’t take your laptop out of the house without your automation going down with it
- Running a laptop constantly for one small script is a lot of overhead for very little benefit
None of this means your automation idea is too ambitious. It means the location is wrong, not the script.
Option 1: A Cheap Cloud Server (VPS)
A VPS (virtual private server) is a small, always-on computer you rent, usually for a few dollars a month. You get a genuine command line, install Python, and your script runs exactly the way it does locally — except the server never sleeps and doesn’t care if your laptop is closed.
Good for: scripts that need to run reliably on a schedule, indefinitely, with minimal fuss.
What to expect: a short one-time setup (connecting to the server, installing Python, copying your script over, setting up a schedule), then it mostly runs itself. This is the most beginner-friendly path into “always-on automation” because it behaves like a normal computer you already understand.
Option 2: A Raspberry Pi at Home
A Raspberry Pi is a small, cheap physical computer you can plug in at home and leave running. It draws very little power, so leaving it on permanently is realistic in a way a laptop isn’t.
Good for: automations tied to your home network or devices — things a cloud server can’t easily reach, like anything interacting with local files, printers, or smart-home devices.
Trade-off: it depends on your home internet and power staying up. If your Wi-Fi drops or there’s a power cut, so does your automation — unlike a cloud server, which lives somewhere professionally maintained.
Option 3: A Free-Tier Cloud Function
Cloud providers offer “serverless” options where you upload just your script, and the provider runs it on their schedule — you never manage a server at all.
Good for: simple scripts that run briefly and don’t need to stay running constantly (e.g., “check something every hour and send an alert” rather than “watch a folder continuously”).
Trade-off: free tiers usually cap how often or how long your script can run, and the setup has a slightly steeper learning curve than a VPS since you’re working within the provider’s specific format rather than a normal terminal.
Which One Should You Actually Pick?
A simple way to decide:
- Script needs to run on a schedule, indefinitely, and you want the most beginner-friendly path → VPS
- Script needs to interact with something physically at home → Raspberry Pi
- Script is short, occasional, and you don’t want to manage a server at all → free-tier cloud function
Most beginners get the fastest, least frustrating result starting with a VPS — it’s the closest thing to “the same computer you already know how to use, except it never turns off.”
A Realistic First Setup (VPS Path)
If you go with a VPS, the beginner path looks roughly like this:
- Rent a small, cheap VPS from any mainstream provider
- Connect to it and install Python
- Copy your existing script over
- Set up the same scheduling approach you used locally, but on the server
- Add basic logging so you can check in on it remotely rather than needing to watch it run
None of these steps requires deep server administration knowledge — it’s closer to “set it up once carefully” than “become a sysadmin.”
FAQ
Do I need to know Linux to use a VPS? A little basic comfort with the command line helps, but you don’t need deep Linux knowledge to get one script running reliably. Most of what you need is copy-paste setup the first time, then it runs itself.
Is a Raspberry Pi cheaper than a cloud server long-term? The hardware is a one-time cost, so it can work out cheaper over a long period — but it depends on your home internet and power staying reliable, which a professionally hosted server doesn’t.
Can I test this before committing to a paid server? Yes — free-tier cloud functions or a free trial on most VPS providers are both reasonable ways to try the always-on approach before spending anything.
What to Do Next
Getting your script scheduled was step one. Getting it running somewhere that’s always on is what turns it from “a script I run” into “a system that works without me” — which is exactly the shift this guide is built around.
The full From Zero to Automated guide walks through this in more depth, including how to keep automations reliable once they’re live and what to do when something goes wrong while you’re not watching.