← All releases

RELEASE v0.1.0

DEVELOPER PREVIEW

Pepper 0.1.0

Released July 11, 2026 · protocol v4

View on GitHub ↗

Overview

Initial developer-preview release of Pepper's distributed content-addressed storage and data-local Firecracker compute platform.

Included

  • Apache License 2.0 distribution terms, DCO 1.1 contribution policy, automated sign-off enforcement, and dependency license checks.
  • Immutable raw blocks and chunked object/directory DAGs.
  • Replicated and Reed-Solomon erasure-coded storage.
  • Signed provider records, implicit root pinning, authenticated pin synchronization, pin-driven garbage collection, corruption recovery, and repair.
  • Authenticated QUIC node networking and local HTTP/CLI interfaces.
  • Firecracker-only compute with CID inputs, captured outputs and logs, cancellation, limits, and signed receipts.
  • Metrics, administrative status, metadata backup, and development multi-node configuration.

Release scope

Version 0.1.0 is intended for evaluation and controlled deployments. It does not provide tenant isolation, public-federation abuse resistance, Byzantine durability, confidential compute, or attestation. Keep the P2P listener behind an appropriate network boundary and use authentication, reviewed rootfs images, resource limits, and the Firecracker jailer where applicable.

Known limitations

  • Normal CI does not execute a real Firecracker/KVM workload; that requires the host-gated workflow.
  • EC reconstruction is bounded and buffered rather than streamed.
  • Metadata backup requires a stopped or quiescent agent.
  • Replicated repair uses serialized full scans.
  • Age-based GC grace periods, tenant quotas, and online coordinated backup are not implemented.