Work enters SolarCompute
A supported workload is submitted through an approved service or application.
SolarCompute coordinates distributed physical and virtual compute through a controlled network designed to validate, match, execute and return supported workloads.
Supported work enters through SolarCompute services.
Requests are validated before approved execution.
Work is matched with compatible network capacity.
Approved workloads run without direct Host access.
Permitted output returns through SolarCompute.
Renewable-powered physical machines form the distributed network, supported by virtual capacity when additional resilience is required.
* Virtual capacity provides additional compute during traffic surges, high demand or temporary network constraints, helping maintain service stability.
Every supported workload follows a controlled execution path through SolarCompute before permitted output is returned.
A supported workload is submitted through an approved service or application.
The request is checked against workload rules, safety controls and execution requirements.
The network determines the hardware and workload capability required.
Compatible available network capacity is selected for the approved workload.
Approved work executes through SolarCompute without exposing Host machines to customers.
Status and permitted output are returned through SolarCompute for review.
The network separates customer access, workload control and distributed execution while coordinating them through the SolarCompute platform.
Customers submit work through SolarCompute services rather than connecting directly to Host computers.
Supported workloads are validated against workload rules, safety controls and approved execution paths.
Available machine capabilities are matched against the requirements of approved workloads.
Work is allocated to compatible physical or virtual capacity and permitted results return through SolarCompute.
SolarCompute is a distributed network. Individual machines can connect, disconnect, become occupied or change availability without defining the state of the platform as a whole.
Workloads are matched against compatible capacity available at the time of execution, with virtual capacity able to provide additional resilience when required.