Skip to content

A control panel only an SRE could love, turned into a few clear steps.

In production since 2024. $4.5M in revenue, verifiable on-chain.

Details

Role
Design Engineer
Timeline
2024–present

Overview

NodeOps Console is a Node-as-a-Service platform. Protocols and enterprises run blockchain nodes on it without touching a server. I have designed it since 2024. Mostly: how you deploy a node, and how you can tell it is alive.

Every chain, every node type, one surface.

What it is

Validators, RPC endpoints, full nodes, across chains. You never see the servers they run on.

What is live, before you have spent anything.

The problem

Running a node yourself means provisioning, upgrades, failover, and a pager that goes off at 3am. The Console was supposed to make all of that someone else’s job.

It shipped. Then it told us where it broke. The same four complaints, over and over.

  • You could not see what was there.

    Nodes sat behind navigation. How many existed, which were live, which ones people were actually buying: you had to dig for all of it.

  • The buy was a black box.

    Between deciding to run a node and actually having one, nothing told you where you were.

  • Chains were a guessing game.

    Which chain is this on? What do I need in my wallet? Both got answered at checkout, or never.

  • After purchase, silence.

    They bought a node. Then nothing told them what it was or whether it was running.

That last one is the whole problem in one sentence. They had paid for infrastructure and had no evidence it existed.

The system

Every chain times every node type is a lot of screens to draw. So I drew one. The chain and the node type are values passed into it, not reasons for a new design.

Adding a new chain is data, not a new interface.

One deploy flow. The chain is a value.
A new chain is a config entry.

The work

Pick a chain, pick a node type, deploy. Everything after that is the Console’s job, and it says so on screen the whole time.

The inventory moved to the front. You see what exists and what is running before you have spent anything, which is the order those questions actually occur to people.

Licenses became credits. A license meant getting the right token into the right wallet before you understood what you were buying, so the first thing the product asked of you was homework. Credits let you start. Payments engineering had to be rebuilt underneath to make that work.

Chain and funding answered up front, not at checkout.
Live in a few steps.
You can see it is alive.
Scale up without touching a server.

Before and after

Oct 2024

Now

You could not tell what was on the platform. Now it is the first thing you see.

Oct 2024

Now

A license and a funded wallet, replaced by credits.

Oct 2024

Now

“Is my node running” went from unanswerable to the default view.

Outcome

The Console has done $4.5M. NodeOps publishes its revenue on-chain, so that is a number you can go and check rather than one I am asking you to believe. It is cumulative, and most of it landed during the 2024–25 node-sale boom, when the market was doing a lot of the work. The redesign owns the flow and the purchase model. It does not own the market.

Support tickets dropped too. We put the answers in the product: what a node is, how to buy one, how to keep it running, with video where reading was not enough. An AI help layer shipped at the same time, so I cannot cleanly claim that drop for the interface.

$4.5M

Console revenue, verifiable on-chain

Cumulative, and mostly earned during the 2024–25 node-sale boom.