> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blockops.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Mission Control

> Deploy and manage blockchain nodes across cloud providers and your own servers.

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

| Platform                    | What you provide                                                                                                                                                                    |
| :-------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Google Cloud**            | A service-account file for the project the node runs in, and a region.                                                                                                              |
| **AWS**                     | An access key ID and secret access key for the account, and a region.                                                                                                               |
| **Cherry Servers**          | A Cherry Servers API key and project ID.                                                                                                                                            |
| **Bare metal**              | A server you already operate: hostname, port, username, and a password or SSH key.                                                                                                  |
| **Your own private server** | An SSH tunnel from the server to Blockops, so no inbound access is needed. See [Deploy to your own servers](/blockchain-infrastructure/node-operations/deploy-to-your-own-servers). |

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](/overview/supported-networks).
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](/blockchain-infrastructure/monitoring-and-alerting).

## Guides

<CardGroup cols={2}>
  <Card title="Deploy a node" icon="server" href="/blockchain-infrastructure/node-operations/deploy-a-node">
    Step by step through the dashboard, including credential setup for each platform.
  </Card>

  <Card title="Deploy to your own servers" icon="network-wired" href="/blockchain-infrastructure/node-operations/deploy-to-your-own-servers">
    Connect a server you operate over an SSH tunnel and deploy to it.
  </Card>
</CardGroup>