FreeBSD on a Dedicated Server: Install Paths, Hardware and ZFS Notes

Running FreeBSD on a dedicated server in 2026 is easier than its reputation suggests: the two current lines are 14.4 (the conservative choice) and 15.1 (first of the new 4-year support branches), and there are exactly two realistic ways to get either onto rented hardware — a provider install template, or your own ISO through IPMI/KVM. The real decision happens earlier, when you pick the hardware: FreeBSD's driver story rewards boring server NICs and punishes budget desktop boards. Here is the whole path, from choosing the box to a ZFS-on-root system you can trust.

Choosing hardware FreeBSD actually likes

FreeBSD's kernel supports far less exotic hardware than Linux, but what it supports, it supports deeply. For a rented dedicated box the checklist is short:

• NIC is the make-or-break item. Intel server NICs (igb, ix/ixgbe families) are first-class citizens. Budget boards with Realtek chips mostly work via re, but with more interrupts, less offloading and occasional firmware oddities — on a remote machine you cannot walk over to, prefer Intel.
• Server platforms over desktop boards. Xeon E3/E-series and EPYC lines ship with ECC RAM and Intel networking as standard — the Xeon-E and Xeon-D configs from $33–59/mo in our catalog are exactly this profile.
• Two disks minimum if you want ZFS redundancy. A 2 × NVMe or 2 × SATA box turns into a ZFS mirror in the installer with zero extra work.

Install path 1: provider template

Large wholesale platforms (OVH and Scaleway among them — both behind lines we resell) offer FreeBSD as a stock install template alongside the Linux images. You pick the OS in the panel, the automation images the disks, and you get SSH credentials — same flow as a Debian install, usually done in minutes. This is the fastest route and the right one if the offered version matches what you want.

Its limits: template catalogs lag releases (expect 14.x before 15.x appears), partitioning choices are whatever the template ships, and some templates default to UFS rather than ZFS. Check before ordering; reinstalling later through path 2 is always possible.

Install path 2: your ISO over IPMI/KVM

On machines with IPMI or a KVM console (most of our stock exposes one — HTML5 where the BMC supports it, Java JNLP on older boards) you mount the official FreeBSD installer ISO as virtual media, boot from it, and install exactly as you would on physical hardware in front of you. This gives you any version including 15.1 on day one, full control of partitioning, geli encryption if you need it, and ZFS-on-root configured your way.

Two practical notes from doing this on rented machines:

• Configure networking before you close the console. Rented boxes use static addressing; put the IP, gateway and resolver into /etc/rc.conf and /etc/resolv.conf and verify sshd_enable="YES" — the classic failure is rebooting into a perfectly healthy, unreachable system.
• Gateway-on-another-subnet is normal at hosting providers. If the gateway is outside your /32-ish netmask, the rc.conf idiom is a host route first: static_routes="gw", route_gw="-host GATEWAY -interface igb0", then defaultrouter="GATEWAY".

ZFS sizing without the folklore

ZFS-on-root from the stock installer is the right default for a dedicated box: snapshots before every upgrade, zfs send as your backup transport, and checksums that actually detect silent disk trouble. The RAM folklore ("1 GB per TB or else") overstates it — the honest version:

• 8 GB RAM runs ZFS comfortably for general workloads; ARC simply adapts. More RAM = more cache, not more safety.
• ECC is not mandatory but is cheap insurance on a filesystem built around checksums — and server-grade rentals include it anyway.
• Only deduplication has brutal RAM demands; leave it off, use compression=zstd, and you get most of the win for free.

What you get that Linux boxes do not

The reasons people put FreeBSD on real hardware in 2026 are specific: jails for OS-level isolation with near-zero overhead (and vnet jails with their own network stacks), bhyve for the occasional Linux or Windows guest, pf with its readable rule syntax for firewalling, and a base system + ports model where the OS upgrades as one coherent unit via freebsd-update. A single dedicated box with jails covers what would otherwise be a small fleet of VPSes — which is exactly why FreeBSD users prefer dedicated: no cloud-image catalog lottery, no virtio corner cases, and the disks ZFS manages are real disks with honest error reporting.

Bottom line

Pick a server-platform config with Intel networking and two disks, take the provider template when its version suits you, and keep the IPMI/ISO route in your pocket for everything else. If you are still choosing between form factors, our FreeBSD on VPS guide covers the virtualized side of the same decision. Versions and paths verified July 6, 2026.