Compute Marketplace
Deliver virtual clusters as a provider and publish provisioned capacity for future renters.
The compute marketplace separates infrastructure delivery from tenant setup. A compute provider reserves CPU, memory, and optional GPU resources in a virtual cluster. Once that resource partition is provisioned, it can be published without configuring a domain, ingress, monitoring, or tenant applications.
Cluster setup belongs to the renter. The rental and renter setup flows are not available yet; the marketplace currently provides discovery only.
Provider workflow
Renters are billed for the capacity they hold, by the hour, so a machine is priced per resource rather than per month. Leave a resource at 0 when the machine has none — a GPU-less machine prices its GPU hour at zero — but at least one rate must be above 0 to publish. The marketplace card also shows the equivalent monthly figure at that machine's own size, so the price stays comparable at a glance.
Publishing requires an active provisioned resource partition. It does not require tenant setup. Published clusters appear in Deploy → Compute marketplace and can be unlisted before they are rented. To change listing details, unlist the cluster and enter the new description or rates while republishing it.
Billing is currently switched off. Usage is metered and shown under Token usage → Compute usage, but nothing is charged to a wallet yet. The platform accrues and reconciles first, and charging is enabled separately once the numbers are trusted.
Editing and deletion
The disabled Edit cluster control is reserved for changing the virtual cluster's allocated CPU, memory, or GPU resources and for deleting the cluster. Those operations are not implemented yet. Publishing details are not cluster resource edits; they are entered through the Publish or Republish action.
When renting is added, a rented cluster will remain locked against resource editing and unlisting until its rental period ends.
Connect Your Machines
Install a managed cluster over SSH, then add, inspect, or remove worker nodes as capacity changes.
Deploying Services
Ship a service onto your cluster from a template, a Helm chart, a Dockerfile, a docker-compose file, or a GitHub URL — each deployment gets its own domain and TLS.