On this page
What this fleet can sell
The fleet costs money to run and every capability below is already built for another reason. This page is the list of what Stado could charge for, what exists today for each one, and what is missing — so a decision about monetization is made against the command surface rather than against a guess. It promises no revenue and sets no retail prices. Those are commercial decisions; recorded provider costs are not customer sale prices.
Four ways of charging appear here, and they are not interchangeable: an hour of hardware, a token of model output, a run with a receipt, and a subscription for operating something. The same GPU is worth a different amount under the first two.
Tokens from our own card
stado inference serves an OpenAI-compatible endpoint from a digest-pinned
vLLM container on a registered GPU host, Brama routes to it under a logical
alias, and stado web declare and stado web route are how a hostname
reaches the public internet (inference,
web hosting). --gpu-mode yieldable gives the board back to
the fleet's own queued work, so selling tokens does not mean losing the card.
What is missing is a public entrance for that endpoint — deployments publish on a Tailscale address by design — a model document with prices and declared throughput for whoever resells it, rate limits returned as early refusals rather than a queue, and a billing account.
Hours of an idle GPU
stado market auto-list --provider vast lists the box on the Vast.ai
marketplace after the queue has been idle for its window and withdraws the
offer the moment our own work appears (renting our idle GPU). This
is the only route the product performs end to end today; it is missing the
credential and nothing else. It is also the least it can earn per hour of that
card, because it sells the hardware rather than the work.
Operating somebody else's fleet
A customer brings their own machines or their own cloud account and Stado runs
the queue, the placements, the deliveries, the declared repairs and the
evidence: stado fleet enroll, stado fleet invite, stado service deploy,
stado repair, stado release (add your machine,
operations). The private marketplace repository already names
this as the first commercial route, and requires that the provider's cost and
the management fee stay separately visible. Charged per host, per month.
macOS builds, signing and updates
A Mac is the scarce machine. Stado installs and reconciles the publisher
runner with stado runner install --profile publisher, the shared workflow
signs with Developer ID, notarizes, staples and publishes a Sparkle appcast
(desktop publisher and Developer ID). Charged per release, or
as a subscription per repository whose updates we carry.
An interactive session at the GPU
stado stream provisions a display session on a host and streams it to a
Moonlight client (stream). It sells what a container marketplace
cannot: somebody working by hand on a board they do not own. Charged per hour.
Browser work with a receipt
Weles executes an authorized browser workflow and emits a signed receipt that
weles-client verifies independently; Stado places the work and carries the
artifacts (workloads). The product here is the
proof that the run happened, not the automation. Charged per run.
Hosting releases and updates
The object plane holds immutable, signed releases with channels, promotion and
rollback, and stado web and stado dns put a product on the internet
(release, primitives/object-store).
Charged as a subscription for a product whose updates we host.
Disposable isolated environments
stado scratch leases a disposable target on a registered host and destroys it
when the run ends (scratch targets). Charged per
hour or per run, for somebody who needs a clean machine for one build.
Somebody else's cloud bill
stado cost allocation, stado cost forecast, stado cost savings and
stado billing read attributed workload cost and what the providers
themselves report, and the autonomy policy's budgets block new cloud placement
before the money is spent (costs, autonomy).
Charged as a share of the measured saving, or a fixed monthly fee.
Provider quotes are not sale prices
stado cost prices --json reads the recorded provider book.
stado cost quote --json -- JOB_ID... matches jobs to the claiming worker's
identity, scoped inventory and complete hourly quotes. local@HOST identifies
agent transport, including cloud workers; it cannot select local pricing by
itself. Unknown, ambiguous or unsupported observations retain their refusal
rather than becoming free capacity or a guessed machine price.
Desktop exposes the same read-only book and per-job report under Earning → Provider prices, including source errors, worker identity and the complete command receipt. Neither a quote nor that screen approves direct resale, customer settlement, deposits or payouts. See Costs for matching and real qualification requirements.
What the fleet earns today
Nothing. The Vast.ai route is provisioned with no credential, the inference
endpoint is reachable only on the tailnet, and every other route above is a
capability that has never been sold. stado market readiness --provider vast
is the only command that reports an earning state, and it reports not provisioned.
Source: this website