Identity
The applicable identity requirements, so providers can verify who is on the other side of the lease.
For tenants & buyers
What are you looking for? Pick a workload below — then verify, find, choose, fund, run.
Tenant journey
Step 1 · Verify
Marketplace access is identity-gated in both directions. Tenants complete the identity requirements a provider or listing may ask for before matching.
What is VEID?Step 2 · Find
Start from a published offering, or describe category, region, specifications and a price cap when you want the engine to find eligible listings.
Browse service typesStep 3 · Choose
Take a listed price, open the order to competing providers, or match by attributes. All three paths resolve on-chain.
Three ways to buyStep 4 · Fund
Escrow is committed against the agreement — provably funded, and released only under settlement rules. Unspent balance returns to you.
Escrow & settlementStep 5 · Run
The provider daemon routes the matched request into the provider's control plane and backend. Usage settles from escrow — full lifecycle in the guide.
Marketplace lifecycleFull protocol detail: Order → Match → Lease → Usage → Settlement →
Entry paths
GPU machines, nodes, training allocations and inference endpoints.
ExploreInfrastructure you control, from VMs to bare metal.
ExploreScheduler-backed queues, allocations and job templates.
ExploreKubernetes, databases, runtimes and batch platforms.
ExploreSeats, licences, subscriptions and support plans.
ExploreAttested paths and enclave-backed workloads.
ExploreBefore you start
The applicable identity requirements, so providers can verify who is on the other side of the lease.
Escrow funding for the order or lease. Funds are committed, not spent, until usage settles.
Region, specifications, compliance or attestation needs — the inputs that make selector matching work.
Under the hood: VEID identity, x/escrow for funds held against leases, x/settlement for usage-to-payment, and the marketplace glossary for every term on this page.
Continue