Hosted ASIC mining farm software
Hosted ASIC mining farm software built for fleets measured in tens of megawatts: per‑rig telemetry, active pool switching, and scheduled power‑rate windows fused into one audit‑locked P&L. Ferrohive runs the loop; you read the ledger.
Ledger
One row per rig, per UTC day, audit‑locked.
The ledger at src/lib/business/rig-ledger.ts rolls hashrate, uptime, kWh, pool fee, and grid‑price window into a single row finance can hand straight to audit. The dashboard renders the same shape, so what landed in the morning email is what finance reads — not a re‑derived view from a vendor console.
- Per‑rig uptime × th‑days
- Pool fee × grid‑price window
- Net margin to the rig level
- Effective ¢/kWh per row
- A-01424.0 h114.2+$1.91healthy
- B-00723.4 h 95.7+$0.74throttled
- C-031 4.1 h 0.0 −$0.88fault
- D-00924.0 h109.7+$1.84healthy
Sample ledger — what the daily digest contains for one site in a single UTC day.
Why B-007 just moved
- Foundry · AntPool · ViaBTC · F2Pool · Luxor supported out of the box.
- Weighs hashprice + fee + grid price in one pass before re‑routing.
- Every switch is logged against the rig's audit row — who, when, why.
Route
Active pool switching the moment profitability dips.
The agent rewires rigs across Foundry, AntPool, ViaBTC, F2Pool, and Luxor the second the combined signal of hashprice, pool fee, and grid price tells it to. No on‑call engineer, no per‑site console, no spreadsheet of who's pointed where.
Decisions are logged against each rig's audit row so finance can replay the reasoning, not just the outcome.
Schedule
Scheduled power‑rate windows, the agent reads them as data.
Operators wire cheap‑rate and curtailment windows into /sites/[id]/power-windows; the agent folds each window into the per‑row kWh cost before it lands in the ledger. A midnight cheap‑rate block and a 4 MWh curtailment band read as two different numbers on the same rig — not one blended ¢/kWh guess.
Cheap‑rate windows
Off‑peak kWh lands at the actual published rate, not a blended average.
Curtailment windows
Hash down‑shifts fold into the row, ready for an LP‑grade curtailment dispute.
Demand‑charge bands
Site peaks that cross a demand threshold show up in the digest, not your bill.
Power‑rate windows — site bravo, 2026‑07‑30 UTC
| Window | Local | UTC | Band | ¢/kWh |
|---|---|---|---|---|
| Cheap rate | 00:00 → 06:00 | 04:00 → 10:00 | off‑peak | 2.91 ¢ |
| Shoulder | 06:00 → 16:00 | 10:00 → 20:00 | mid‑day | 4.19 ¢ |
| Curtailment | 16:00 → 20:00 | 20:00 → 00:00 | demand | 6.84 ¢ |
| Shoulder | 20:00 → 24:00 | 00:00 → 04:00 | mid‑day | 4.19 ¢ |
Answers for hosted‑mining operators
Questions operators ask before they switch.
A five‑objection rundown of how Ferrohive resolves in practice — scale, scope, offline behaviour, rig load, and curtailment disputes — before you run a single site under monitoring.
Take the next step
See the pricing tier, or read the operator FAQ first.
Tier shape is published on the pricing page; the operator FAQ is free to read and answers the recurring objections before you sign.
Run the agent against one site for 30 days.
Bring a single site, point Ferrohive at its server, and ship the daily digest to your inbox for a month. Keep the audit log whether you sign or not.
One site · thirty days · your data