Website
GreenPublic pages, signup, docs, and status are available.
Status
Check public-alpha GPU capacity, rendering, delivery, receipt, wallet, and website signals. Public health endpoints expose operational state without exposing private job files, account secrets, or internal filesystem paths.
Reading the current verified fleet status.
Public pages, signup, docs, and status are available.
Balance, card top-ups, charges, and refunds are available; Bitcoin top-up visibility is limited during alpha.
Upload, price, render, and package progress are available for small Blender packages.
Available GPU render partners are active, with limited visibility during controlled alpha.
ZIP outputs and completed packages are available from package tracker and receipt links.
Delivery receipts include SHA-256, cost, renderer, and frame count.
These endpoints are machine-readable operational checks. A successful HTTP response means the endpoint answered; read its returned state before assuming the associated render or worker path is available.
Green means the listed public function is available according to the current published status model. Limited visibility means the function exists, but the public page does not expose complete operational detail during the controlled alpha.
Capacity is separate from general website availability. The website can be reachable while GPUs are busy, fleet data is stale, or estimated availability is temporarily unavailable.
The capacity panel reads the public fleet-status feed and can report busy GPUs, stale jobs, update time, and estimated availability when those values are available. An unavailable value is not silently converted into a positive capacity claim.
Capacity can change after this page loads. Check again immediately before submitting time-sensitive work, especially when a project contains many frames or depends on a narrow completion window.
Public operational status is not a guarantee that a specific Blender project will render successfully. Scene compatibility, missing assets, memory use, unsupported configuration, upload validity, and job lifecycle state can still affect an individual submission.
Use the workspace or public API job-status response for the authoritative state of a submitted job. Download, receipt, and proof availability depend on that job reaching the relevant lifecycle state.
Open the workspace, review the API quickstart, read the files guide, inspect receipt guidance, or browse the proof index.
This page is an operational summary, not a historical uptime report or service-level agreement. It does not publish an uptime percentage, incident archive, recovery-time promise, or permanent-capacity guarantee.
The current status model intentionally distinguishes known green functions from areas with limited public visibility. It does not turn missing telemetry into a green result.
No. Website availability and GPU capacity are separate signals.
No. It means the endpoint answered. Read the returned operational state.
Use the workspace or the public API job-status operation for that specific job.
No. This public-alpha page is not a service-level agreement or historical uptime report.
No. The public status links are not intended to expose private files, account secrets, or internal paths.