Running Workloads
Every public workload moving through the network, and the machine running it.
Where work sits right now
Public jobs at each stage of the lifecycle.
Accepted and validated against public workload rules.
Waiting for a machine with matching capability.
Executing on renewable-powered compute right now.
Finished with a public-safe result available.
Live workload activity
Recent public jobs, the machine that ran each one, and its result.
| Job | Compute | Machine | Status | Runtime | Result |
|---|---|---|---|---|---|
| Loading live workload activity… | |||||
How workloads move through the network
Every public job follows the same controlled path.
Submit
A request enters through a public launcher and is checked against workload rules.
Queue
The job waits for a machine advertising matching capability.
Allocate
The scheduler assigns it to a suitable machine on the network.
Result
The job runs under limits and publishes a public-safe result.
What can be shown publicly
Workload reporting confirms network activity without exposing prompt contents, private results, user identity, or internal infrastructure detail.
Suitable public fields
- Public job reference
- Workload class
- Assigned public machine label
- Job status and runtime
- Public-safe result link
What is never exposed
Private prompt contents, user identity, host details, tokens and internal machine identifiers are never published.
Protected fields
- User and account identity
- Private prompt or input contents
- Host names and exact locations
- Tokens, keys and internal identifiers
- Admin-only job records
Workloads connect the public site to the network
Every job on this page ran on a real machine powered by renewable energy. Run one yourself and watch it move through the same pipeline.