Submit
Choose a workload and provide its supported inputs, prompt, parameters or files.
Submit supported AI, GPU and CPU workloads to SolarCompute. The network validates the request, finds a compatible available machine and returns the completed result.
You describe the work and choose a supported workload. SolarCompute handles validation, queuing, compatible-machine allocation, execution status and result delivery.
Customers do not connect directly to Host computers. Workloads run through controlled network services using approved runtime configurations.
Choose a workload and provide its supported inputs, prompt, parameters or files.
SolarCompute checks safety limits, runtime requirements and required compute resources.
The accepted workload enters the network queue with its GPU, CPU and runtime requirements.
The network selects compatible available capacity based on reported machine capabilities.
The approved workload executes while status, runtime and billable resource use are recorded.
Review the completed response, metrics, logs or downloadable result supported by that workload.
Each launcher applies workload-specific validation, limits and result handling.
Prompt-based AI tasks, questions, summaries and evaluation.
Open AI inference → 02 · GPUSupported training sessions with progress and completed metrics.
Open AI training → 03 · GPUGPU-backed generation and rendering with downloadable results.
Open rendering → 04 · CPUControlled computational tasks using allocated vCPU capacity.
Open CPU jobs → 05 · CPU/GPUSupported modelling and simulation workloads with public-safe results.
Open simulation → 06 · CPU/GPUControlled container validation and execution on compatible infrastructure.
Open containers →GPU-hour means one GPU allocated for one hour. Two GPUs for 30 minutes also equal one GPU-hour.
vCPU-hour means one virtual CPU allocated for one hour. Four vCPUs for 15 minutes equal one vCPU-hour.
Current default rates come directly from SolarCompute’s billing policy. A particular GPU model or workload may use an applicable override. The confirmed price should be shown before paid work is submitted.
Requests are checked against supported workload rules and public or account-level limits.
Allocation uses reported hardware capabilities and the approved recipe for the workload.
Submitted, queued, allocated, running and completed states make the execution journey visible.
Results are returned through the supported response, metric or downloadable-artifact flow.
Yes. The page reads the current default rates from SolarCompute’s public pricing endpoint. Administrators can update network billing policy as capacity and demand change.
Not necessarily. The default rate applies unless an eligible GPU-model or workload-specific override is used. Confirm the applicable price shown by the service before submitting paid work.
An accepted workload may remain queued while SolarCompute looks for capacity that meets its requirements. Workload status should show where the request is in the process.
No. SolarCompute coordinates the workload through controlled network services. Customers do not receive direct access to Host computers or private Host infrastructure.
Use the Early Access page to begin the workload journey, or create an account for dashboard tools and private platform participation.
Choose a supported workload and follow it from request to result.