Browse documentation
Docs/For providers

Provider and renter tutorial

Rental websites and storefronts

Register your rental website, select private listings, connect customer accounts and use ComputeCubed Rental Balance.
Product source reviewed: 30 October 2026

Accounts and catalog ownership

A storefront is a provider's rental website that uses ComputeCubed accounts, Rental Balance and rental operations. Storefront integration must be enabled on the platform before registration and private listing controls are available.

There are two separate connections. The website's backend uses a client ID and secret belonging to the account that registered the storefront. Each renter then connects their own ComputeCubed account and approves the website's requested permissions. A provider's client credentials alone cannot access a renter's wallet or rent on their behalf.

The catalog contains only the owner's node listings explicitly assigned to that storefront. It does not include other providers' inventory or automatically copy the public marketplace. This pilot supports sliced workspace rentals; cluster listings and Kubernetes namespace rentals are not supported through storefronts.

Register your website

  1. Sign in to ComputeCubed Console with the account that owns the listings you intend to offer, and accept the current Terms when requested.
  2. Open Account → Storefronts → Add storefront.
  3. Enter a display name, a unique permanent catalog slug, your HTTPS website origin, and the exact authorization callback and payment return URLs supplied by your website backend.
  4. Save the registration and copy the generated client ID and one-time client secret into your website backend's secure configuration.

For example, a website at https://compute.example could use https://compute.example/auth/callback for authorization and https://compute.example/ for payment returns. Both destinations must belong to the registered origin and contain no query or fragment. You can register up to 20 storefronts per account.

The client secret is displayed only once. Never place it in browser code, browser storage, source control, screenshots or support reports. A personal account API key is not a substitute. No separate identity-service application is required for the supported ComputeCubed connection flow.

Registration creates the connection credentials; it does not publish any machines. Complete listing selection and verify your website's catalog before opening it to customers.

Choose what your website offers

Open Provider → Node listings, create a listing or use Edit for new rentals, and choose your registered website under Where customers can rent. Save the listing. Repeat for each listing you want to offer.

Each node listing belongs either to the ComputeCubed marketplace or to one storefront. Assigning an existing marketplace listing to a website removes it from marketplace discovery. You cannot publish the same listing in both channels simultaneously. You can select all eligible listings you own or a subset; new listings are not automatically added to a storefront.

Only your own active, enabled storefronts can receive listings. Paused or platform-suspended storefronts cannot receive new assignments, and their existing private listings remain outside the marketplace. Changing the distribution does not end accepted rentals or change their agreed prices.

The catalog reflects listing status and observed capacity. A registration or a visible machine does not guarantee that a rental can start: capacity and eligibility are checked again when you accept a quote. See Listings, rental modes, and pricing for pricing and availability controls.

Connect and recharge as a renter

Choose Connect ComputeCubed account on the provider website. Sign in through ComputeCubed's usual identity service, review the website name, address and requested permissions, and approve the connection. Give your password only to the normal ComputeCubed sign-in service; the provider website never needs your password or personal API key. Cancelling leaves the account unconnected and you can try again.

An approved connection can allow the website to read your global Rental Balance, open hosted Stripe Checkout at your request, and manage rentals created through that storefront. It does not expose provider earnings, payouts, account administration or unrelated rentals.

To recharge, enter at least €10 and choose Add credit with Stripe. Complete payment on Stripe's hosted page. The full top-up amount credits your existing global ComputeCubed Rental Balance; it is not a separate provider wallet and can be used across ComputeCubed.

A return from Checkout alone does not confirm credit. The website displays a verification message until the platform confirms payment and updates the balance. A cancelled or unconfirmed payment must not be treated as usable credit. If verification remains pending, check Account billing and payments before attempting another payment.

Payment does not reserve a machine. If price terms expire or availability changes while paying, select the machine and review a fresh quote before accepting a rental.

Rent and connect

Connect your account, select an available machine, and choose the sliced workspace resources and image. Configure your SSH public key in ComputeCubed Console before launching. Review the full renter price, initial balance reservation, contract end and any minimum-time terms, then explicitly accept the rental.

When the workspace is ready, open Connection and details, download its WireGuard profile, activate the tunnel and use the supplied SSH command. The profile contains a private key; keep the downloaded file secret. End rental requires confirmation and settles billing under the accepted terms.

Your complete rental and transaction history remains available in ComputeCubed Console. Public reviews are not available for private storefront rentals in this pilot. See Workspace rentals for connectivity and workspace responsibilities.

Manage settings and credentials

Return to Account → Storefronts to edit your website, pause or resume it, reload the list, or rotate its client secret. The reload icon refreshes the displayed registrations; it does not change credentials.

Changing only the display name preserves customer connections. Destination changes and pausing require confirmation and invalidate previous website tokens and customer connections. Resuming allows customers to reconnect; it does not restore their old grants. Provider controls cannot lift a platform suspension. Running rentals continue and can be managed from Console.

Choose Rotate client secret to replace a lost or exposed credential. The old secret, website tokens, pending approvals and customer connections stop working immediately. The client ID stays the same. Save the replacement secret, update your website backend's secure configuration, and ensure the running backend loads it before asking customers to reconnect. The replacement is also displayed only once.

Disconnect a website

On the provider website, choose Disconnect and confirm. You can also revoke access centrally from Account → Connected rental websites → Disconnect in ComputeCubed Console.

Disconnecting prevents further delegated requests. It does not automatically end existing rentals, which remain subject to their accepted billing rules. Manage or end those rentals from Rentals in ComputeCubed Console.

Was something unclear or out of date?

Include the page title and visible Console version when reporting a documentation issue.

Cookie settings