ACCOUNT
Sign in with a reachable email before you touch inventory; payout rails can wait until you actually withdraw.
← ALL GUIDESYOUR FIRST
01 02 03 04 05 06 WHY THE FIRST RENTAL
SIX STAGES FROM
PICK A TERM THAT
MINIMUM RECOMMENDED COMMIT READ STATUS BEFORE
TOTAL UPDATES LIVE.
FOUR PANELS BEFORE
END CLEAN.
BEFORE YOU OPEN
QUESTIONS THAT SHOW UP
RUNBOOKFR-01
RAR / RENTALS GUIDE · START · ~12 MIN
YOUR FIRST
RENTAL.
Treat the first rental as a controlled experiment, not a career bet. You are proving that you can choose a live unit, clear payment, and read the dashboard without getting lost — so when capital gets larger later, the muscle memory is already there. This walkthrough mirrors the Rent A Rig rental UI end to end: plan length, inventory status, deploy mode, checkout lock, and the four telemetry panels that tell you the machine is actually working.
TERM
Pick 7 or 30 days on your first pass so you learn the dashboard without locking a year of conviction you have not earned yet.
UNIT
Filter to AVAILABLE or LOW STOCK, open DETAILS, and keep Deploy Mode on RENT with quantity set to one.
PAY
Clear checkout so inventory locks on payment confirmation — not on a sold-out click that never reserved anything.
READ
Prove hashrate, power, temperature, and uptime on the dashboard before you trust any revenue model number.
EXIT
Decide renew, upgrade, buy, or stop before term end so the next invoice cycle never surprises you.
OPERATOR BRIEF
WHY THE FIRST RENTAL
IS A LAB, NOT A FLEET.
Operators who skip the lab phase usually fail in quiet ways: they buy because rent “feels expensive,” they host into a bay that cannot feed the wattage, or they panic when revenue estimates wobble even though hashrate and uptime are fine. A short rental forces the real sequence into your hands — account state, term choice, inventory truth, payment lock, dashboard literacy — before any of those mistakes get expensive. If you have not read Rent vs Buy yet, skim it first so you are not second-guessing ownership mid-checkout; then come back here and run the experiment with deploy mode locked to RENT and quantity locked to one.
PROCESS MACHINE
SIX STAGES FROM
SIGN-IN TO EXIT.
LIVE RUNBOOK
DEPLOY SEQUENCEACTIVE
CURRENT OBJECTIVE
STAGE 01 → 06
CONTROLLED FIRST DEPLOY
Move through account readiness, a short contract length, one AVAILABLE unit, payment clear, dashboard confirmation, and a deliberate renew-or-exit decision. Do not parallelize. Do not scale quantity until the first allocation has proven telemetry for at least one full quiet day.
- 01 · ACCOUNTSign in with a reachable email before you touch inventory; payout rails can wait until you actually withdraw.
- 02 · TERMPick 7 or 30 days on your first pass so you learn the dashboard without locking a year of conviction you have not earned yet.
- 03 · UNITFilter to AVAILABLE or LOW STOCK, open DETAILS, and keep Deploy Mode on RENT with quantity set to one.
- 04 · PAYClear checkout so inventory locks on payment confirmation — not on a sold-out click that never reserved anything.
- 05 · READProve hashrate, power, temperature, and uptime on the dashboard before you trust any revenue model number.
- 06 · EXITDecide renew, upgrade, buy, or stop before term end so the next invoice cycle never surprises you.
CONTRACT LENGTH
PICK A TERM THAT
TEACHES, NOT TRAPS.
On /rent, plans price differently by length. Contracts start at 6 months and run through 5 years — longer terms discount the daily rate. Plan price is a tier estimate — the inventory row shows the exact machine daily rate you will pay for that SKU.
FIRST PASS · 6 OR 12 MO
6 MONTHS
ENTRY CONTRACTSHORTEST AVAILABLE TERM
Use six months when you want a full ops cycle — pool strings, worker naming, dashboard literacy, and enough telemetry to know whether hashrate tracks nameplate. It is the shortest contract RAR offers, so treat it as a real commitment rather than a trial window.
12 MONTHS
OPS RHYTHMMOST SELECTED · RATE DISCOUNT
Use twelve months when you already trust the UI path and want a full year of renewals, quiet nights, and how revenue models drift against real pool shares. Most operators who intend to stay on rent start here for the balance of rate and horizon.
2–5 YEARS
COMMITTED RATEAFTER YOU KNOW THE RHYTHM
Multi-year contracts make sense when pool config is boring, Support tickets are rare, and you can name why the discounted daily rate beats a shorter horizon for your capital plan. Max term is five years — come back to long terms when renew, upgrade, or buy is a calm decision instead of a reaction.
LIVE INVENTORY
READ STATUS BEFORE
YOU FALL IN LOVE WITH A SKU.
Open the rental list and filter hard. Hashrate (TH/s), power (W), efficiency (J/TH), and status are the four fields that matter on the first pass — marketing copy is secondary. Click DETAILS to open the rental product page: machine view, deploy mode (Rent vs Host), term chips, and quantity. For a first run, leave Deploy Mode on RENT and quantity on 1.
AVAILABLE
Safe for first deploy. Stock is live, the row rate is the rate you will see at checkout, and you can move through DETAILS → term → pay without racing a disappearing SKU. Prefer AVAILABLE even if a flashier unit sits in LOW STOCK — boredom beats a mid-checkout sold-out for a first rental.
LOW STOCK
Fine if you act now and do not hesitate mid-checkout. Low stock means the allocation can vanish between DETAILS and payment clear, so have account and payment rail ready before you open the page. Skip LOW STOCK on your very first attempt if you are still learning the UI — save the urgency for attempt two.
INCOMING / SOLD OUT
Skip for your first rental. Incoming is a promise, not a lock; sold out is a dead click. Watching an incoming ETA teaches you nothing about dashboard literacy and trains the wrong habit — waiting on inventory theater instead of executing a live unit you can actually pay for today.
CHECKOUT LEDGER
TOTAL UPDATES LIVE.
LOCK HAPPENS ON PAY.
Select 6 MONTHS or 12 MONTHS (up to 5 YEARS) and watch the CTA total update — it multiplies day rate × term × quantity, plus a host premium only if you selected Host. Quantity is how many identical allocations you want; start with one. Complete checkout with the rail offered (crypto, card, or transfer). Inventory locks when payment clears — not when you mash a disabled sold-out control. You should land in account context with the rental marked provisioning or online; if status stalls past thirty minutes, open Support with the rental ID already copied.
LINEDETAILNOTE
DAY RATETaken from the inventory row for the chosen SKUNot the plan tier teaser alone
TERM7 or 30 days multiplies the day rate into the CTAWatch the total before you pay
QTYIdentical allocations; keep at 1 for the lab runScale after telemetry proves out
DEPLOYRENT for first pass — Host adds premium and ownership pathDo not mix modes on day one
LOCKPayment clear reserves the unit and opens dashboard contextSave the rental ID immediately
DASHBOARD LITERACY
FOUR PANELS BEFORE
YOU TRUST THE MODEL.
Revenue estimates are models — useful for direction, not for accounting. Confirm the pool and worker string match what you intended. If hashrate is flat zero while power looks normal, it is usually config, not facility downtime. Focus on these four panels until they feel boring.
TELEMETRY FIRST
HASHRATENAMEPLATE
~TH/sNEAR SPEC
Hashrate near nameplate means the allocation is hashing. Drift within a normal band is expected; a flat zero with healthy power almost always points at pool or worker config. Fix strings before you open an uptime ticket.
POWERDRAW
WATTSIN ENVELOPE
Power draw should sit inside the product envelope for the SKU you rented. Spikes during warm-up can settle; sustained draw far outside the listed watts is a Support conversation with the rental ID attached, not a reason to keep refreshing the revenue card.
TEMPTHERMAL
°CINSIDE LIMIT
Temperature inside the product envelope is healthy facility behavior. If temp climbs while hashrate collapses, you are looking at a thermal or throttling event — document the timestamps and open Support rather than swapping pools in a panic loop.
UPTIMECLOCK
LIVEADVANCING
An advancing uptime clock means the allocation is live on the facility side. Pair it with hashrate before you celebrate — uptime without hash is still a config problem. Estimated $/day moving only proves the model feed is alive; it is not a payout promise and never substitutes for the four hard panels.
RENEW · UPGRADE · EXIT
END CLEAN.
THEN SCALE.
Before term end, decide deliberately: renew the same class, move to a higher SKU, buy hardware, or stop. Ending cleanly beats drifting past contract end without a renewal plan, and it beats extending a machine you already distrust because canceling feels like admitting defeat. If the lab worked — hashrate near nameplate, temp calm, Support quiet — renewing or stepping up quantity is earned. If the lab exposed that you hate reading dashboards, stop; renting more will not fix an attention problem. If ownership now looks rational, open Rent vs Buy again with real numbers from this cycle instead of vibes from before you had telemetry.
Keep the rental ID, the term dates, and a one-line note on pool settings in a place you can find. Future-you will thank present-you when a second rental starts and you are not reconstructing worker names from memory. When you are ready for payouts, read the withdrawals guide before you wire a destination — you did not need that rail to start, but you will need it to finish the cash loop cleanly.
PREFLIGHT
BEFORE YOU OPEN
/RENT.
01 · ACCOUNT — You are signed in with an email you can reach in the next hour, and you are not blocking the experiment on payout setup you do not need yet.
02 · TERM — You have already decided 7 or 30 days so term chips at checkout are confirmation, not a debate under pressure.
03 · UNIT — You will filter to AVAILABLE first, open one DETAILS page, keep Deploy Mode on RENT, and leave quantity at 1.
04 · PAY — Your payment rail is ready, and you will wait for clear before assuming inventory is yours.
05 · READ — You will not declare success until hashrate, power, temperature, and uptime all look sane on the dashboard.
06 · EXIT — You will calendar the term end and decide renew, upgrade, buy, or stop before the invoice cycle decides for you.
DESK FAQ
QUESTIONS THAT SHOW UP
ON FIRST DEPLOYS.
HOW LONG UNTIL HASH SHOWS?
Most rentals show telemetry within minutes of payment clear. Provisioning can sit briefly in a pending state while the facility attaches the allocation; that is normal. If nothing appears after thirty minutes — no hashrate, no power, no uptime advance — contact Support with your rental ID rather than starting a second checkout that doubles confusion.
CAN I CHANGE POOLS LATER?
Yes for rental allocations through the dashboard or Support. Keep a note of prior worker names when you rotate so you can confirm the old string went quiet and the new string picked up share. Changing pools will not fix a sold-out mistake or a term you regret — it only redirects where proven hashrate lands.
WHAT IF I PICKED THE WRONG TERM?
Flex terms are the easiest exit path. Fixed terms follow the cancellation rules shown at checkout, which exist so inventory planning stays honest for everyone on the facility. Open Support early if you need an exception; last-day emergencies are harder to unwind than a calm request made when you first realize the mismatch.
WHEN DO I ADD WITHDRAWALS?
After the lab works and you care about moving value off the platform. You do not need a payout destination to start a rental, and wiring one mid-checkout only adds friction. Read the withdrawals guide when revenue is real enough to protect — not before you can read the four telemetry panels cold.