Hive Compute Marketplace

Hive Compute is an experimental option, not a near-term revenue assumption. The near-term business is Hivemind Cloud: subscriptions, metered managed execution, and the Managed Agent Ops pilot. No marketplace revenue, provider supply, or network effect is forecast until real demand and reliable supply exist.

Users can already try self-hosted compute in the app; see Hive Compute.

Why it is deferred

A two-sided compute marketplace means running several businesses at once:

• finding buyers and routing their work
• finding hosts and checking their quality
• balances, metering, settlement, and payouts
• fraud, disputes, sanctions, tax, and support
• reliability, privacy, attestation, and reputation

These only pay off once Hivemind Cloud has repeatable demand. Building them too early would pull focus from the core business.

Evidence Gates

The marketplace launches only when all of these are true:

1. At least 20 paying Hivemind Cloud customers with recurring managed-compute usage.
2. At least $25,000 in monthly managed-compute gross merchandise value for three consecutive months.
3. At least 10 qualified supply partners that meet measured latency, uptime, privacy, and support requirements.
4. A documented contribution-margin advantage over centralized fallback capacity after payment, support, fraud, and payout costs.
5. Completed settlement, provider agreement, tax, sanctions, privacy, and security reviews.
6. Server-authoritative balances, reservations, receipts, fees, provider earnings, withdrawals, replay protection, and audit logs.

These are management gates, not forecasts or investor promises.

Experimental pricing

Today’s test defaults, such as a 20% platform fee and token-level input/output prices, are for experimental routing only. They are not validated market pricing and are not in the financial model. Launch pricing would be rebuilt from observed demand, costs, host payouts, fraud loss, and support burden, and the marketplace would launch only if it improves customer economics without lowering contribution margin below the Cloud target.

Who decides what

The downloadable app is never the commercial authority. HivemindOS-controlled hosted infrastructure, or verifiable settlement rails, decide buyer balances, job settlement, provider eligibility and reputation, fees and payouts, refunds and disputes, payment verification, and private-workload eligibility.

The app may discover local models, set up an opt-in worker, show status, and display signed receipts. It cannot create balances, choose fee recipients, approve payouts, or override hosted policy.

Launch decision

If the gates pass, Hive Compute becomes a second stage of the metered-execution business. If they do not, HivemindOS keeps buying capacity from established providers and stays focused on reliable managed execution.