The Stack That Runs Tayozola

People sometimes assume a managed service is just a reseller — a thin layer over someone else's giant cloud. Tayozola isn't that. We run the infrastructure ourselves, on hardware we own, with a small set of tools we trust. Here's the short tour.

We didn't try to invent the pieces. We picked dependable ones and took responsibility for running them well.

Proxmox — the machines

Proxmox is what turns our physical servers into the virtual machines you actually use. When you get a Windows 11, Mint Linux, or macOS workspace, Proxmox is what's provisioning and isolating it underneath. It's open, well-proven, and it keeps each member's machine cleanly separated from everyone else's.

Synology — the storage and backups

Your files live on Synology storage. It's also where our backups run — nightly snapshots that make "design for recovery" a real thing rather than a slogan. If something goes wrong, the question we want to answer is "which version do you want back," not "is it gone."

Cloudflare — the front door

Everything you reach — the dashboard, sign-in, email, this journal — comes through Cloudflare. It handles the network edge: routing, protection against the noisy traffic of the open internet, and keeping the sites fast wherever you are. It's the layer that lets a small team serve things reliably at a distance.

Ubiquiti — the network

Behind all of it is the actual network the hardware sits on, built on Ubiquiti gear. It's the unglamorous part nobody sees until it fails — so we'd rather it be steady and boring.

Why run it ourselves

Owning the stack is more work than renting someone else's. We do it because it's the only honest way to make the promises we care about: that your machine is really isolated, that your data stays on our network, that ZOLA runs locally, and that when something breaks there's a specific person who can go fix it.

We'll go deeper on individual pieces in future posts — starting with how the backups actually work.