Universal Distributed Compute Runtime
KRAFT virtualizes computation — not computers. Applications stay where they are. Computation doesn't.
The problem
You need the ones you already have.
A household, a small studio: a main Mac, a second notebook, a Mac mini in the corner, a retired MacBook in a drawer. Together that is quickly 28 cores and over 64 GB of RAM. Most of the time they do nothing. They contribute nothing to the work that matters.
Corporations solved this problem — with render farms, cloud and distributed infrastructure. They spent millions on it and hired teams of engineers for it. KRAFT exists because that should not be necessary. The only requirement should be owning the hardware.
cores in an average household — mostly idle.
of RAM, spread across devices that never talk to each other.
in running costs. No cloud, no subscription, no new hardware.
lines of code an application has to change in order to benefit.
The distinction
KRAFT is not a cluster manager, not a job scheduler, not a distributed operating system, not a render farm, not a remote desktop.
All of that exists. All of it is powerful. All of it needs people who can run infrastructure. KRAFT is categorically something else: a runtime that virtualizes computation while applications are running.
The principle
Applications stay where they are.
Computation doesn't.
KRAFT — Principle No. 1
The path of the work
The originating process sees only step 7. Steps 1 to 6 happen while the application keeps running.
What gets offloaded
Only work that is bounded, self-contained and describable in a hardware-neutral form can be distributed.
The adapter layer makes that decision and carries full responsibility for the translation. Whatever cannot be expressed cleanly as an IR atom stays local. No discussion.
Application state. Interactive UI. Everything that is not bounded, not neutral and not reproducibly describable. KRAFT distributes nothing it has no contract for.
Read on