Offer the time windows you can commit to customers, with clear hardware and pricing conditions.
Describe the capacity
Submit capacity with your company, authorised contact, GPU model and count, location, availability and pricing preference. Cluster and node identities are reported by the agent in the connection step. Only declare resources you are entitled to provide commercially.
Define the conditions
Specify the minimum and maximum duration, allowed purchase modes and whether separate customers may use distinct GPUs on a node. On-demand sessions with early release are opt-in. Hardware compatibility and isolation must support the service you offer.
Keep maintenance and your own workload needs outside the committed window. An inventory count alone does not establish how many GPUs are free to sell.
Review and listing
Requenta reviews supplier authority, hardware, access, isolation and commercial conditions before capacity can be offered to customers. Submitting a declaration does not make it immediately available to purchase.
Your supply agreement defines commitments, interruption handling, evidence and payment conditions. Keep changes to availability and payment details up to date through the agreed review process.
Security review
Provide evidence for access controls, workload isolation, network policies, host and image maintenance, access expiry and data cleanup, and incident response. A reviewer checks the scoped report before qualifying an offer. A recorded review is not a security certification. Infrastructure or access changes require a new review; withdraw affected capacity while resolving an issue.
Connect with Helm
After saving capacity, open its Connection & setup page. Generate a private installation code, install the Helm agent and wait for the connection to appear. Follow Connect your cluster for installation and permissions. No node names are required in the initial capacity form.
Choose your pricing
At the market price offers the selected period without a personal minimum. Minimum net price accepts matches only when the supplier net rate clears your chosen minimum. The form starts with a minimum net price; market pricing is optional. Both modes require a defined availability window. Offering a period is not a guaranteed purchase of all its hours.
The buyer rate differs from supplier net earnings. Requenta buys the hours it resells to its customers and pays you 94.5% of the price each customer accepts; it keeps 5.5% before costs. There is no shared bonus. A market price is not a promised supplier payout. The current rate is shown in the market, and an accepted booking keeps its agreed price. Existing bookings are never repriced when market conditions change.
Include disk and network costs
Choose your infrastructure provider and cloud region or datacentre. Confirm the rates against your compute contract, including network gateways and any applicable region-specific charges. Public Object Storage prices and account-wide free quotas are not automatically substituted for compute network costs.
Set the working disk included per booking and the largest disk you can supply. Choices range from 10 to 2,000 GiB. Set separate included upload and download allowances. Additional disk is priced per 100 GiB-hour; upload and download extensions are priced per 100 GiB. Enter your net rates: the form displays the customer price, which includes Requenta's 5.5% reseller margin. A zero rate offers that resource without an additional charge.
The customer chooses disk before confirming a quote. GPU and selected extra disk are prepaid together, then settled for delivered minutes. Undelivered time returns to credits; the accepted cancellation schedule still applies. Extra disk is per booking, not per GPU. Temporary disk is deleted at cleanup and cannot be expanded during the session.
Transfer extensions are explicit purchases in 100 GiB packs, up to your maximum in each direction. The customer sees the rate and maximum amount before purchase. Each started GiB of allocated transport capacity is charged; unused whole GiB return to credits at session end. Your reservation details show your earnings and Requenta's margin. There is no automatic overage invoice.
Your accepted earnings cover the included resources, image downloads and infrastructure overhead, including when a customer stops early. Infrastructure traffic outside the SSH relay is not a customer usage meter. Include these costs in your GPU floor or agreed resource rates; they cannot be invoiced later without a separately accepted purchase.
Qualify the resource profile
Use agent/chart 0.5.0 or newer with resource-bundle execution enabled. Set its maximum per-booking disk and aggregate ephemeral-storage budget to match verified infrastructure capacity. The workspace requests its selected disk plus 10 GiB runtime overhead. Kubernetes schedules against these requests; confirm the node filesystem layout supports kubelet ephemeral-storage accounting and eviction. Test concurrent reservations and cleanup. A pending or failed allocation does not establish delivered compute.
Record the resource review: provider contract and region, included quantities and optional tariffs, sufficient disk and runtime overhead, effective resource accounting, eviction behaviour, network denial, transfer directions and limits, and cleanup. A recorded review is not an automated audit of the provider bill.
New resource bundles require Requenta workspace access. The console rejects quotes from older or incompatible agents instead of silently providing 10 GiB. Supplier gateways retain their historical reviewed profiles and do not sell these resource extensions.
Capacity without agreed resource terms cannot generate new quotes. Submit a new capacity declaration to change your package. Existing accepted reservations always retain their original disk, network and settlement terms.