Learn · Economics
Provider Economics: Revenue & Pricing
A provider's business on VirtEngine reduces to three questions: what does capacity earn, what do chain actions cost, and what raises realized prices over time? The answers are unusually legible, because every term is chain state.
Revenue: prices you set, escrow that pays
You publish list prices for direct orders, and configure bid strategy in the provider daemon for orders opened to competition; the marketplace matches both against demand. Every lease you win is backed by escrow funded before the workload starts — verifiable on-chain — so revenue risk is settled before capacity is committed.
Usage is metered hourly and settles automatically after the 24-hour dispute window. There is no invoicing, no collections, and no accounts-receivable aging: settled usage is settled money.
Costs: transaction fees and operations
Lease settlements have no platform or validator fee deduction: the full agreed amount is paid to the provider in ACT. Chain transaction fees for actions such as bidding and usage submission compensate validators and are proposed at approximately 90% below standard network transaction fees. The daemon can manage those fees with batching. Your real cost base remains power, hardware, bandwidth, and people.
What raises realized prices
Anonymous capacity competes on price alone. Verified capacity competes on quality:
- Benchmarks (x/benchmark) — published measured performance lets tenants pay for verified capability
- Auditor-signed attributes (x/audit) — attested region, tier, and compliance claims unlock orders that require them
- Reviews (x/review) — lease-bound reputation compounds with every served workload and is yours permanently
- Confidential compute (x/enclave) — attested TEE capability is a premium, filterable attribute
The demand side you're selling into
Orders arrive from identity-verified tenants with funded escrow — from containerized services to HPC batch jobs. Attribute-constrained orders (audited claims, benchmarked hardware, enclave attestation) are where differentiated operators escape pure price competition.
A worked lifecycle
A tenant posts an order; a direct order matches your published price, or your daemon bids your configured price and the tenant accepts. The workload runs on your Kubernetes cluster or HPC scheduler. Hourly usage records — signed, anomaly-screened — accumulate against the lease. Each clears its dispute window and settles: escrow pays the agreed lease amount at the full agreed amount. Your track record grows by one more served lease, and the next order prices a little better.
Asked about provider economics
What does the protocol charge providers?
Settlement fees are governance-set protocol parameters, not a private platform margin. Only chain-message transaction fees otherwise apply — proposed at approximately 90% below standard network transaction fees, manageable with batching. Your real cost base stays power, hardware, bandwidth, and people.
How do we escape pure price competition?
Publish benchmarks for measured capability, get attributes auditor-signed, compound lease-bound reviews, and offer attested enclave capacity. Attribute-constrained orders pay for verified quality instead of the lowest sticker price.
What does “no accounts receivable” mean in practice?
Usage meters hourly and settles automatically after the dispute window. No invoicing, no collections, no aging — settled usage is settled money.