From Cloud Bills to Home Lab: Why I Bought a $764 Mini PC
How a Beelink GTi13 Ultra replaced my $500/month cloud infrastructure and taught me more about systems than any tutorial
---
The $6,000 Annual Problem
It was September 2024, and I was staring at my AWS bill again.
$487.32 this month.
Not a huge amount in the grand scheme of things, but I ran the numbers: $5,848/year for what was essentially:
There had to be a better way.
---
The Epiphany
The realization hit me during a late-night debugging session: I'm paying AWS to run services that idle 90% of the time.
My "production" workloads were:
Did I really need enterprise cloud infrastructure for this?
I started researching alternatives. The options were: 1. DigitalOcean/Linode - Cheaper, but still ~$200-300/month 2. Raspberry Pi - Too underpowered for my workloads 3. Used server - Loud, power-hungry, overkill 4. Mini PC - Interesting...
That's when I discovered the Beelink GTi13 Ultra.
---
The Decision
Specs that caught my attention:
The math was compelling:
Cloud (1 year): $5,848 Beelink (1 year): $764 + ~$60 electricity = $824 Savings year 1: $5,024 Savings year 2+: $5,788/year
ROI: 1.6 months
But beyond the money, something else drew me in: I wanted to learn systems administration properly.
AWS abstracts so much away. Click a button, get a database. Need more RAM? Slide a slider. Scale? Auto-magic.
I was good at using AWS. I sucked at understanding what it was actually doing.
A home lab would force me to learn:
Skills that would make me a better engineer.
---
The Purchase
October 1, 2024, 8:46 PM. I clicked "Order" on Beelink's website.
Order #33183:
Shipping: 30-35 days (pre-sale order) My excitement level: Through the roof
I told Claude (yes, this AI) about it immediately. The conversation was basically me being like a kid before Christmas.
The 30-day wait felt endless.
---
The Arrival
When the package finally arrived, I tore it open like it was Christmas morning.
First impressions:
Setup took 30 minutes: 1. Unbox 2. Connect power, HDMI, dual ethernet 3. Boot into Windows 11 Pro (pre-installed) 4. Install Proxmox (my choice for virtualization) 5. Start migrating services
---
What I'm Running (Today)
Virtual Machines:
1. PostgreSQL Database Server
2. Development Environment
3. Staging Server
4. Production Web Services
5. Home Assistant
6. Pi-hole
7. Monitoring Stack
8. Tailscale Exit Node
Total resources in use:
Remaining capacity for experiments: Plenty
---
What I Learned
Lesson #1: Cloud is a Convenience Tax
For production services with unpredictable traffic, AWS is amazing. For personal projects and side businesses? Overkill.
My photography business:
Lesson #2: Hypervisors Are Magic
Proxmox (or ESXi, or any hypervisor) is basically:
I broke my development environment 6 times in the first week. Each time: restore snapshot, back to work in 30 seconds.
On AWS, I'd have to: 1. Stop instance 2. Create AMI 3. Launch new instance 4. Update DNS 5. Hope nothing broke
Time saved: Hours → Seconds
Lesson #3: Networking is Fascinating
Having dual 2.5GbE ports unlocked possibilities:
Setup:
Use cases:
I learned more about VLANs, routing, and network security in one month than 3 years of "just use AWS VPC."
Lesson #4: Power Consumption Matters
Beelink GTi13 idle: ~15W Beelink GTi13 loaded: ~55W Average: ~30W
Monthly electricity cost: ~$5
Compare to:
The i9-13900HK is a mobile processor. Designed for laptops. Insanely power-efficient for the performance.
Lesson #5: Backups Are Your Responsibility
AWS spoiled me with:
With a home lab:
My backup strategy: 1. Nightly Proxmox backups to external USB SSD 2. Weekly off-site sync to Backblaze B2 (~$6/month) 3. Critical data replicated to Google Drive 4. Database dumps encrypted and stored remotely
Total backup cost: $6/month vs. $0 on AWS (but built into the $500/month bill)
---
The Unexpected Benefits
1. Learning by Breaking Things
Want to test a risky PostgreSQL configuration change?
I experimented way more because failure was cheap.
2. Interview Talking Points
Interviews changed after I set this up:
Before: "I use AWS for hosting" After: "I run a home lab with Proxmox managing 8 VMs, dual network interfaces for segregated traffic, and automated backup pipelines to cloud storage."
Suddenly I sounded like I knew what I was doing.
3. Always-On Development Environment
My dev environment never sleeps. I can:
4. Real-World Experience
Concepts I now understand deeply:
These are skills that directly translated to my contracting work at BNT.
---
The Downsides (Let's Be Honest)
1. Uptime is Your Problem
AWS promises 99.99% uptime. My home internet? Not so much.
Power outages: Happened twice in 3 months ISP issues: Once (3 hours down) My fault: Breaking something stupid (often)
Solution: Hybrid approach. Critical services (like my photography business payments) still use AWS. Everything else? Home lab.
2. No Auto-Scaling
If gilricardo.com suddenly gets 100,000 visitors (unlikely), my mini PC can't magically add more resources.
Reality: Personal projects rarely need auto-scaling. And if they do? That's a good problem to have.
3. You're the Sysadmin
Something breaks at 2 AM? You fix it.
Hardware failure? You order parts.
Security vulnerability? You patch it.
Trade-off: I wanted to learn this stuff. If you don't, stick with cloud.
4. Limited Off-Site Redundancy
My Beelink lives in Florida. If a hurricane takes out my apartment, my services go down.
Mitigation:
---
The ROI (6 Months Later)
Money saved:
Time invested:
Skills gained:
Value of skills: Priceless (literally landed me interviews)
---
Would I Do It Again?
Absolutely.
But not for everyone. Here's who should (and shouldn't) get a home lab:
✅ You Should If:
❌ You Shouldn't If:
---
The Future of My Home Lab
Phase 1: Current (Complete) ✅
Phase 2: Network Upgrade (In Progress)
Phase 3: GPU Addition (Planned)
Phase 4: High Availability (Maybe)
Total projected investment: ~$2,000 Annual cloud equivalent: $8,000-12,000 Break-even: 3-4 months
---
Technical Specs Deep Dive
For the nerds who want details:
Beelink GTi13 Ultra
CPU: Intel Core i9-13900HK
Memory: 64GB DDR5-5200
Storage: 2TB NVMe (2 × 1TB)
Networking:
I/O:
Power: 120W adapter (65W typical usage)
Cooling: Dual-fan active cooling with vapor chamber
Dimensions: 135mm × 135mm × 51mm
Weight: ~900g
---
Performance Benchmarks
CPU (Geekbench 6):
For reference:
Storage (CrystalDiskMark):
Network (iperf3):
Power Consumption:
Thermals:
---
Lessons for First-Time Home Labbers
1. Start Small
Don't try to replicate your entire production stack immediately.
Week 1: Get hypervisor running Week 2: One VM with your most-used service Week 3: Add monitoring Week 4: Automate backups Month 2: Migrate remaining services
2. Document Everything
You will forget how you configured things.
What I document:
Tool: Simple markdown files in a git repo
3. Test Your Backups
Backups you've never restored are useless.
I learned this the hard way when a VM got corrupted and my backup was incomplete.
Now: Monthly restore drills. Restore a random VM from backup and verify it works.
4. Security Matters
Your home lab is exposed to the internet (if you want remote access). Secure it.
Minimum security:
5. Budget for Extras
Beyond the mini PC, I needed:
Total extra: ~$395
Still cheaper than 2 months of AWS!
---
Resources That Helped Me
YouTube Channels:
Subreddits:
Documentation:
Tools:
---
The Bottom Line
Should you buy a $764 mini PC to replace your cloud infrastructure?
It depends.
If you:
Then yes. The ROI is there, both financially and educationally.
If you:
Then no. Cloud is the right choice.
For me? Best $764 I ever spent.
Six months in:
---
FAQ
Q: Can I really run 8 VMs on a mini PC? A: Yes! With 64GB RAM and proper resource allocation. Most VMs idle at <10% CPU usage.
Q: What happens if it breaks? A: I have off-site backups. Can rebuild anywhere within 4 hours. For critical services, I keep cloud failovers.
Q: Is it loud? A: At idle? Silent. Under load? Barely audible (quieter than a laptop).
Q: Can it handle gaming? A: Integrated graphics are decent for light gaming. For serious gaming, add external GPU via OCuLink.
Q: How's the build quality? A: Solid aluminum, feels premium. No cheap plastic. Well-designed thermals.
Q: Any regrets? A: Should have bought a UPS sooner. And maybe 128GB RAM instead of 64GB (future-proofing).
Q: Would you recommend Beelink? A: Yes. Good balance of performance, price, and features. Customer support was responsive.
---
Where to Buy
Official Beelink Store: https://www.bee-link.com Amazon: Check current pricing
Pro tip: Watch for sales. I got mine during a pre-order special with $5 off (not much, but hey).
Alternatives to consider:
---
About the Author:
Ricardo Gil is a Full Stack Software Engineer who enjoys replacing expensive cloud services with mini PCs. He runs his entire portfolio, photography business, and development environment from a box smaller than a lunch pail. Originally from Venezuela, he immigrated to the US in 2015 and now lives in Dania Beach, Florida with his wife Daniela and his trusty Beelink.
---
Related Posts:
---
This post contains affiliate links. If you purchase through these links, I may earn a commission at no extra cost to you.
Related Posts
Building with Angular + Firebase? Check out my Photography E-Commerce Platform that combines Firebase auth with Stripe payments and AWS S3 storage.
Self-hosting your projects? Learn how I host production apps on a Raspberry Pi with PM2, Nginx, and Tailscale.
About the Author: Ricardo Gil is a full-stack software engineer specializing in .NET/C#, Angular, and cloud platforms. Read more or subscribe for updates.