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

# Node Operators

This section helps you run and operate a Celo L2 node. If you are starting fresh, the fastest path is to [run a full node with Docker](/infra-partners/operators/run-node) — a new node bootstraps from a published snapshot (or, on Celo Sepolia, syncs from genesis), with no L1 data migration required.

## What is a Celo L2 node?

A Celo L2 node is made up of two core services, plus an optional third:

* **Rollup node** (`op-node`) — derives L2 blocks from L1 data, analogous to a consensus client.
* **Execution client** — executes those blocks and exposes the standard Ethereum JSON-RPC API.
* **Legacy L1 (optional)** — serves stateful queries for blocks and transactions from before the L2 transition.

See [Architecture](/infra-partners/operators/architecture) for how these fit together.

## Node types

* **Full node** — follows the chain and serves recent state. Starts from an empty datadir — bootstrap it from a published snapshot (or sync from genesis on Celo Sepolia), with no migrated L1 datadir required. This is the right choice for most operators.
* **Archive node** — additionally preserves all historical state, at the cost of terabytes of storage. See [Running an archive node](/infra-partners/operators/archive-node).

## Execution client

* **op-reth** — Celo's primary execution client, built on `reth`. The guides in this section use `op-reth`.
* **op-geth** — the previous execution client. It is deprecated in favor of `op-reth` and remains supported only until your network's switch date.

<Warning>
  **op-geth is being deprecated**

  Celo is switching its execution client from `op-geth` to `op-reth`. All node operators must migrate to `op-reth` by their network's switch date. See [End of Support for op-geth](/infra-partners/notices/op-geth-deprecation) for the switch dates and details, and follow the [celo-l2-node-docker-compose](https://github.com/celo-org/celo-l2-node-docker-compose) repository for release updates.
</Warning>

## Guides

* [Run a node with Docker](/infra-partners/operators/run-node) — the fastest way to get a full node syncing (also covers building from source).
* [Run an archive node](/infra-partners/operators/archive-node) — preserve access to all historical state.
* [Run a public RPC node](/infra-partners/operators/public-rpc-node) — operate a public JSON-RPC endpoint (and optionally earn rewards).
* [Monitoring & metrics](/infra-partners/operators/monitoring) — enable the Grafana/Prometheus stack and watch sync health.
* [Upgrades & maintenance](/infra-partners/operators/maintenance) — upgrade clients, restart safely, and back up your data.
* [Troubleshooting](/infra-partners/operators/troubleshooting) — fixes for common node issues.
* [Configuration reference](/infra-partners/operators/configuration) — the `.env` variables and key client flags.
* [Network Config & Assets](/infra-partners/operators/network-config) — bootnodes, container images, and downloadable artifacts.
* [Migrate an L1 node](/infra-partners/operators/migrate-node) — for operators moving existing Celo L1 data to L2 (legacy path).

## Getting help

Please reach out to our team on [Discord](https://chat.celo.org) in the [#celo-L2-support](https://discord.com/channels/600834479145353243/1286649605798367252) channel if you have any questions.