App builder

See every rig, watt and payout
in one crypto mining dashboard.

Tell the agent how your sites, machines and pools are set up, and get a web app that tracks hashrate, uptime, power cost and repairs — with a live preview and code you can export.

Start building free More app ideas
Starter prompt

Build a web app for a bitcoin mining operation with three sites. Register every machine with its model, serial, owner, site, rack position, rated hashrate in TH/s, rated watts and status. Each day, record a reading per machine: the hashrate the pool credited, the rejected share rate, hours hashing and the payout in coin. Give each site a rate per kilowatt-hour, then rank machines by payout value minus power cost. Technicians sign in on a phone at the rack, raise work orders with a fault type and photo and close them with the parts used and hours lost.

Build it in Netiva Paste the prompt into a new workspace and adjust it to your business.
Overview

Who this crypto mining dashboard is for

A mining site keeps its numbers in four places: the pool dashboard has yesterday’s payout, each machine reports its own hashrate, the utility bill turns up a month late and the repair history is whatever the technician remembers. So when a hashboard dies or the tariff moves, nobody can say which units are still worth the power. A crypto mining dashboard built in Netiva puts sites, machines, daily readings and work orders behind one login, so every rig carries its own uptime, power cost and repair record.

Key features

What your crypto mining dashboard can do

  • Every machine on the register

    Each unit gets a record with its model, serial, owner, rated hashrate and watts, the site and rack it sits in and whether it is hashing, underclocked, down or waiting on the spares shelf.

    • Rack, row and shelf on every unit, so a fault list reads as a walk order
    • Statuses for hashing, underclocked, down, spare and retired
    • Owner on each machine, whether it is yours or a hosting client’s
    • Saved views per site, per model and per owner

  • Hashrate and payouts from your pool

    The app calls your pool’s API with the key stored securely and files each worker’s hashrate, rejected share rate and payout against the machine it belongs to. Where a pool offers no API, a shift lead types the day’s figures in.

    • Pool-credited hashrate stored beside the machine’s rated terahashes
    • The day’s rejected share rate on every reading, so a failing hashboard shows early
    • Payouts recorded in coin and in value on the day they landed
    • An overnight email listing workers the pool has stopped crediting with hashrate

  • Power cost per machine and site

    Rated watts and the hours a machine actually ran become kilowatt-hours, priced at the rate you pay at that site, so the margin screen can rank units by what they earn against what they burn.

    • Kilowatt-hours from rated watts times hours hashing, divided by 1,000
    • The rate you pay per kilowatt-hour at each site, beside the rate you bill hosted machines at
    • Efficiency in joules per terahash from rated power and hashrate
    • Machines earning less than their power cost listed first

  • A work order queue for the aisle

    Technicians scan the barcode on a unit’s serial label with the phone camera to open its record, raise the fault, attach a photo of the board or error screen and close the job with the parts used and the hours lost.

    • Fault types for hashboards, power supplies, fans, controllers and network
    • Photos attached to the job, not buried in a chat thread
    • Downtime hours totaled per machine, model and fault type
    • Technicians sign in and see the jobs assigned to them
Data model

The collections behind it

Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.

Sites

Each location you run machines in, with the power it can draw and what that power costs.

  • Name (required) Text
  • Capacity in kilowatts (required) Power available to the site at the meter Number
  • Power rate (required) All-in cost per kilowatt-hour; update it when your tariff changes Number
  • Hosting rate Per-kilowatt-hour rate you bill hosted machines at this site Number
  • Cooling Air, immersion or hydro Text
  • Meter reading Latest kilowatt-hours off the utility meter, to check the app’s math Number
  • Meter read on Date
  • Notes Paragraph

Machines

One record per miner, from the shelf it sits on to the name it submits shares under.

  • Model (required) Manufacturer and model as printed on the unit Text
  • Serial number (required) Set each miner’s pool worker name to its serial so readings match the machine Text
  • Owner (required) Your operation or the hosting client; the client statement groups and signs in by it Text
  • Site (required) Relation to Sites
  • Rack position Rack, row and shelf, such as B-04-12 Text
  • Rated hashrate (required) Terahashes per second at the settings you actually run Number
  • Rated power (required) Watts at the wall at those same settings Number
  • Status (required) Hashing, underclocked, down, spare or retired Text

Readings

What a machine did in one day: the hashrate the pool credited, the reject rate, hours hashing and the payout.

  • Machine (required) Relation to Machines
  • Date (required) Date
  • Worker name As returned by the pool, before it is matched to a machine Text
  • Pool hashrate Average terahashes per second the pool credited that day Number
  • Rejected share rate Percent of submitted shares the pool rejected Number
  • Hours hashing (required) Drives the power math; 24 for a full day with no stops Number
  • Payout Coins credited for the day under your pool’s payout scheme Number
  • Payout value Value on the day, from the price source you choose Number

Work orders

Every fault, swap and clean, with the parts used and the hours the unit was down.

  • Machine (required) Relation to Machines
  • Raised at (required) Date & time
  • Fault type (required) Hashboard, power supply, fan, controller, network or firmware Text
  • Status (required) Open, waiting on parts, in progress or closed Text
  • Assigned to The technician who owns the job; defaults to the signed-in user and can be changed Text
  • Photo Image
  • Parts used Paragraph
  • Downtime hours From the fault being raised to the unit hashing again Number

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

A typical first version. Ask the agent for more, or annotate the preview to change any of them.

  • Fleet

    Every unit with its site, rack, status, rated hashrate and the hashrate the pool credited yesterday, filtered by site or model.

    Signed-in users

  • Machine detail

    One unit’s daily readings, uptime, power cost, payouts and its full work order history, opened by search or by scanning its serial barcode.

    Signed-in users

  • Not hashing

    Workers the pool has credited with no hashrate since the last check, or well under their rated terahashes, sorted by site and rack.

    Signed-in users

  • Margin by machine

    Payout value against power cost for the period you pick, ranked by machine and grouped by model and by site.

    Your team

  • Work orders

    The repair queue for a site, filtered by status, fault type and technician, opened and closed from a phone in the aisle.

    Signed-in users

  • Client statement

    A hosting client’s own machines, their kilowatt-hours for the month at that site’s hosting rate and the payouts credited to those units.

    Signed-in users
How it works

From prompt to a live crypto mining dashboard

  1. Describe your sites and fleet

    Tell the agent how many sites you run, what you pay for power at each one and which pools you mine to. It drafts collections for sites, machines, readings and work orders.

  2. Load the register

    Paste your machine list into the collection grid, then ask the collection assistant to tidy models, serials and rack labels across hundreds of rows at once. Rename each miner’s pool worker to its serial as you go, or map the strays by hand.

  3. Wire up the pool feed

    Add your pool’s API token with monitoring or read permission only, point the agent at the endpoint that returns worker hashrate and payouts and check the first readings in the preview. Annotate anything that looks wrong and it gets fixed.

  4. Open it to the crew

    Publish to your own domain, give each technician their own sign-in to the app and switch on the overnight check. Any edit you regret rolls back to an earlier checkpoint.

Why Netiva

Netiva vs a traditional build

Building a crypto mining dashboard with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Knowing what a rig earns Payout value and power cost on the same machine record, priced at the rate that site pays The pool dashboard in one tab, a power bill in another and a spreadsheet to join them up
Finding a dead machine Workers the pool has stopped crediting with hashrate listed by rack, with an email waiting in the morning Someone spots a dip in the pool graph, then walks the aisle listening for the unit that went quiet
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A 40-machine shed behind a workshop

    One owner runs two rows of air-cooled units on a commercial tariff. The margin screen shows which older models stop covering their own power as difficulty climbs, so those are the first to be switched off or sold.

  • A hosting provider with client units

    Every machine is tagged with the client who owns it. Each client signs in to see their own units, the kilowatt-hours billed for the month at that site’s hosting rate and the payouts the pool credited against them.

  • A container site that curtails on price

    A container site drops load when the grid pays more for that power than the machines earn. One ask adds a curtailment log against the site, so the crew can set the fleet’s lost hours beside the month’s payouts and the credit the utility program paid.

Good to know

Before you build

  • Netiva doesn’t mine or hold coins

    The app records what your machines and pools already did. It doesn’t run mining software, flash firmware, hold a wallet or move a payout, and no figure on a screen is investment advice. Ask your own advisers how mined coins are treated where you operate.

  • Your pool decides what you can read

    Readings go only as deep as your pool’s API allows: some return hashrate and payouts per worker, others only an account total, and rate limits cap how often you can ask. Create that token with read permission only, never one that can change a payout address or move a balance.

  • Machine telemetry needs a way out

    Board temperatures and fan speeds sit on the local network, which a published web app can’t reach. To land here they have to come from a monitoring service with an API you can call, or be typed in during a walk.

  • Power math is an estimate until the meter agrees

    Kilowatt-hours worked out from rated watts and running hours won’t match the utility meter, because cooling, losses and idle draw never show up in a machine’s rating. Keep the meter reading in the app and reconcile it each month.

Compliance note

Netiva builds the web app that records your operation. It doesn’t mine, run miner firmware, hold or move coins, sell hashrate or give investment advice, and payout values use the price source you choose. Mining is its own regulated business: power contracts, noise and zoning limits, energy reporting and the tax treatment of mined coins differ by jurisdiction, and hosting other people’s machines adds contract duties. Get local legal and accounting review.

FAQ

Questions about building a crypto mining dashboard

Can a cryptocurrency mining app control my miners or change their firmware?

No. Netiva builds a web app that runs in the browser, so it records and reports on the operation rather than reaching into machines. It doesn’t mine, push settings, flash firmware or move a payout. Control stays in your miner firmware or fleet tool, while the app holds the register, the daily readings, the power math and the repair history around it.

Where do hashrate and payout figures come from?

From your pool. Apps built with Netiva can call any REST API with the key stored securely, so the app pulls each worker’s hashrate, rejected share rate and payouts on a schedule and files them against the matching machine. Pool-side hashrate is estimated from submitted shares, so it drifts through the day and rarely matches the number on the miner exactly. Where a pool offers no API, readings get typed in at the end of a shift.

How does the app work out what one machine costs to run?

You give each site a rate per kilowatt-hour and each machine its rated wattage. The app multiplies watts by the hours that unit was hashing, divides by 1,000 for kilowatt-hours and prices the result at the site rate. It can also show efficiency in joules per terahash, which is rated watts divided by rated terahashes per second. Keep the meter reading in the app and reconcile monthly.

Why did revenue per machine fall when nothing changed at the site?

Usually difficulty or price, not your machines. Bitcoin retargets its mining difficulty every 2,016 blocks, roughly every two weeks, and as network hashrate grows the same machine earns a smaller share of each block reward. Payout value moves with the coin price as well. Because each daily reading keeps hashrate, payout in coin and payout value side by side, you can see which of the two moved.

Can hosting clients sign in and see only their own machines?

Yes. End users can sign in to an app built with Netiva, and each one sees only their own records. A client opening the statement page gets the machines tagged to them, their kilowatt-hours for the month at the hosting rate you set for that site and the payouts credited against those units. What that statement shows is your call: describe it to the agent and adjust it in the preview. The hosting contract itself stays outside the app.

Can I build a blockchain mining app for coins other than bitcoin?

Yes. The collections are yours to shape, so a GPU rig can carry the fields its algorithm needs — cards per rig, memory clocks, the coin mined and the pool it points at. What changes is the data source: pools expose different endpoints and different payout schemes, such as pay-per-share, full pay-per-share or pay-per-last-N-shares, so map your fields to the response your pool returns.

Keep exploring
All ideas
Compare

How Netiva compares

All comparisons

Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.

Build your crypto mining dashboard today

Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.

Start building free Browse more ideas