Overview

QuickPod hosts supply GPU or CPU capacity to the QuickPod marketplace and manage their listings from the hosting side of the console.

Important public and host-related routes:

• Public marketplace search: https://console.quickpod.io/

• Public host directory: https://console.quickpod.io/host-stores

• Host console area after login: /hosting

• Host occupancy analytics after login: /occupancy

• Host contracts after login: /contracts

• Host storefront management after login: /my-store

What hosts manage today

The current hosting experience goes beyond simple machine listing.

Hosts now manage:

• machine health and listing state

• GPU and CPU offer pricing

• minimum GPU grouping and max duration rules

• privileged access eligibility

• occupancy and reliability visibility

• payout setup and payout history

• contract visibility

• public host storefront branding and sharing

Core host responsibilities

Hosts are still responsible for machine setup, networking, system reliability, thermal stability, driver health, and predictable uptime.

QuickPod expects listed machines to have working open ports, stable networking, and healthy hardware.

Listings and contracts

An offer is the rentable unit presented to users in the public search console. When a user launches on your offer, that activity becomes part of your host-side contract and revenue history.

Duration, pricing, and hardware grouping influence how your machine appears in the search marketplace.

Newer host-facing surfaces the old docs missed

Occupancy analytics

Hosts can inspect occupancy and usage trends from the dedicated occupancy route.

Contracts

Hosts can review contract history and cost-related details from the contracts route.

Earnings and payouts

Hosts can configure payout providers and track payout history from the earnings and billing-related host surfaces.

Host stores

Hosts can publish a branded storefront and share public links to their offers.

See Host Stores & Analytics for the newer host experience.

Maintenance guidance

Avoid disruptive maintenance while customer workloads are active. Delisting prevents new contracts, but existing workloads and contract expectations still matter until they expire or are terminated cleanly.