Use cases
Use cases
- Plan infrastructure for an operator-managed network or node service.
- Define validator operations and governance responsibilities between parties.
- Scope ongoing maintenance and support around a selected published product.
Solutions
Blockchain network operators
Assess managed network, infrastructure, and operational product options while keeping protocol choices, validator duties, access, upgrades, incident handling, and customer responsibilities explicit.
Business challenges
Business challenges
Operating a blockchain service requires more than selecting a chain. The protocol, control plane, infrastructure, and response responsibilities must be agreed.
- Choose supported network components and define ownership of validator and administrative keys.
- Plan upgrades, monitoring, backups, recovery, and incident escalation for the selected environment.
- Coordinate network operations with explorers, applications, and customer support expectations.
Relevant products
Relevant products
Review current managed-chain and infrastructure categories, then configure published products to see eligible scope.
Logical architecture
Logical architecture
Operator responsibilities span the protocol-facing network, administrative controls, and service monitoring and response.
01Network participantsValidators, peers, and protocol dependencies
02Operations control planeAccess, maintenance, deployment, and change approval
03Service interfacesRPC, explorers, and customer applications
04Observability and responseMonitoring, escalation, and agreed recovery tasks
Deployment considerations
Deployment considerations
Agree on supported protocol and version, network placement, access paths, key custody, upgrades, backup and recovery, monitoring, incident escalation, and who approves changes.
Integrations
Integrations
- Blockchain RPC endpoints and network tools included by the selected product.
- Customer application and observability systems where supported and scoped.
- Identity and change-control workflows for operator access.
Commercial engagement
Commercial engagement
Compare the available network and infrastructure products, then configure the desired scope. Any operational coverage, response target, or custom topology must be explicit in the resulting agreement.
Documentation
Documentation
Check the existing catalogue and operator guides for product-specific scope and configuration information.
Trust and responsibilities
Document operations instead of assuming them
Key custody, protocol governance, service access, incident decisions, and recovery responsibility must be stated by party. Check product documentation and contract terms for included operations; this overview makes no availability or security certification claim.
Architecture resourcesPricing and procurement
Build a scope from current listed products
Published prices and configuration estimates belong to the existing blockchain catalogue and configurator. Operator coverage, custom infrastructure, and support terms depend on the selected products and agreed scope.
Frequently asked questions
Questions for network operators
Does managed infrastructure include protocol governance?
Not automatically. Review the selected product description and agree which party controls protocol decisions, keys, upgrades, and operational changes.
Are response times or availability guarantees stated here?
No. Confirm any service levels and support commitments in the applicable product documentation and written agreement.
Define the network and operator handoffs
Bring protocol, topology, key ownership, maintenance, and incident requirements to a review.