PitBox prepares portable Components and schedules each execution directly across a shared pool of execution lanes.
Traditional container orchestrators hold idle memory for thousands of static replicas. PitBox only schedules active work.
All services compete for the same available execution capacity. When a request ends, the lane is freed instantly.
Compile once, reuse prepared Wasmtime artifacts across executions for sub-millisecond execution start times.
Queue depth and lane capacity keep concurrency strictly controlled without reserving static capacity per service.
Execute tasks locally or fire high-throughput load tests through the PitBox execution lanes.
# 1. Execute workload directly inside a lane
pit run service-a:v1
# 2. Run high-concurrency benchmark against shared lanes
pit bench pit://service-a/hello --concurrency 50 --requests 5000
# 3. View real-time lane utilization and queue depth
pit statusEvery subsystem handles one distinct responsibility in the demand-driven execution chain.
Start the PitFast daemon locally and watch requests execute across disposable lanes.