← Back|VNISH NINJA / Enterprise
For farms and fleets

Deploying VNISH across a fleet

A practical, honest playbook for professional operations. Everything below uses the same public builds, checksums and tools as the rest of this site - nothing enterprise-only is hidden.

Staged rollout: 1 → 10 → 100 → fleet

  1. Pick one representative miner per model/board combination. Install from its exact kit page, verify SHA-256 before flashing.
  2. Run 24 hours. Compare J/TH, temperature bands and stability against your stock baseline for the same machine.
  3. Extend to 10 units per model. Keep pools, presets and firmware file identical - the toolkit batch-installs from one verified local file.
  4. Extend to 100, then the fleet. Stagger installs per aisle or PDU so power swings stay predictable.

Rollback runbook

  1. Per miner: web UI, System, Backup and Restore, Return to stock firmware - about a minute per unit.
  2. Per batch: schedule rollback windows per row; the toolkit shows per-miner status in its Operations panel.
  3. Non-booting board: SD recovery or factory unlock - contact support with the model and stock date for the verified image.

Note: whether the manufacturer's warranty covers third-party firmware is decided by Bitmain and your vendor - check your terms before a fleet rollout.

Version policy

Current stable: v1.3.4 for all 45 models, one build per control board, SHA-256 published next to every file and in the machine-readable manifest. New stable versions replace downloads on this site; your installed fleet keeps running until you choose to update.

Benchmark methodology

Spec tables on model pages show manufacturer stock ratings. Preset examples (e.g. Antminer S21 Pro: stock 234 TH at 3510 W vs efficiency ~224 TH at 2934 W) are measured on the dashboard presets named in each article; your numbers depend on cooling, ambient and power quality. Test on your own machine first - that is the whole point of the staged rollout.

Automation and API

Machine-readable layer for your tooling: firmware-catalog.json · install-routes.json · checksum-manifest.json · OpenAPI. Every install kit also exists as JSON under /api/v1/install-kits/.

Terms for volume

Individual terms for high-volume and enterprise miners are agreed directly - use the contact on the main page and mention your fleet size and models.

Contact us All models