PRE-RELEASE DEVELOPMENT

Verifiable by design.

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

Development is active. Public releases are not.

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.

RuddBSD intentionally does not publish release claims before the evidence required for those claims has been satisfied.
DevelopmentActive
Public releaseNone yet
Installable artifactNot published
GovernanceMaintainer-led

Architecture

Trust should be explainable.

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.

01

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.

02

Controlled transitions

Meaningful changes are designed to be planned, reviewed, policy-checked, applied transactionally, and recorded as evidence.

03

Evidence-backed builds

Build and release claims are separated from assumptions. RuddBSD aims to claim only what its collected evidence can substantiate.

04

VM-first validation

Boot and installation behavior is validated in controlled virtual environments before stronger artifact claims are made.

05

Strict system profiles

Profiles define deliberate operating environments with explicit expectations around packages, services, configuration, and policy.

06

Rust at trust boundaries

Rust is used where memory safety matters most: verification, policy, evidence processing, and RuddBSD-owned trusted tooling.

INTENDEDWhat the operator wants.
DECLAREDWhat policy has accepted.
APPLIEDWhat RuddBSD changed.
OBSERVEDWhat the machine actually is.

Root of trust

Official RuddBSD identities.

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.

Official channels

Canonical project identities linked from ruddbsd.org. Additional accounts appear here only after they are established.

Maintainer-led

Independent technical direction.

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

Found something security-sensitive?

Please report vulnerabilities privately rather than publishing them as general project discussion.