Get Started

Artifacts stay immutable. Deployment stays simple.

Store and distribute verified PitFast Components through content-addressed filesystem or S3-compatible storage.

IMMUTABLE DIGEST
sha256:a4f8e9...
artifact.wasm
artifact.json
SHA-256
Byte Verification
Cryptographically verified runtime components
Dual-tier
Tags & Digests
Flexible human tags with permanent digest anchors
S3 / Disk
Vendor Neutral
Works on bare-metal disk or cloud object storage
REGISTRY ARCHITECTURE

Predictable distribution without vendor lock-in

Paddock guarantees that the artifact deployed to testing is bit-for-bit identical to the artifact running in production.

01Integrity

Immutable by Digest

Every artifact is identified by the SHA-256 of its actual bytes. No accidental overwrites or deployment drift.

02Tagging

Mutable Human Refs

Tags can move freely without changing previously deployed artifacts, enabling clean release promotions.

03Backends

Vendor-neutral Storage

Filesystem and S3-compatible backends without locking PitFast to a single proprietary cloud provider.

CLI ARTIFACT MANAGEMENT

Push, pull, and inspect verified artifacts

Paddock exposes transparent inspection tools to examine digests, manifests, and component metadata.

bash
# 1. Push component with human-readable tag
pit push service-a:v1

# 2. Pull artifact directly by tag or digest
pit pull service-a:v1

# 3. Inspect artifact manifest, dependencies, and SHA-256
pit paddock inspect service-a:v1
The PitFast Lifecycle

How it connects to the rest of PitFast

Every subsystem handles one distinct responsibility in the demand-driven execution chain.

GET STARTED WITH PADDOCK

Push your first artifact.

Verify how content-addressed storage eliminates build drift across all your machines.