Check the System
A daily planner builds and publishes the System repository only when its sealed inputs change.
Download centerYour firewall starts
Your firewall starts
with a verifiable build.
Choose the supported Stable line or an experimental Development build, verify one checksum, and install or import on amd64 or standards-compliant ARM64 UEFI hardware. Every published image is tied to exact source, ports, OS-definition, and FreeBSD revisions.
amd64 supportedARM64 experimentalSigned repositoriesApache-2.0
Guided download
Choose the image that fits.
Start with Stable for production. Cloud users can then choose UFS or ZFS and the disk format their platform expects.
Reading the release manifest...
This picker stores no release versions. It reads independently published Stable and Development documents live from the package service; installer and cloud-image links point to immutable files on the download service.
Independent build flow
Rebuild only what changed.
System updates and optional packages have separate fingerprints, repositories, and publication decisions.
Reuse optional packages
Optional packages are reused while their sources and the pinned FreeBSD platform are unchanged. A System-only change does not rebuild them.
Publish after verification
The ISO and every UFS/ZFS cloud image must pass integrity and boot-smoke checks. All immutable files are public before the channel document advances.
What is inside32 8 2 1 Explore the package platform
A smaller, sharper platform.
Curated packages
Each package declares capabilities, services, support state, and resource impact before installation.
Suricata generation
Validated atomic configuration, EVE event browsing, service controls, and a focused security overview.
Modern network additions
First-class CrowdSec response and consent-driven ZeroTier networking, integrated into the WebUI.
Sealed build set
Every stage consumes the same resolved commits. Channel metadata points to exact verified artifacts; publication never rebuilds them.
Installation
From image to gateway.
Use a dedicated appliance or VM with at least two interfaces, or one VLAN-capable interface.
- 01
Verify the download
Compare the selected ISO or compressed IMG with its published SHA-256 checksum.
sha256sum FreeSense-* - 02
Write the installer
Flash amd64 ISO media directly. Decompress the ARM64 installer IMG first, then write it to a 4 GB or larger device.
xz -dk FreeSense-*-arm64-installer.img.xz - 03
Boot and configure
Assign WAN and LAN, open the WebUI, then replace the initial administrator password.
First-boot guide
Recommended starting point64-bit CPU4 GB RAM16 GB storage2 network interfaces
ARM64 scope: The experimental image targets generic standards-compliant ARM64 UEFI systems with virtio devices. It does not include Raspberry Pi, U-Boot, DTB, or other SBC-specific firmware.
Cloud networking: Use two NICs so management remains on LAN. A one-NIC image permits key-only WAN SSH only when metadata supplies a valid key; restrict it with a cloud security group. The WebUI is never opened on WAN automatically.