Forty practical answers, organized by task.

A dedicated GPU configuration means one card is reserved for one customer for the paid term rather than time-sliced. Actual allocation is confirmed only when provisioning succeeds.
Link to this answer ↗

The catalog covers NVIDIA and AMD models across Dallas, Ashburn, and Portland. Catalog quantities are reference values; current availability must be confirmed before an order is accepted.
Link to this answer ↗

Configurations support 1, 2, 4, or 8 cards. The catalog applies the published volume discount to 2-, 4-, and 8-GPU nodes and shows the complete 7- or 30-day price before deployment.
Link to this answer ↗

Start with required VRAM, software compatibility, latency or throughput goals, and whether the workload can use multiple cards efficiently. Multiple GPUs do not automatically behave as one shared memory pool; the application must support sharding or parallel execution.
Link to this answer ↗

Provisioning time is not published. A deployment must remain pending until the infrastructure provider confirms a usable machine.
Link to this answer ↗

No. The intended signup flow uses a unique username and password without requesting an email address, phone number, or identity document. The Acceptable Use Policy and applicable legal obligations still apply.
Link to this answer ↗

Recovery codes are shown once when the account is created. Store them offline and separately from the password; they are the recovery path when no email address or phone number is attached to the account.
Link to this answer ↗

The account may not be recoverable because support has no verified email or phone identity to fall back on. Never assume that a wallet transaction, username, or support message alone proves account ownership.
Link to this answer ↗

Add a supported SSH public key, such as Ed25519 or ECDSA P-256. Never paste a private key, seed phrase, recovery code, password, or API secret into the dashboard or a support request.
Link to this answer ↗

API secrets should be displayed only when created and stored as hashes by the service. Revoke a key or active session if it is exposed, and use a separate key for each system so access can be withdrawn independently.
Link to this answer ↗

No. A weekly term is exactly 7 consecutive days and a monthly term is exactly 30 consecutive days. There is no hourly meter inside either fixed term.
Link to this answer ↗

The total starts with the published per-card price, multiplies it by the selected card count, applies the published node discount, and adds selected options. The complete USD-denominated amount should be visible before any balance is charged.
Link to this answer ↗

The billing rule debits the full fixed-term amount only after capacity is accepted for deployment. The displayed balance is derived from individual ledger entries.
Link to this answer ↗

No. A quote describes a configuration and price for a limited period; capacity is reserved only when a deployment is accepted. Availability may change between viewing a quote and submitting the deployment.
Link to this answer ↗

The price for an active 7- or 30-day term does not change. The applicable renewal price must be shown before the next charge.
Link to this answer ↗

Only after checkout displays a confirmed payment request linked to your order. The addresses shown can be real: verify the asset, network, address, amount, and order reference before sending. Never send funds during testing or from an unconfirmed screen.
Link to this answer ↗

Checkout lists BTC on Bitcoin, ETH on Ethereum, USDT on TRC-20, USDC on ERC-20, XMR on Monero, SOL on Solana, and LTC on Litecoin. Availability depends on the payment integration. Sending an asset on another network may be unrecoverable.
Link to this answer ↗

The displayed thresholds are 1 confirmation for BTC, 12 for ETH, 19 for USDT TRC-20, 12 for USDC ERC-20, 10 for XMR, 32 for SOL, and 6 for LTC. Credit must occur only after the payment integration confirms the required threshold.
Link to this answer ↗

Checkout shows an indicative, time-stamped conversion for a chosen USD amount. It is not a payment request or locked rate; network and withdrawal fees are excluded, and payment confirmation is handled separately.
Link to this answer ↗

Withdrawals are not enabled until limits, rate handling, network fees, review timing, asset provenance, and processing responsibilities are published.
Link to this answer ↗

When enabled, automatic renewal is attempted 24 hours before the current term expires. The renewal must create only one charge for that billing period, even if a scheduled job is delivered more than once.
Link to this answer ↗

The instance continues until the paid term ends, then stops. Its reservation and local data remain in a 72-hour grace period before final release; no partial renewal or negative balance should be created.
Link to this answer ↗

The intended lifecycle allows renewal while the instance remains in grace if sufficient eligible balance is available. Once release has completed, the former instance and its local data cannot be restored.
Link to this answer ↗

Stopping is reversible and does not pause or extend the paid term. Release is permanent in the account workflow; infrastructure data deletion depends on the provisioning integration and published retention policy.
Link to this answer ↗

Yes. Automatic renewal can be disabled before the renewal attempt, and a manual renewal can be requested while the instance remains eligible. The account should always show the resulting term end and charge.
Link to this answer ↗

The catalog lists Ubuntu, PyTorch, vLLM, ComfyUI, Ollama, JAX, ROCm, and Debian starting points. Image availability depends on GPU vendor compatibility; for example, ROCm targets supported AMD configurations.
Link to this answer ↗

The intended dedicated-node service provides administrative access so customers can update packages, run containers, and configure their workload. Customers remain responsible for licenses, security updates, and compatibility with the selected hardware.
Link to this answer ↗

The account lifecycle treats local NVMe as part of the instance. Stopping preserves its allocation during the paid term or grace period; final deletion depends on the provisioning integration and retention policy. Do not treat local NVMe as a backup.
Link to this answer ↗

The catalog can quote extra NVMe storage, a dedicated public IPv4 address, additional bandwidth, and a private colocation VLAN. Availability, limits, and the exact period price should be confirmed before deployment.
Link to this answer ↗

Do not assume either. The deployment quote and documentation must state included transfer, purchased increments, enforcement behavior, and any overage policy. Backups exist only when a specific backup or persistent-storage product is selected and documented.
Link to this answer ↗

The intended design does not inspect workload content by default; actual isolation and operator access still need production verification. Limited host, network, account, billing, and security information may be processed when needed to operate the service, investigate authorized support, respond to an active threat, or meet a valid legal obligation.
Link to this answer ↗

The intended records include account and session data, public SSH keys, API-key hashes, ledger and transaction records, instance configuration, support messages, and limited security telemetry. Exact retention periods and subprocessors must be stated in the production Privacy Policy.
Link to this answer ↗

Customers are responsible for protecting passwords, recovery codes, SSH private keys and API secrets; applying software updates; limiting exposed services; and securing their own data and backups. Dedicated hardware does not make an unsafe workload secure.
Link to this answer ↗

The service must not be used for malware, phishing, credential theft, botnets, unsolicited messaging, denial-of-service attacks, unauthorized access, exploitation of minors, interference with other tenants, or unlawful conduct. Security testing requires authorization from the target.
Link to this answer ↗

No. It means identity documents are not requested at signup. AnchorGPU may still enforce its Acceptable Use Policy, protect customers and infrastructure, investigate credible reports, and respond to valid legal process.
Link to this answer ↗

Normally no. A fixed term reserves dedicated capacity for all 7 or 30 days, so stopping or releasing a healthy instance early does not create an automatic prorated refund.
Link to this answer ↗

A verified duplicate debit or deployment that never becomes usable should be corrected with a separate compensating ledger entry. Existing accounting entries should not be silently edited or deleted.
Link to this answer ↗

Service-credit eligibility depends on an approved SLA covering exclusions, measurement, claim windows, and the credit schedule. No uptime or credit commitment is made until that SLA is published.
Link to this answer ↗

Catalog entries are not binding offers. Before accepting an order, a listing must confirm stock, condition, test results, included items, exact price, location, and serial-specific details.
Link to this answer ↗

Used-hardware orders must not be accepted until the listing and sales terms disclose payment, delivery regions, shipping responsibility, taxes or duties, transfer of title, warranty, returns, and item condition.
Link to this answer ↗