Enterprise
What does a production blockchain deployment cost to run, after launch?
The number the launch budget rarely includes, and the reason year-two surprises happen.
The answer
Budget for four ongoing lines beyond the build itself: node operations and monitoring, the daily reconciliation close, key ceremony and rotation on a rehearsed cadence, and an on-call rota for incidents — together typically the cost most launch budgets underestimate, because they are modelled during delivery and paid for during operation.
The four ongoing costs
Node operations and monitoring — validators or full nodes, upgrade choreography, and alerting that distinguishes a lagging peer from a fork.
The daily reconciliation close — a break procedure with a named owner, run every day the system operates, not just at audit.
Key ceremony and rotation — rehearsed on a cadence, because an unrehearsed recovery procedure should be treated as absent.
On-call and incident response — a rota, an escalation path, and a post-mortem policy that produces a written record every time.
Why this is where estimates go wrong
A build budget is scoped against a delivery date and reviewed by people motivated to hit it. An operating budget is scoped against a year that has not happened yet, reviewed by nobody in particular, and inherited by whichever team is running the system when the invoice arrives. Naming the four lines above, with an owner for each, is the entire fix.
Talk to the practice
Tell us what you are trying to build and what has to be true for it to work.
Contact