Why BSD & Unix?

The Short Answer

BSD and Unix systems have decades of production pedigree, a cleaner separation between base and ports, and tooling that was designed for correctness first. FreeBSD powers Netflix's CDN, PlayStation Network, and parts of WhatsApp's infrastructure. OpenBSD has the strongest default security posture of any OS. Illumos (the Solaris fork) is where ZFS and DTrace were born. These aren't hobby OSes.

That said, BSD isn't the answer for everything. We'll tell you when Linux (Ubuntu Server, Fedora Server) is the right fit for your workload.

FreeBSD: Stability and Production Pedigree

FreeBSD has been in continuous development since 1993. Its base system (kernel, libc, userland utilities) ships as a cohesive unit, so you get a stable, well-tested combination rather than a kernel bolted to independently-versioned packages. The ports and packages system gives you access to a large software catalog without pulling from 40 different upstreams.

Notable production deployments: Netflix uses FreeBSD for their open-connect CDN appliances. Sony uses FreeBSD as the foundation of the PlayStation operating system. WhatsApp (before Meta) ran FreeBSD for most of its infrastructure.

The bhyve hypervisor is built directly into the FreeBSD kernel: mature, lightweight, and well-integrated with Jails for a hybrid container/VM model that predates modern Linux container ecosystems by years.

OpenBSD: Security by Default

OpenBSD's design philosophy is "secure by default." The project has a multi-decade track record: only two remote vulnerabilities in the default install in over 25 years. The team invented pf, the packet filter that pfSense, OPNsense, and many appliances are built on.

OpenBSD is the right choice when the attack surface matters above all else. It's not the fastest; it's not the most feature-rich. It's the most conservative, and for firewalls, VPN gateways, and hardened services, that conservatism is a feature.

Illumos & OmniOS: ZFS and DTrace at Home

Illumos is the open-source fork of OpenSolaris, maintained by a community that includes the original Solaris engineers. Two technologies that came out of Sun Microsystems and live most naturally on Illumos: ZFS (the filesystem) and DTrace (the dynamic tracing framework for deep production diagnostics).

OmniOS CE (Community Edition) is a production-grade Illumos distribution with a small, security-focused footprint. For ZFS-native storage servers (replication, deduplication, cryptographic checksumming, snapshot-based backup), OmniOS on appropriate hardware is a strong first choice.

OpenZFS: Why the Filesystem Matters

ZFS is a copy-on-write filesystem that checksums everything. Every read verifies data integrity. Silent corruption (the kind that eats backups and isn't discovered until restoration fails) is detected and corrected automatically with redundant vdevs.

Key properties:

• Atomic snapshots with zero performance overhead at creation
• Send/receive for efficient replication to remote hosts
• Compression built-in (lz4, zstd), often faster than no compression because reads are smaller
• Datasets with individual quotas, inherited properties, and mount options
• RAID-Z (1/2/3): analogous to RAID 5/6 but without the write hole

ext4, XFS, and btrfs are good filesystems. ZFS is in a different category for environments where data integrity and replication strategy are first-class concerns.

pf, pfSense, and OPNsense: The Network Stack

pf (packet filter) originated in OpenBSD and spread to FreeBSD and the BSDs generally. pfSense and OPNsense are FreeBSD-based firewall/router distributions built on pf. They power a significant fraction of small business and homelab networks worldwide.

The pf rule syntax is clear and auditable. Stateful filtering, NAT, traffic shaping, and CARP for high-availability failover are all well-supported. If you're running a pfSense/OPNsense appliance, you're already in the BSD ecosystem. You might not know it.

When Linux or Windows Is the Right Answer

BSD isn't religious dogma. Linux (Ubuntu Server, Fedora Server, Debian, RHEL) is the right answer when:

• Your team already knows it and the switching cost outweighs the benefit
• A specific application only supports Linux (containerized workloads, certain GPU compute)
• You need the broadest hardware driver support for cutting-edge hardware
• Your client or employer mandates it

Windows Server and Windows 10/11 workstations are also fully supported. Many businesses run mixed environments — BSD or Linux on the server side, Windows on the desktop — and that's a completely normal setup we work with regularly.

The goal is matching the right tool to the requirement, not proving a point.

The Practical Takeaway

If you're building infrastructure with longevity in mind, want to understand what you're running, and care about data integrity and security posture, BSD and Unix tooling deserves serious consideration. It won't be in every news article about cloud-native architecture. That's partly why it's still standing.