Proxmox for Small Business: How We Use It and How You Can

Most small offices still run one aging server in a closet: a file share, an accounting app, maybe a domain controller, all on a single machine with a single point of failure. Proxmox for small business is how we’d replace that box today. It’s what Rainier IT runs on, and it gives a small office the same tools the big shops use without the big licensing bill.

What Proxmox is, in plain English

Proxmox Virtual Environment turns one or more physical servers into a pool that runs many smaller machines. It combines two kinds:

• Virtual machines (KVM) for full operating systems such as Windows Server or a line-of-business app that needs its own computer.
• Containers (LXC) for light Linux services such as a website, a wiki or a monitoring tool.

Everything is managed from a web page. Several servers can join a cluster, and with high availability a machine on a failed server restarts on a healthy one. Storage can be local disks with ZFS, which checks your data for silent corruption, or Ceph spread across servers.

It’s open source under the GNU AGPL, so there is no per-core license to buy. A paid subscription adds the vendor’s enterprise update channel and support, and for a business we recommend one. The free channel is meant for testing, not production.

Its partner, Proxmox Backup Server, makes incremental, deduplicated backups of every machine, with encryption and integrity checks.

How we run Proxmox at Rainier IT

We don’t sell anything we don’t run ourselves. Our own infrastructure is a cluster of Proxmox VE 9.2 servers, and almost everything you touch when you work with us lives on it:

• Containers host our website, this blog (WordPress), our knowledge base, our password vault and our monitoring stack.
• Virtual machines host the client portal, the ticket system and our remote management server.
• A graphics card passed straight through to one virtual machine runs our local AI workloads, so that work never leaves the building.
• A warm-standby copy of our internet-facing proxy sits in a container on a second server, ready if the main one fails.
• Every machine is backed up nightly to Proxmox Backup Server, and the backups are verified every week. Verification means the server reads each backup back and confirms it’s intact.

Backups also make testing safe. Before we upgrade our remote management server, we restore last night’s backup into a separate staging copy and upgrade that first. If something breaks, it breaks there, not in production.

None of it is managed by hand. Ansible playbooks in Git describe how each server should look, and Jenkins runs them on a schedule to patch, check certificates and confirm every host is healthy. Prometheus and Grafana watch it all and alert us when something drifts.

Where Proxmox for small business fits

Here’s where it makes sense for a small office:

• Replacing the closet server. One modern server, or a pair of quiet mini PCs, runs the file server, the accounting app and the domain controller as separate machines. A problem in one doesn’t take down the others.
• Moving off another hypervisor. Proxmox includes an import tool for VMware ESXi machines, so a migration doesn’t mean rebuilding from scratch.
• Keeping data on-site. Some practices, such as dental and medical offices, want patient files under their own roof. Local servers plus tested off-site backups cover that.
• A safe place to test. Clone a machine, try the software update, throw the clone away.
• Backups you can restore in minutes. A whole machine comes back from Proxmox Backup Server, not just a folder of files.

It’s not the right fit for everyone. If your apps already live in Microsoft 365 and nothing runs in the office, you may not need a server at all.

Cloud redundancy and failover on AWS

On-site servers are fast and private, but one building is still one building. That’s why we pair Proxmox with Amazon Web Services (AWS). Our AWS environment is built the same way as everything else here: in code, with Terraform. It has separate accounts for management and production, single sign-on, organization-wide audit logging and threat detection, and a private network spread across three availability zones in Oregon, ready to carry standby workloads.

We’re building on that foundation now. Next are off-site copies of our Proxmox backups in AWS storage that locks each copy against changes or deletion for a set period, so ransomware can’t reach them. After that comes warm-standby hosting that can take over websites and key services if the office goes dark. The same pattern scales down for a small business: local servers for daily work, an AWS copy for the bad day.

What we build: infrastructure, code and the web

This is the work we do for small businesses around Pierce County:

• Infrastructure. We design, install and look after Proxmox servers sized to your office, from a single host to a small cluster. We also migrate old servers and other hypervisors onto them.
• Infrastructure as code. We describe your servers, settings and patching in code (Ansible, and Terraform for cloud resources) and keep it in version control. That gives you documentation that’s always current, changes we can review before they happen, and a rebuild that follows a script instead of someone’s memory.
• Backups and recovery. Proxmox Backup Server on-site, a copy off-site, and restores we actually test. See backup and recovery.
• Cloud redundancy. An AWS landing zone built in Terraform, with off-site backup copies and standby hosting for the services you can’t be without. See cloud services.
• Monitoring and patching. The same alerting and scheduled updates we use on our own servers, run for you as part of managed IT.
• Web. We design and host websites for local businesses on infrastructure like ours. See web design.
• Security. Hardened hosts, a firewall on every machine, and endpoint protection through our security services.

What to do this week

• Find your server and write down what runs on it and how old it is.
• Check when your last backup was, and whether anyone has ever restored from it.
• List which apps must stay in the office and which could move to the cloud.
• Ask us for a free look before the old server makes the decision for you.

If you’d like a second set of eyes on your setup, book our free 30-minute assessment. We’ll tell you whether Proxmox, the cloud or a mix fits your office best.

This article was drafted by Percival, Rainier IT’s AI writing assistant, from the sources linked above, and reviewed by Christopher Engelhardt before publication. Spot an error? Email [email protected].