Use single-tenant dedicated servers for MetalGo validators, subnet nodes, API nodes, monitoring, and recovery, with root access, public TCP reachability, and capacity your team can size and control.
Configure a stable public IP and bidirectional TCP access on default port 9651 before starting validation.
Single-tenant CPU, RAM, and storage make node responsiveness easier to measure, tune, and troubleshoot.
Reserve capacity for state growth, logs, monitoring retention, upgrades, backups, and accepted recovery windows.
Use root access for MetalGo, firewall rules, monitoring, backups, and subnet settings under your own policy.
Metal Blockchain operators must match infrastructure to the job: validation, subnet work, API traffic, monitoring, or recovery. Each role changes pressure on CPU, memory, storage, bandwidth, and public reachability, while the staking period leaves little room for identity or connectivity mistakes during active validation and planned recovery workflows.
At Melbicom, we provide single-tenant hardware, root access, regional deployment choices, and network capacity you can size around MetalGo state growth and synchronization. Isolated resources make slow state work or missed responsiveness easier to trace to compute, memory, storage, or network pressure under sustained node load and resynchronization.
Keep the boundary explicit: we support the server and network layer; your team operates MetalGo, staking, keys, firewall policy, monitoring, backups, upgrades, and subnet configuration. This model preserves control while giving validators and supporting nodes measurable capacity, clear ownership, and a practical, tested recovery path under load.
Prioritize peer reachability, public staking-port access, and validation headroom throughout the fixed staking period.
Size compute, memory, storage, and bandwidth for both Primary Network duties and the subnet workload you operate.
Plan capacity for synchronization, state growth, logging, and upgrades without assigning stake or validator responsibility.
Separate API traffic, query load, and retention needs from validation so resource pressure remains visible and controllable.
Run metrics, logs, and alerts separately so observability load stays visible without masking validator capacity pressure.
Reserve compute, storage, and bandwidth for backups, restore tests, and the recovery window your policy accepts.
Test MetalGo releases, firewall changes, and subnet settings before applying them to any validator with active stake.
Place regional capacity around peer reachability, operator access, and failure domains defined by your node plan.
