Open-source cloud operations
Waldur is the enterprise catalogue and control plane for the VirtEngine market: publish IaaS, PaaS, SaaS and custom listings, order directly from chosen providers, and gate everything with approvals and compliance. VirtEngine turns each permitted order into a verifiable lease — escrowed, metered and settled on-chain.
Demonstration
The interactive order demo now lives where it belongs — on the marketplace hub. Browse the catalogue, configure a plan, buy direct, by bid or by selector, then deploy the lease and settle usage.
Architecture
VirtEngine treats the chain as the marketplace source of truth. Waldur remains the provider-operated control plane for fulfilment and infrastructure operations. The provider daemon keeps the two correlated.
Verifiable market
Consensus state: who may trade, what was agreed, what is owed, and what was settled.
Consensus + market state
Bridge
The operator-run agent that translates protocol events into control-plane operations and reconciles the answers back.
Translation + reconciliation
Control plane
The service-management platform that presents the catalogue and operates resources, projects, quotas and reporting.
Service management + fulfilment
Trace a responsibility: hover or focus offering sync to follow an on-chain offering into the provider mapping and the Waldur catalogue; hover usage submission to follow component measurements back through signed usage into settlement state.
Waldur is developed independently by the Waldur community and OpenNode Cloud. VirtEngine consumes its public platform and client interfaces; it does not own or replace Waldur, and Waldur is not “running on the blockchain”.
What users actually see
Four interface areas, and the responsibility split inside each one. Screenshots are Waldur's own, reproduced with attribution.
Categories, offerings and plans turn provider capacity into products. Users search, compare and order inside the same interface they use for everything else.
Screenshot reproduced from Waldur's published material to explain the integration. View the official source ↗
Organisations and projects carry membership, limits and cost views. Leased resources appear in the same workspace as the rest of a team's infrastructure.
Screenshot reproduced from Waldur's published material to explain the integration. View the official source ↗
Resource state, quotas and supported actions live in Waldur. Signed callbacks return lifecycle outcomes to the bridge, where they are validated and correlated.
Screenshot reproduced from Waldur's published material to explain the integration. View the official source ↗
Waldur exposes usage, estimates and accounting reports. VirtEngine separately turns signed usage records into protocol settlement against escrow.
Screenshot reproduced from Waldur's published material to explain the integration. View the official source ↗
Walkthrough
A fictional Managed GPU Workspace, from publication to settlement. Illustrative example — no step implies live production availability.
A provider registers the offering on-chain and maps it into Waldur. The catalogue card and the protocol object stay connected by a persisted identifier.
Illustrative example — Managed GPU Workspace.
PaaS
Illustrative exampleExample Provider
ap-southeast
Component-priced plan
VirtEngine offering_id → chain objectProvider daemon mapping → persisted cross-referenceWaldur offering_uuid → catalogue itemThe synced offering shows up as a catalogue card with its category, plan, region, components and provider details.
Illustrative example — Managed GPU Workspace.
PaaS
Illustrative exampleExample Provider
ap-southeast
Component-priced plan
OrderA direct order names the listing and matches at its published price. Escrow is funded before anything is provisioned.
Illustrative example — Managed GPU Workspace.
Service Managed GPU WorkspaceRegion ap-southeastComponents GPU-hour · vCPU-hour · RAM · storageEscrow funded against the orderOne tenant, one provider, one escrow account. The lease is the agreement every later step references.
Illustrative example — Managed GPU Workspace.
The lease binds tenant, provider and escrow account.
The provider daemon routes the matched request into Waldur, which invokes the configured backend. The chain records the outcome; it does not create the resource.
Illustrative example — Managed GPU Workspace.
Fulfilment runs through the provider's control plane — not through consensus.
Resource state moves through the provider's control plane and returns as an authenticated lifecycle callback.
Illustrative example — Managed GPU Workspace.
The provider daemon meters consumption per workload on a scheduled cadence and submits signed records against the lease.
Illustrative example — Managed GPU Workspace.
GPU hours 12.4 h
vCPU hours 198 h
RAM GB-hours 792 GB-h
Storage GB-months 0.41 GB-mo
Illustrative meter readings — not production data.
After the dispute window, validated records price into line items and the agreed amount releases from escrow to the provider.
Illustrative example — Managed GPU Workspace.
Waldur reporting stays operational; the protocol payout follows the lease.
Catalogue
Waldur fulfils IaaS, PaaS, SaaS and custom listings — the catalogue itself is owned by the marketplace hub. Direct ordering is what this catalogue fulfils end to end; open bids and selector matching are chain-side paths covered in the buying guide.
Buying modes: Three ways to buy → Service types: Marketplace catalogue → Lifecycle: Order → Match → Lease → Usage → Settlement →
Enterprise control
Waldur's catalogue controls decide which providers your teams can even see — the chain then records and settles whatever those controls permit.
Catalogue scoping
Providers can publish private offerings visible only to chosen customers, limit plans to specific organization groups, and restrict ordering to named project roles. What your teams can't see, they can't order.
Dual approval
Every order passes two independent approvals: your side (consumer review, cost limits, purchase-order attachments) and the provider's side. Either side can require manual sign-off.
Terms and compliance
Each offering carries its own terms of service, privacy policy and access policies, re-accepted whenever they change. Providers attach compliance checklists your teams answer and auditors can inspect.
Counterparty choice
Providers must clear VEID identity verification, minimum trust scores and compliance checks before they can publish; offerings can additionally demand score thresholds and multi-factor authentication from buyers.
A note on SLAs and liability, stated plainly: there is no on-chain SLA object, and the protocol cannot underwrite a provider's uptime. Commercial terms live where contracts live — in offering terms, descriptions and plans, accepted per order — while the chain independently verifies what money can verify: gated counterparties before matching, signed metering during service, escrowed funds, and rule-bound settlement. Legal liability stays with the provider organisations you chose; the protocol makes their performance auditable.
Integration status
An upstream Waldur connector is not automatically a production-ready VirtEngine integration.
Real code paths in the repository — not a design-only diagram.
Production availability depends on operator configuration and certification.
“Implemented” means a code path exists in the repository; production availability still depends on provider configuration, credentials, backend compatibility and deployment certification. This status reflects the current repository and published Waldur documentation.
Available in Waldur upstream
VirtEngine roadmap
Project stewardship
OpenNode Cloud leads Waldur development, support and deployment services. Waldur is open source and is co-developed with the University of Tartu. VirtEngine consumes the public platform and client interfaces; it does not claim ownership of Waldur.
source VirtEngine chain
bridge provider daemon
control Waldur MasterMind
catalogue offerings → orders → resources
feedback signed lifecycle + usage callbacks
settlement on-chain escrow releasePrimary sources
Architecture and integration details on this page are grounded in the VirtEngine repository and Waldur's official material.
Continue