A marketplacemade of records.
Five signed records carry a machine from spec to receipt — a compute.vm payload wrapped in a four-hop RFP→bid→accept→receipt chain
Each record carries its own inline network.attested signature. The arrows are strongRefs linking each hop to the one before it.
Sample RFPs
role: ml-inference-worker · policy: tangled-vouch
role: batch-render-node
role: ci-runner
Hand your spare capacity to your own people
If your org already owns infrastructure — a Docker host, a DigitalOcean account — it can act as a bidder with pluggable compute providers for its own members — no shared root passwords, no internal ticket queue. A member's RFP is just another signed record, and your bidder decides whose it will even look at.
See how policy modes work →Just your own DIDs — an internal pool, nothing public yet.
Anyone your org mutually follows — reuse the social graph you have.
Anyone vouched for on Tangled's graph — revocable with a denounce.
Delegate the allow/deny call to your own policy server or CI, per request.