OPEN INFRASTRUCTURE MARKETPLACE

The open market for infrastructure and services.

Buy from providers you choose, let providers compete for your workload, or match by requirements. Identity, escrow and settlement remain verifiable protocol state.

Protocol in development

BuyingThree paths · one rail

Three ways in. One market rail out.

Pick a listing, open demand to bids, or describe requirements. The match becomes a lease under escrow — the rail below never changes.

Default · listed price Illustrative example

Name the listing. Buy at the published price.

Pick a provider's offering and plan from the catalogue and order it directly. The order names that exact listing, matches without a bidding window, and becomes a lease backed by escrow. This is the default path — and the right one for most purchases.

  1. Pickoffering + plan
  2. Ordernames that listing
  3. Matchat the listed price
  4. Runprovision · meter · settle

When to use it — Published plans from providers you have chosen — compute, SaaS seats, support, anything with a price list.

Compare in the buying guide

Opt-in · price discovery Illustrative example

Post what you need. Providers compete on price.

Open your order to a bidding window and let eligible providers offer prices. Accept a bid yourself, or let the matching engine take the best-ranked offer when the window closes. Use it for fungible capacity where competition should set the price.

  1. Postspecs + max price + window
  2. Bidsproviders offer openly
  3. Acceptyou pick, or auto-resolve
  4. Runprovision · meter · settle

When to use it — Commodity or spot capacity — GPU-hours, bulk compute — where price discovery beats a price list.

Compare in the buying guide

Attribute matching Illustrative example

State the requirements. Get matched to eligible listings.

Instead of naming a provider, describe the category, region, minimum specifications and maximum price. The engine filters to eligible listings and matches deterministically within your cap — request-for-quote semantics without the negotiation round-trip.

  1. Describecategory · region · specs · cap
  2. Filtereligible listings only
  3. Matchlowest eligible price ≤ cap
  4. Runprovision · meter · settle

When to use it — Constrained workloads where the fit matters more than the vendor name.

Compare in the buying guide

Compact overview. Full comparison lives in the buying guide.

Why it exists

Infrastructure should be an open market.

VirtEngine is not the cloud. It is the market independent infrastructure can join.

Catalogue

IaaS, PaaS, SaaS — and custom listings.

One catalogue. Multiple service models.

Infrastructure, managed platforms, software plans and provider-defined services — all in one place, with the same ordering and settlement flow.

IaaS

Infrastructure as a Service

Compute, storage and networking on demand.

  • Virtual machines
  • Private cloud
  • Bare metal
  • GPU nodes
PaaS

Platform as a Service

Managed platforms for modern application teams.

  • Managed Kubernetes
  • Managed databases
  • Inference endpoints
  • ML workspaces
SaaS

Software as a Service

Software sold as plans, with seats, licences and support.

  • Software subscriptions
  • Seats
  • Licences
  • Hosted applications
Custom

Anything a provider can describe

From consultancy to scripted provisioning and bespoke bundles.

  • Scripted service
  • Custom order form
  • Remote catalogue item
  • Specialist service
One catalogue All service models, one marketplace
  1. Browse Explore the catalogue
  2. Order Self-serve or assisted
  3. Provision Automated delivery
  4. Use Track usage and limits
  5. Settle One consistent model

Infrastructure depth stays first-class: GPU fleets, HPC schedulers and confidential enclaves sit alongside general cloud.

Explore the catalogue

Guarantees

Trust built into every transaction

Identity

VEID

Verified counterparties without exposing unnecessary identity data.

Identity

Evidence

Audit · benchmark · attestation

Evidence travels with providers and capacity.

Providers

Money

Escrow · usage · dispute · payout

Payment follows recorded service.

Settlement

Want the architecture? Client → Protocol → Provider daemon → Infrastructure Explore the protocol

Source

Built in the open

  • 27 modulesConsensus-executed protocol surfaces.
  • One repositoryChain, client and provider tooling.
  • Apache 2.0Inspect and build the implementation.

Network status

Protocol development · Active
Public TestNet · Planned
Production MainNet · Not live

Last updated 17 Sep 2026

View network status

VirtEngine is stewarded by DETIO FOUNDATION LTD, Australian not-for-profit public company limited by guarantee (ACN 699 651 771), supporting open infrastructure, privacy-preserving identity and public-interest technology.

About the Foundation DET.io ↗

The thinking behind the protocol.