I Tried to Build My Own Cloud at Home and Almost Lost My Mind – Ocheverse

At some point in every engineer’s life, a dangerous thought appears:

“What if I just… built my own cloud?”

Not AWS.
Not Azure.
Not some overpriced VPS.

My own.
In my house.
With my electricity.
And my router.

So I bought a Lenovo ThinkCentre, brought it home, plugged it in, and said:

“Let’s cook.”

Reader.

We did not cook.

The kitchen caught fire.

The Dream

I wanted a server that I could:

SSH into from anywhere
Deploy apps on
Expose to the internet
Not pay AWS for
Feel like a real cloud engineer using real hardware

Basically…

I wanted to feel powerful.

The Hardware

I bought a Lenovo ThinkCentre with:

1TB SSD
8GB RAM
Intel CPU
Ethernet port (important, you’ll see why)

Small box. Silent. Cute. Unassuming.

This box was about to ruin my week.

Proxmox: The First Betrayal

Naturally, I wanted to start like a serious engineer.

So I said:

“Let’s install Proxmox. Datacenter vibes.”

What followed:

BIOS fighting me
UEFI vs CSM beef
EULA button disappearing like my motivation
PXE boot loops
ATA bus errors
Disk refusing to cooperate

At some point Proxmox basically said:

“You’re not that guy.”

And I replied:

“Okay.”

So I pivoted.

Ubuntu Server: The Peace Treaty

I installed Ubuntu Server.

No drama.
No attitude.
No nonsense.

Just:

“Hello. I am a server. Let’s work.”

I felt safe again.

Networking: The ZTE Router Arc

Ubuntu booted.
Ethernet connected.
Router gave it an IP.
Life was good.

Until I rebooted.

And the IP changed.

And my server disappeared.

So I went full network engineer:

Scanned my LAN like a hacker
Found the MAC address
Logged into my ZTE router
Created a DHCP reservation
Locked the IP forever

Now my server lives at:

192.168.1.200

Like a respected elder.

The 1TB That Was Actually 100GB

Ubuntu looked at my 1TB disk and said:

“I will use 100GB. The rest is vibes.”

Turns out LVM did a magic trick and hid my storage.

So I expanded it and reclaimed my disk like a landlord.

Now I have my full 1TB.

As God intended.

Making My Server Public Without Letting the Internet Touch It

I wanted my apps online.

But I didn’t want:

Port forwarding
Bots scanning my IP
Random Russians knocking on port 22
My router becoming a public API

So I chose peace.

I used Cloudflare Tunnel.

Which is basically Cloudflare saying:

“Don’t worry bro, I’ll stand in front.”

Instead of the internet talking directly to my server, my server creates an outbound tunnel to Cloudflare, and Cloudflare routes traffic back in.

So now I get:

https://app.mydomain.com → localhost:3000

With:

HTTPS by default
Zero open ports
No public IP exposure
No router config
No stress

My server talks out.
The internet never talks in.

Reverse Uno card.

What I Ended Up With

At the end of this madness, I now have:

A physical server in my house
1TB of usable storage
Permanent IP on my LAN
SSH access from anywhere in the world
Public HTTPS apps
No port forwarding
No cloud bills
No vendor lock-in

I built my own cloud.

In my bedroom.

With a ZTE router and vibes.

Things This Journey Taught Me

BIOS is the real final boss
Datacenter installers hate TVs
Proxmox is not your mate
Ubuntu Server just wants to help
Routers run the real world
DHCP reservations are elite tech
LVM is a magician
Owning hardware humbles you
Homelabs make you dangerous
The cloud is just someone else’s computer and now I have my own

The Real Flex

Anyone can deploy to AWS.

Not everyone can:

Debug ATA bus errors
Fight UEFI firmware
Recover missing storage
Design home IPAM
Run zero-trust tunnels
Build infra from scratch

This is where engineers are forged.

Final Words

If you’re an engineer and you don’t have a homelab yet, you’re missing out.

Not because it’s fun (it’s stressful).
Not because it’s easy (it’s not).

But because it teaches you how things really work.

And once you build your own cloud…

You’ll never look at AWS the same way again.

I Tried to Build My Own Cloud at Home and Almost Lost My Mind