PUBLIC / OPEN SOURCE
Open source and transparency
“Auditable” is not a slogan — it is the one promise among the three that can be checked.
Code you can review
The node app, protocol and ledger logic are open, so anyone can review resource usage and billing rules.
Logs you can export
Local logs are inspectable and exportable, including the “what is using your machine right now” view.
A ledger you can verify
Merkle roots are published and locally recomputable; a zero diff across migrations is the release gate.
Boundaries
- The three promises cover resource usage and observability — not custody or financial guarantees.
- The platform does not custody your provider key. The web binding flow forwards the client credential once to verify node identity; it is never stored or echoed.
- The front end exposes public pages and two role workspaces only; there is no admin entry point here.
What we do not do
- We make no return promise and no promised rate of return.
- There is no transferable balance; tokens only offset inference, and referral points carry no yield promise.
- We do not invent a green state when there is no data.