The questions that come before an order.

Start with the software and a representative unit of work. Note the required GPU memory, the full execution time, the transfers and the overlapping tasks. Then compare a few configurations using the same parameters, rather than choosing only the most recent card. The catalog states the model, the memory per card and the composition of the lot. Your decision must tie these elements to the schedule and the outcome expected by the team.

The stated memory corresponds to one card. It must hold the data and structures used by your software during execution, with requirements that can vary depending on the parameters. Measure the peak on a representative job and keep its launch conditions. GPU memory, system memory and storage play different roles: a large capacity in one does not guarantee that the other constraints of your processing are met.

No. The application must be able to distribute its data and computations across the cards. Some workloads allow launching several independent tasks; others require distributed operation and exchanges between GPUs. These are two different needs. Check what your software supports before increasing the number of lots. The total memory of several cards must not be presented as a single capacity available to any program.

A B200 lot contains two cards. The price shown for the chosen duration already covers this full lot. By choosing two lots, you are requesting four GPUs and the total corresponds to two lot packages. The other models in the catalog are offered with one card per lot. Choose the quantity based on the work you can actually distribute; the configurator distinguishes the number of lots from the total number of cards to avoid counting the same hardware twice.

Choose the duration that covers your full cycle: installation, import, computation, verification and retrieval of results. A three-day period may suit a processing job ready to launch; seven days cover a work week; thirty days accompany several cycles or a continuous workload. These guidelines are not performance estimates. Prepare your files and your procedure before provision so you can devote the rented period to useful operations.

The start of service corresponds to the effective provision, according to the terms of your order. Creating the case or clicking "I have paid" does not start this period. Your tracking distinguishes payment from provision of the GPU. To organize the team, record the confirmed receipt date and the associated end date, then plan an internal decision early enough to finish the processing or prepare a new period.

No, a new period requires a new order. Your team can thus review the model, the number of lots and the duration before continuing. Do not wait until the deadline to decide: allow time to finish the last jobs and retrieve their outputs. If you change configuration, also keep the software versions and a usable restart state. An early decision makes continuity easier without confusing two successive orders.

Start with the software, extensions and libraries your work depends on. For an application using CUDA, check the NVIDIA configuration compatible with its version. For an AMD Instinct target, review the ROCm stack suited to the model and system, along with the project's dependencies. High memory capacity alone is not enough to establish compatibility. Keep a precise list of versions and run a representative workload before moving your entire pipeline.

Yes, you choose the software and workloads that run on your GPU. Capordia does not inspect the content of your files, prompts or computations. Your team handles the installation, access, necessary licenses and usage rights for the data it provides. To make a restart easier, keep your versions and your launch procedure. This autonomy concerns the use of the compute; it does not remove the contact details and information needed to track the order.

Capordia does not ask for an identity document or a KYC screening procedure for rental and crypto payment. First name, last name and email are requested at sign-up, along with a password to protect account access. The email serves as an identifier without verification by message. The absence of KYC therefore does not mean an absence of order data or absolute anonymity. Use appropriate contact details and never share your private key.

Open the intent corresponding to your order and check together the asset, network, address, exact amount and deadline. The same token symbol can exist on several networks; the network displayed must match the one chosen for the transfer. Take into account the fees charged by your wallet or platform. After sending, use “I have paid” on the correct intent, then track its status without making a new transfer simply because verification is still pending.

The button records a time-stamped report for the selected payment intent and leaves the settlement pending. Tracking updates automatically; a second click does not create a second payment. Only confirmation from the payment service validates the settlement. The click does not prove receipt, does not credit your balance and does not declare the GPU delivered.

For an order still awaiting settlement, choose the intent whose asset, amount and date match the transfer made. Report the payment on that intent, even if it appears in the history. Do not automatically use the most recent one: its amount or asset may be different. An old transfer must not be repeated to match a new screen. Settled or cancelled orders keep their history in read-only mode; contact support if you need their case reviewed.

A top-up and a rental are two separate files. Reporting alone does not change the balance: the credit waits for confirmation from the payment service and can be recorded only once. Tracking shows the updated balance after confirmation. When the available USD balance is sufficient, you can choose to settle a rental with that balance. This use remains attached to the order concerned and does not automatically allocate a GPU. The history distinguishes top-ups, rental settlements and remaining balance.

Keep the order reference and the intent concerned, then describe the discrepancy in a support request. An incomplete amount, an excess or a transfer on another network must not be interpreted as an automatically settled payment. Avoid multiplying sends to correct the situation without reconciling the first transfer. The case must make it possible to understand what was expected, what was reported and the outcome chosen; a refund or recovery cannot be assumed.

Sign in with the email and password of your Capordia account. You will find the same orders, balance and support requests from another browser. Signing out revokes the current session without deleting the folders. In the settings, changing your password requires the current password and revokes the other sessions. No reset email is available if you forget it. Keep your references in your team register, without sharing the account password there.

Separate the inputs you already own, the results produced and the state needed to resume work. Export the outputs to a location controlled by your team and check that they open from that destination. Also keep the software versions, the settings and, depending on the application, the checkpoints. A copy that stays only on the compute environment does not prepare a handover. Assign export verification to one person and schedule it before the final deadline.

Define a resume boundary: last validated batch, position in the queue or checkpoint associated with the right data. Plan where new inputs wait during the transfer and which process is allowed to publish results. Repeat the copy, the restart and the output comparison on a controlled scope. The plan must also state when to revert to the previous environment and how to preserve the work already done on the target. Copying files alone does not cover these decisions.

Link the project's internal reference to the order, its amount, the settlement statuses and the provisioning. Keep each document in its role: a summary describes the order, a payment receipt describes a confirmed settlement and an invoice serves its own purpose. The technical team adds its acceptance criteria and results. Compute data, credentials and secrets do not need to circulate in this administrative register; share only the information useful to each party.

Give the reference concerned, the step in the journey, the time of the observation and the expected result. Describe the actions already attempted and the message displayed, without adding any password, private key or sensitive content. For a GPU question, specify the software and its version; for a payment, use the order and the selected intent. A factual description helps distinguish an access, a processing, a payment and a delivery issue, which do not require the same checks.