March 01, 2025 • Moose Labs
A look at our experiences operating the DN nodes on FreeBSD during cohort two.
Running Polkadot validators well is mostly a discipline problem. The node software needs predictable resources, fast storage, stable networking, good observability and operators who treat upgrades as routine engineering rather than occasional heroics. FreeBSD fits that mindset for us.
During DN cohort two we continued operating our Polkadot nodes on FreeBSD. That is still unusual in an ecosystem where most validator guides and automation assume Linux, but the tradeoff has been worthwhile for our infrastructure. The base system is coherent, upgrades are explicit and the separation between the operating system and installed packages makes production changes easy to reason about.
The main work is not getting a node to start. It is making sure the whole lifecycle is boring: building and testing releases, rolling out client updates, keeping kernel and package changes under control, watching disk growth, monitoring peer health and making restart behaviour predictable after maintenance. We keep those tasks documented because repeatability matters more than individual memory.
FreeBSD has also been a useful way to add operating-system diversity to the validator set. Diversity is often discussed in terms of geography or hosting provider, but software diversity matters too. Different kernels, service managers and packaging assumptions reduce the chance that every operator hits the same failure mode at the same time.
There are real costs. Some upstream tooling expects Linux paths, Linux service managers or Linux-specific observability defaults. We prefer to solve those gaps in small, boring pieces rather than maintain a large custom platform. When a change is specific to our environment, we keep it visible and easy to audit.
The result is a validator setup we understand deeply and can operate confidently. DN cohort two gave us a public setting to keep proving that FreeBSD is a practical home for Polkadot infrastructure, provided the operator is willing to own the details.