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.
PRE-RELEASE DEVELOPMENT
Verifiable by design.
AsterBSD 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.
AsterBSD 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.
AsterBSD 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.
AsterBSD 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.
Controlled transitions
Meaningful changes are designed to be planned, reviewed, policy-checked, applied transactionally, and recorded as evidence.
Evidence-backed builds
Build and release claims are separated from assumptions. AsterBSD aims to claim only what its collected evidence can substantiate.
VM-first validation
Boot and installation behavior is validated in controlled virtual environments before stronger artifact claims are made.
Strict system profiles
Profiles define deliberate operating environments with explicit expectations around packages, services, configuration, and policy.
Rust at trust boundaries
Rust is used where memory safety matters most: verification, policy, evidence processing, and AsterBSD-owned trusted tooling.
INTENDEDWhat the operator wants.
DECLAREDWhat policy has accepted.
APPLIEDWhat AsterBSD changed.
OBSERVEDWhat the machine actually is.
Root of trust
Official AsterBSD identities.
This website is the authoritative source for AsterBSD 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 asterbsd.org.
- Websiteasterbsd.orgOfficial
- GitHubgithub.com/AsterBSDOfficial
- X@AsterBSDProjectOfficial
- Bluesky@asterbsd.orgOfficial
Maintainer-led
Independent technical direction.
AsterBSD is an independent, maintainer-led open-source project. Community feedback, testing, bug reports, security research, documentation improvements, and aligned contributions are welcome, 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.