Verifiable system state
The system should be able to explain what it is supposed to be and whether the observed machine still matches that declaration.
RuddBSD is an independent, maintainer-led, security-focused operating system built on FreeBSD, centered on verifiable system state, controlled transitions, strict policy, evidence-backed builds, VM-first validation, and Rust-powered trusted tooling.
Current state
RuddBSD is under active private pre-release development. There is no public installable release yet. The first Developer Preview will be published only after the required build, boot, installation, and evidence-validation gates are satisfied.
Architecture
RuddBSD builds on the FreeBSD base rather than hiding it, adding a focused product layer for verifiable state, controlled change, policy enforcement, and evidence-backed operations.
The system should be able to explain what it is supposed to be and whether the observed machine still matches that declaration.
Meaningful changes are designed to be planned, reviewed, policy-checked, applied transactionally, and recorded as evidence.
Build and release claims are separated from assumptions. RuddBSD aims to claim only what its collected evidence can substantiate.
Boot and installation behavior is validated in controlled virtual environments before stronger artifact claims are made.
Profiles define deliberate operating environments with explicit expectations around packages, services, configuration, and policy.
Rust is used where memory safety matters most: verification, policy, evidence processing, and RuddBSD-owned trusted tooling.
Root of trust
This website is the authoritative source for RuddBSD accounts and contact addresses. If an account is not listed here, do not assume it represents the project.
Canonical project identities linked from ruddbsd.org. Additional accounts appear here only after they are established.
RuddBSD is an independent, maintainer-led operating system project. Core development is currently private while the architecture and release process are being established. Public testing, bug reports, and selected contributions will be introduced later, while architectural direction and official releases remain centrally maintained to preserve the project’s security, verifiability, minimal upstream divergence, and evidence-backed design principles.
Security reporting
Please report vulnerabilities privately rather than publishing them as general project discussion.