Max hashrate, best efficiency, low noise, hosting ready, or budget — pick the primary driver so the desk knows which trade to sacrifice first. Secondary wants belong in notes as ranked preferences, not as five simultaneous “musts.”
← ALL GUIDESCUSTOM RIG
CONSTRAINTS BUILD BOMS.
FILL THE FORM THE
FIELD · GOALPRIMARY OBJECTIVE FIELD · POWERENVELOPE BAND FIELD · BUDGETHONEST USD CEILING FIELD · PATHHOST AFTER BUILD / SHIP ONE TIGHT PARAGRAPH
BUILD → INTAKE
BUILD → FREIGHT
WHAT A REAL REPLY
KEEP THE QUOTE ID
BEFORE YOU HIT
QUESTIONS BEFORE
RAR / HARDWARE GUIDE · ADV · ~11 MIN
> make me the best miner > somehow quiet and max hash > budget: "flexible" > ship? host? idk ERR · NO CONSTRAINTS ERR · NOT ACTIONABLE
GOAL · BEST EFFICIENCY POWER · UP TO 3.5 kW BAY NOISE · FACILITY OK BUDGET · $12,400 CEILING PATH · HOST AFTER BUILD INTAKE · RACK · WEEK 14
CUSTOM RIG
BRIEFS.
A good custom rig request reads like an engineering brief, not a wish list. The hardware desk returns real BOMs when you specify goals, power, noise, budget, and whether the build will host at Rent A Rig or ship to you. This terminal guide shows why briefs fail, how to fill the form fields the desk actually sees, how to write notes like an operator, what a real BOM contains, and what to do after the quote — including the valid outcome where custom work simply points you back to a store SKU.
DESK DOCTRINE
CONSTRAINTS BUILD BOMS.
WISHES BUILD DELAYS.
“Make me the best miner” is not actionable. Desk engineers need a budget ceiling, a kilowatt limit, a noise limit, an algorithm target, and a timeline. Failed briefs also omit hosting intent: a rack-dense build and a quiet edge build are different shopping lists, different fans, and different freight. If you have not decided host-after-build versus ship-to-me, the desk cannot choose between hall density and residential manners. Read Reading Efficiency before you invent a power band that fights your own J/TH goals, and read Hosting Basics before you ask for a machine that will not fit the bay you think you want.
SPEC SCHEMA
FILL THE FORM THE
DESK ACTUALLY SEES.
On /custom-rig, fill name, email, primary goal, power envelope, budget, notes, and host-after-build versus ship-to-me. The request packet on the right of that form is what the desk reads — keep it accurate, not aspirational.
LIVE FORM FIELDS
A balanced brief has tension on purpose: goal pulls against power, noise, budget, and time. If every axis is “max,” you have not briefed — you have wished.
Choose a band that matches your breaker or bay continuous rating with headroom. A brief that asks for M160-class draw into a 3.5 kW bay is a contradiction the desk will send back; fix the envelope before you ask for a quote cycle.
Include shipping and taxes if you are self-hosting. “Flexible” is not a number. A ceiling lets the desk shortlist instead of guessing whether you want a flagship or a compromise SKU that still meets the goal.
Host-after-build versus ship-to-me changes BOM, packaging, and lead time. Say it explicitly. If hosting, name the tier intent; if shipping, name the country and whether a liftgate is required.
OPERATOR NOTES
ONE TIGHT PARAGRAPH
BEATS FIVE OPINIONS.
Include ambient temperature range, elevation if relevant, single-phase versus three-phase, and whether you can accept loud fans overnight. If hosting, say which tier you want and when the intake window opens. If shipping to you, say country and liftgate needs. Market monologues about hashprice waste desk cycles; constraint sentences accelerate quotes.
− WEAK NOTES
I think mining is the future and I want something powerful but also efficient and maybe quiet if possible. Not sure about hosting yet. Budget depends. Please advise on whatever is best right now given the market.
+ STRONG NOTES
Single-phase 3.5 kW continuous at site ambient 18–32°C; overnight noise OK (facility host). Goal: best efficiency in envelope. Host after build into RACK; intake opens week 14. Budget ceiling $12,400 hardware only; RAR hosting billed separately. Need one spare PSU if lead time exceeds 21 days.
DESTINATION · HOST
BUILD → INTAKE
→ TELEMETRY.
Host-after-build means the BOM optimizes for hall density, facility power ceilings, and intake paperwork. Name bay, rack, or pod intent and the week intake can accept freight. The desk will not assume a pod because you said “serious.” Pair the brief with a hosting rate conversation before you approve a dense SKU that only pencils at a rate you never confirmed.
DESTINATION · SHIP
BUILD → FREIGHT
→ YOUR SITE.
Ship-to-me means noise, phase, and breaker limits are yours to state with numbers. Country, liftgate, and indoor path matter as much as J/TH. Budget must include logistics or the “accepted” quote will grow after you thought the decision was over. Edge goals belong here; hall-density goals usually belong on the host port instead.
BOM PRINTOUT
WHAT A REAL REPLY
LOOKS LIKE.
Expect a machine recommendation or shortlist, estimated watts, expected J/TH class, ship versus host path, lead time, and a quote validity window. If the desk asks a clarifying question, answer with numbers — every round-trip without data slows your quote.
RAR HARDWARE DESK · QUOTE PREVIEWVALIDITY · ILLUSTRATIVE
RECOMMENDATIONHASHCORE M-CLASS SHORTLIST
EST. WATTS~3.1–3.3 kW
J/TH CLASS~22–24 J/TH
PATHHOST · RACK INTAKE
LEAD TIME14–28 DAYS
QUOTE WINDOW7 DAYS TYPICAL
Sometimes the custom path resolves to “buy the store SKU and host.” That is a successful brief outcome, not a failure — the desk saved you a custom lead time when stock already met the constraints. Compare any BOM against live /hardware cards before you accept.
QUOTE LIFECYCLE · ILLUSTRATIVE
BRIEF IN
CLARIFY
BOM + QUOTE
ACCEPT / BUY
BUILD / SHIP
AFTER THE QUOTE
KEEP THE QUOTE ID
IN THE ORDER.
Compare the BOM against store SKUs you could buy today. When you accept, keep the quote ID in your order notes so Support and logistics stay aligned with the desk that sized the build. Submit the request once with complete fields, then respond fast to clarifying questions — serial half-finished briefs and silent inboxes are how lead times stretch without anyone touching steel. Payment happens only after you accept a quote and checkout; the request itself is not an invoice.
SUBMIT PROTOCOL
BEFORE YOU HIT
SEND ON THE FORM.
GOAL — Primary objective selected on the form so the desk knows which axis wins when trades appear.
POWER — Envelope matches real breaker or bay continuous capacity with headroom, not a fantasy draw.
BUDGET — USD ceiling includes logistics if you are shipping to yourself; hosting power billed as its own line of truth.
PATH — Host-after-build or ship-to-me chosen explicitly, with tier or country detail in notes.
NOTES — Site constraints and deadline in one tight paragraph; no market essay.
CADENCE — Submit once, then answer desk questions with numbers inside the quote window.
DESK FAQ
QUESTIONS BEFORE
THE BOM LANDS.
IS A CUSTOM BUILD ALWAYS FASTER THAN STORE STOCK?
No. If stock matches your brief, the desk will tell you to buy the SKU. Custom shines for constraints stock cannot meet — unusual envelopes, specific noise goals, or host-ready bundles that need coordinated intake. Faster is not the default promise; fitter is.
CAN I REQUEST NON-SHA-256?
Say so in notes. Catalog focus is SHA-256 HashCore-class, but the desk can advise on availability. Do not hide algorithm intent inside a vague “best miner” line — surface it so the first reply is not a reset.
DO I PAY BEFORE THE BOM?
No. You submit a request first. Payment happens only after you accept a quote and checkout. Treat the brief as engineering intake, not as a cart. If someone pressures payment before a written BOM, you are no longer on the hardware desk path.
WHAT IF MY BRIEF CONFLICTS WITH ITSELF?
The desk will say so. Max hashrate, minimum watts, residential silence, and a tiny budget cannot all win. Rank the constraints in notes so the reply can optimize the top two instead of stalling on an impossible four-way tie.