UserBus
Your machine
- An availability window: how many hours a day the machine serves jobs.
- The runtimes it runs, declared per machine.
- The worker process, running under an account you control.
One job per worker at a time.
COMPUTE PROVIDERS
Supply the compute. Serve the jobs.
Providers contribute compute and run the UserBus worker. The marketplace matches each job to a declared runtime, leases it to one provider at a time, verifies the result and settles payment for verified work.
Enrolment is by operator invitation. Estimate your earnings
01 / WHAT YOU CONTRIBUTE
Capacity, and a clear declaration.
The marketplace matches on what you declare, so the declaration is the contract.
The worker
- A Rust binary, published as the UserBus worker.
- It builds and runs on Linux and macOS.
- It registers capabilities, claims one job, renews its lease, uploads the finished file and exits nonzero on any failure.
- It runs the reference video path with an ordinary CPU machine.
- A prompt arrives as data and stays data.
02 / RUNTIMES
Declare what you run.
Providers declare a runtime per machine. UserBus targets three of them.
| Runtime | Target hardware | Assignment |
|---|---|---|
| NVIDIA CUDA | NVIDIA GPUs on Linux | Declared by the provider, admitted by UserBus |
| Apple Metal | Apple silicon on macOS | Declared by the provider, admitted by UserBus |
| Apple MLX | Apple silicon on macOS | Declared by the provider, admitted by UserBus |
- A job is assigned to a provider whose declared runtime fits the request.
- The worker runs the runtime the request names, and starts nothing else.
- The video reference path runs on CPU capacity, so a provider can serve delivery work on an ordinary machine.
03 / MATCHING AND LEASES
One job, one provider, one lease.
Fencing keeps a job tied to the provider that holds it.
- 01
Declare
You register the exact tuple you run: kind, model, version and runtime. Matching jobs come to you.
- 02
Lease
A job is leased to one provider at a time, with a deadline. You renew the lease with heartbeats while you work.
- 03
Fence
The lease decides who may change a job and its result, so a job stays with the provider that holds it.
- 04
Retry
A job that fails returns to the queue and is retried a bounded number of times. Attempts are counted.
04 / VERIFICATION AND PAYMENT
Verified work is the work that pays.
Payment follows verification on every job.
Before a job counts
- UserBus checks the uploaded file's size, media type and digest itself.
- A verified upload is what completes the job.
- The provider holding the current lease submits the result for it.
How settlement works
- One settlement record is written per completed job.
- Providers are paid for verified work.
- Your rate is your own input, and the earnings page turns it into a monthly and yearly figure.
ESTIMATE YOUR NUMBERS
Work out the arithmetic.
Enter your own assumptions on the earnings page and read every step of the calculation.