StudioFS v0.2.0

StudioFS 0.2.0 is the first public release: a self-hosted, local-first
filesystem for VFX and post-production teams, mounted through the operating
system and backed by S3-compatible object storage and PostgreSQL.

Warning

StudioFS is early-stage software. Breaking changes will happen; keep
independent backups of production data.

What is included

• Local mounts on Windows (WinFsp), Linux (libfuse3) and macOS (macFUSE legacy
  backend), with metadata served from a local redb view.
• On-demand payload reads with a persistent local cache and background upload
  of local changes.
• Shared metadata replication through PostgreSQL; peers converge after upload,
  publication and replay.
• Snapshot v2, encryption at rest for remote payloads, runtime telemetry and an
  optional tray icon.

Downloads

Archive	System
x86_64-pc-windows-msvc.zip	Windows x86-64
aarch64-pc-windows-msvc.zip	Windows ARM64
x86_64-unknown-linux-gnu.tar.gz	Linux x86-64 (Ubuntu 24.04 libraries)
aarch64-unknown-linux-gnu.tar.gz	Linux ARM64 (Ubuntu 24.04 libraries)
aarch64-apple-darwin.tar.gz	macOS Apple Silicon

Verify each archive with its .sha256 file. WinFsp, macFUSE and Linux FUSE
libraries are installed separately; see INSTALL.md inside each archive and the
user guide.

Source

StudioFS is licensed under GPL-3.0-only. This release attaches the exact
project source (studiofs-v0.2.0-source.tar.gz) and the vendored source of
every locked Rust dependency (studiofs-v0.2.0-dependency-source.tar.gz).
BUILD-INFO.json in each archive records the source commit, toolchain and
build command. Reproduction steps are in
docs/releases.md.

Known limitations

• quick-xml advisories RUSTSEC-2026-0194 (quadratic duplicate-attribute
  checking) and RUSTSEC-2026-0195 (unbounded namespace allocation) remain in
  v0.2.0 and are explicitly ignored by the security audit. A malicious or
  compromised S3 endpoint (the one recorded in the volume's format metadata)
  can cause CPU/memory denial of service through XML responses parsed by
  opendal. The affected reqsign parser handles AWS STS XML responses;
  StudioFS passes static S3 keys and disables config-file and EC2-metadata
  credential loading, so it does not use those credential flows.
  A third affected version is used by wayland-scanner at build time on
  protocol XML. The S3 dependency migration and removal or narrowing of these
  exceptions are tracked for v0.3.0 in
  SFS-883.
• Binaries are unsigned: no Windows code signing or macOS notarization.
• macOS FSKit/MFMount support is experimental and excluded from this release.
  Intel macOS, 32-bit x86 and musl/Alpine Linux packages are not provided.
• Windows per-file ACL persistence (SetSecurity) is unsupported.
• Local acceptance, local durability and peer visibility are distinct states;
  snapshots alone are not a complete metadata-plus-payload backup.
• Application compatibility depends on workload validation; see the
  roadmap.

Source commit: b615480