Open-source cloud operations

Waldur connects VirtEngine to hybrid cloud and HPC infrastructure

Waldur supplies the catalogue, self-service and operational control plane. VirtEngine supplies the decentralized exchange, identity, escrow and settlement protocol. The provider daemon keeps both sides synchronized.

Explore Waldur Read Waldur documentation Inspect the bridge code

Architecture

Two systems with a defined boundary

VirtEngine treats the chain as marketplace source of truth. Waldur remains the provider-operated control plane for fulfilment and infrastructure operations.

Waldur contributes

Service management and delivery

HomePort gives users a self-service interface. MasterMind provides the API, catalogue, orders, resources, accounting and provider plugins used to fulfil services across hybrid infrastructure.

VirtEngine contributes

Exchange, identity and settlement

The chain coordinates provider discovery, competitive bids, leases, Verifiable Electronic Identity checks, escrow, metered usage and final settlement. Waldur does not replace that consensus layer.

Marketplace flow

From catalogue entry to settled usage

The integration follows a chain-first workflow so infrastructure changes can be connected to signed protocol state.

  1. 01

    Publish

    Providers register offerings on-chain, then the provider daemon synchronizes the catalogue and maps Waldur offering identifiers.

  2. 02

    Order

    A tenant order and selected bid become protocol state. The bridge routes the matched service request into Waldur.

  3. 03

    Provision

    Waldur coordinates fulfilment through the configured cloud, HPC or provider-specific integration and returns operational status.

  4. 04

    Operate

    Signed, replay-protected callbacks report lifecycle changes to VirtEngine. Provider-local infrastructure views remain in Waldur.

  5. 05

    Meter

    Usage records return to the chain, where the settlement module produces billable line items and releases escrowed funds.

Integration map

Current code, upstream capability and roadmap

The labels below are deliberate. An upstream Waldur connector is not automatically a production-ready VirtEngine integration.

Implemented in the VirtEngine bridge

  • Waldur marketplaceOfferings, orders, resources, lifecycle operations and usage records through the official Go client.
  • OpenStackInstance, tenant and volume operations exposed through the Waldur client package.
  • Amazon Web ServicesCompute and storage resource operations represented in the current bridge.
  • Microsoft AzureVirtual-machine, size and location operations represented in the current bridge.
  • SLURM and HPCAllocations and job-state reporting connect scheduler-backed capacity to the marketplace.
  • Object storage and supportEncrypted object workflows and provider-local support desk operations have dedicated clients.

Available in Waldur upstream

  • Cloud and cluster providersWaldur documents OpenStack, Rancher, Kubernetes, VMware, Azure, DigitalOcean, SLURM, MOAB and other provider modules.
  • OpenNebula site agentWaldur already documents an OpenNebula site-agent plugin; VirtEngine's first-class chain mapping is still planned.
  • Federation and identityDocumented options include eduGAIN, eduTEAMS, Keycloak, LDAP, FreeIPA, MyAccessID and TARA.
  • ExtensibilityRemote offerings, custom scripts, OpenPortal and site-agent plugins provide routes for operator-specific services.

VirtEngine roadmap

  • Proxmox VEA planned provider adapter and catalogue route. It is not presented here as a shipped Waldur or VirtEngine integration.
  • OpenNebulaA planned first-class VirtEngine bridge using Waldur's existing site-agent capability, with lifecycle and usage mapped to chain state.
  • Production certificationEach enabled backend still needs versioned profiles, end-to-end provisioning evidence, cleanup, quota and cost-control testing.

This status reflects the current repository and published Waldur documentation. “Implemented” means a code path exists; production availability still depends on provider configuration, credentials, backend compatibility and deployment certification.

Project stewardship

Developed and stewarded by OpenNode Cloud

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.

Visit OpenNode Cloud Waldur on GitHub
provider-daemon
source      VirtEngine chain
bridge      provider daemon
control     Waldur MasterMind
catalogue   offerings → orders → resources
feedback    signed lifecycle + usage callbacks
settlement  on-chain escrow release

Waldur ecosystem

Organizations featured by Waldur

Waldur publishes the following organizations in its own customer and partner showcase.

Logos are reproduced from Waldur's published showcase to describe Waldur adoption. Their appearance here does not imply endorsement of VirtEngine or DETIO FOUNDATION LTD.

Primary sources

Explore the platform directly

Architecture and integration details on this page are grounded in the VirtEngine repository and Waldur's official material.

Waldur platformFeatures, use cases and organization showcase ArchitectureHomePort, MasterMind, workers and site agent Marketplace modelOfferings, orders, resources and accounting Integration catalogueProvider, identity and site-agent plugins OpenNode CloudDevelopment, deployment and support VirtEngine bridgeCurrent integration source code