Skip to main content
Mission Control deploys and manages blockchain nodes from the Blockops dashboard. You choose the network, where the node runs, and how it is configured; Mission Control provisions it and reports its status and resource usage back to the dashboard.

​
Where nodes can run

Resource sizing on cloud platforms is either the Default profile, which is the minimum recommended for the node, or Custom.

​
How a deployment is configured

  1. Network: the protocol and environment (mainnet or a testnet). The list of networks Mission Control supports is on Supported networks & assets.
  2. Platform: one of the options above, with its credentials.
  3. Container: name, restart policy, and optional commands, arguments and environment variables.
  4. Network configuration: a monolithic deployment runs the whole node on the provisioned server; a distributed deployment points the node at an execution RPC endpoint and a Beacon API endpoint you supply. For Ethereum-based networks you also select execution and consensus clients, their image versions, and MEV-Boost relays.
  5. Launch: review the configuration and, optionally, enable Telescope monitoring for the node before deploying.
Once the node is running, the dashboard shows its containers and resource utilisation. Health, logs, uptime checks and alerts are covered by Monitoring & alerting.

​
Guides

Deploy a node

Step by step through the dashboard, including credential setup for each platform.

Deploy to your own servers

Connect a server you operate over an SSH tunnel and deploy to it.