What is a node?
A node is the software you run to join the Morpheum network: it synchronizes state, participates in peer-to-peer networking, and—depending on role—may take part in consensus or serve public APIs. You pick a role when you first set up the machine; the role determines what the node is allowed to do, how it should be exposed on the network, and how much history it keeps. This section is for operators and integrators who need to deploy and run nodes, not for low-level implementation details.Choosing a role
Validators execute transactions and participate in consensus. All other roles follow the chain by applying committed updates produced elsewhere—they do not replace a validator for safety-critical execution.
Public APIs (RPC, WebSocket, JSON-RPC, agent portals) belong on Sentry, Full, Archive, or AgentPortal nodes as your policy allows—not on validators.
Where to go next
DIY stack setup
Self-build, colocation, OS baseline, and networking before you deploy by role.
Cloud
VPCs, instance classes, storage, and security patterns for cloud deployments.
Command-line interface
Initialize a data directory, run the node, snapshots, genesis helpers, and agent-related commands.
Deploy a validator
Keys, private peering, and running a consensus node safely.
Deploy a full node
Default-style node for operators and indexers.
Deploy a sentry
Public gateway in front of validators.
Deploy an archive node
Long retention and historical queries.
Deploy an agent portal
AI- and agent-optimized deployment.