In one breath
Every action, derivation, test and artifact: computed once, withdrawn everywhere.
Investors
In thirty seconds
Compute once, withdraw everywhere. GloriousFlywheel schedules Bazel actions and Nix derivations on one pooled remote-execution fabric; authorized callers withdraw verified results for matching inputs, toolchains and policy.
The longer version
Separate development and CI environments can rebuild identical inputs. GloriousFlywheel runs its own scheduler, which places Bazel actions and Nix derivations on one pooled worker fleet. The unit of compute is an action or derivation, not a CI job or runner. Developers and CI use distinct credentials under the adopter's policy; verified results are shared only with authorized callers. Work that requires remote execution stops when its authority or inputs are missing, with no local or hosted-runner fallback. Reuse depends on matching inputs, toolchains and policy, and on results remaining available. The product is the loop: compute, deposit, withdraw. Every authorized caller withdraws the deposited result rather than recomputing it.
Status
Status, 2026-09-29: latest signed release v0.5.2; scheduler and workers are source on main; first adopter installing; nothing measured yet.
Whitepaper
Who built this
Jess Sullivan, founder, xoxd.ai; MLOps lead on Merlin Sound ID
Request a conversation
This is the contact intake, tagged for investors: tell us about your organization and what you want to see first.