Platforms often need many instances of the same workload, started on demand. The workload may be a container, an agent or a plain process. Each new instance usually boots, loads its code and fills its own memory, and often waits on a control plane first, even though it is a copy of one that already runs. fiberd creates those instances from one warm copy, fast and densely, inside whatever already places the workload, such as Kubernetes or Slurm. It is a reference implementation, not yet production-ready, and production-readiness.md lists what is missing.

What fiberd does

A template starts once and stays warm .

Each fiber is a cheap fork or snapshot restore of that template, so it starts in milliseconds.

An issuer grants a block of capacity once, as a signed grant .

The home checks the grant locally and mints fibers from it without calling back.

Why fiberd

fiberd works with the scheduler, not instead of it. Fast starts from a warm copy are not new either.…