From Zero to Own Server
How I saved $40/mo building my infrastructure on Oracle Cloud
Working with professional automation tools (n8n, Typebot, WhatsApp APIs) requires infrastructure that most shared hosting plans simply cannot deliver. Anyone who has tried running n8n on a standard "cPanel" knows the struggle: slowness, constant crashes, and memory limits.
The obvious solution would be to rent a robust VPS (Virtual Private Server) on DigitalOcean or AWS. But to get a machine with 4 CPUs and 24GB of RAM, the bill would easily exceed $40 or $50 per month. For those starting out or scaling an operation, this fixed cost adds up.
That's when I decided to accept a challenge: Build an "Enterprise-level" infrastructure spending exactly $0.00.
Sounds too good to be true? I thought so too. But then I discovered the Oracle Cloud Always Free Tier.
The Dream Setup (For Free)
Unlike other providers that offer "free trials" for 30 days, Oracle offers (if you can snag a spot) an ARM Ampere machine with up to 4 OCPUs and 24GB of RAM forever. Even when that machine is unavailable, we can use AMD Micro instances, which are modest but perfect for validating test environments and running lightweight services via Docker.
In this new technical journey, I migrated my automations there and achieved:
Pure Docker: Total control over versions and containers.
Self-hosted n8n: No execution limits.
Evolution API v2: Professional WhatsApp integration.
Cloudflare Tunnel: The icing on the cake. I achieved secure HTTPS and external access without opening a single port on the firewall or exposing the server IP.
It's Not All Roses: The Challenges
I won't lie: it's not "click and install." Leaving the comfort zone of ready-made hosting requires getting your hands dirty in the terminal. We had to deal with SSH keys, Linux file permissions, Swap configuration (virtual memory), and YAML files that don't forgive a single misplaced space.
But the result is worth it. I now have a server that is mine, secure, and extremely performant.
Follow the Series
Over the coming weeks, I will document the technical step-by-step of this implementation here on the blog. If you want to learn how to set up your own automation server with no licensing costs, stay tuned.
Next Thursday, I will explain the first critical step: How to create the account, generate security keys, and access the server without getting locked out.
See you there!
