GoKawiilPullrun One OCI image. Any execution target. CLI + runtime under 25 MB. Run the same OCI image as a container, Firecracker microVM, Apple Silicon VM, Kubernetes workload, or AI agent task. No daemon required. No overlayfs. No separate VM images.
⚡ 30-Second Install • 🚀 Quick Start • 🏗️ Architecture • 🎯 Why Pullrun? • 🗺️ Feature Map • ☸️ Kubernetes • 🤖 AI Agents
⚡ What is Pullrun?
Pullrun runs the same OCI image as a container or a VM. It stores layers in a content-addressed DAG (no overlayfs), syncs blocks peer-to-peer, and ships as a ~14 MB CLI + ~6 MB runtime daemon.
Why this matters: Modern infrastructure uses too many execution engines — Docker for dev, containerd for production, Firecracker for isolation, CRI for Kubernetes, MCP agents for AI. Each has its own image format, storage, and operational model — even though they all run the same OCI images. Pullrun collapses these layers into one runtime.
Key differentiators:
Containers and VMs from the same image — no separate VM build step, no separate VM image format
— no separate VM build step, no separate VM image format Content-addressed DAG store — zero-copy mmap reads, deduplicated by content hash, byte-identical across every node
— zero-copy mmap reads, deduplicated by content hash, byte-identical across every node P2P image distribution — one registry pull per cluster, rest sync peer-to-peer at LAN speed
— one registry pull per cluster, rest sync peer-to-peer at LAN speed ~14 MB CLI + ~6 MB runtime daemon (stripped) — no daemon required by default (CLI-only pullrun run ), optional daemon for background services
... continue reading