Network guide

Stellar Full Node: Complete Guide

A practical guide to Stellar full nodes: server requirements, self-host in a few clicks with RpcNode Toolkit, manual setup, and when to use managed Full Node RPC instead.

0 environments

What is a Stellar full node?

A Stellar full node is infrastructure that syncs and verifies the Stellar ledger, then answers application queries about balances, blocks, and transactions.

This guide covers what a Stellar full node does, when to self-host versus use managed RPC, and how RpcNode fits as a Full Node RPC provider for Stellar.

Why Stellar full nodes matter

Every wallet balance, payment confirmation, and contract read ultimately depends on nodes that agree on Stellar state. Public endpoints rate-limit and flake; your product’s reliability tracks the quality of the full nodes behind your RPC URL.

Stellar in the RpcNode catalog: Stellar.

  • Native asset: native token
  • Environments:
  • API family: native JSON-RPC / HTTP APIs
  • Listed in the RpcNode network catalog

When to run your own Stellar node

Self-hosting a Stellar full node makes sense when you need custom indexing, ultra-low latency next to your app, or compliance constraints that forbid third-party RPC. For most product teams, managed Full Node RPC is faster to ship and cheaper to operate.

  • Building wallets, payments, or address watchers that need reliable Stellar reads and writes
  • Avoiding multi-terabyte disks, peer tuning, and 24/7 pager duty for chain upgrades
  • Preferring HTTPS JSON-RPC with allowlists, keys, and usage metering
  • Evaluating Stellar before dedicating hardware — start on RpcNode, or self-host with Toolkit in a few clicks

Stellar full node server requirements

Stellar full node server requirements depend on the official client. Treat the figures below as a planning baseline for NVMe-backed Full Node RPC — then verify against current project documentation before purchase.

Looking up "Stellar server requirements", "Stellar hardware requirements", or "Stellar minimum specs"? Use the checklist below as the planning baseline for a self-hosted full node.

Stellar is in the RpcNode catalog. Until you need custom indexing or on-prem constraints, prefer managed Full Node RPC when available rather than buying this class of server “just in case”.

  • CPU: 4–8+ cores as a starting point
  • RAM: 16–32 GB+
  • Disk: prefer NVMe; 500 GB–2+ TB until you measure real growth
  • Bandwidth: 1 Gbps recommended
  • OS: Ubuntu 22.04/24.04 LTS
  • Monitor tip lag and disk growth after the first month

Install a Stellar full node in a few clicks

Stellar is in the free RpcNode Toolkit catalog (mainnet, testnet, futurenet). Skip the manual binary hunt: the self-hosted panel walks Add server → Add node → the node page.

On Linux (amd64/arm64) you install the host agent once, register the server, pick Stellar and an environment, then the node page handles ports, install, snapshot when the chain supports it, sync, logs, and the public RPC endpoint.

  1. Install the host agent on the Linux server (curl one-liner from rpcnode.dev).
  2. Add server: paste IP and AGENT_API_TOKEN, Check connection, then add.
  3. Add node: network Stellar → environment (mainnet, testnet, futurenet) → that server.
  4. Open the node page — install, sync %, logs, restart, client update, fullnode RPC.

Self-host Stellar with Toolkit

How to run a Stellar full node

How to run a Stellar full node: use the network’s official node documentation for the supported client, then harden RPC exposure.

RpcNode publishes this guide so teams can compare self-host minimum specs with managed Full Node RPC when the catalog network is activated.

Stellar is in the RpcNode catalog. Until you need custom indexing or on-prem constraints, prefer managed Full Node RPC when available rather than buying this class of server “just in case”.

  1. Provision Ubuntu 24.04 LTS (or the OS your client documents) on bare metal or a dedicated VM. Create a system user such as `nodeop` — do not run the node as root.
  2. Attach NVMe sized from official docs. Mount it away from the root filesystem and give ownership to the operator user.
  3. Apply OS hygiene: unattended-upgrades or a patch cadence, fail2ban/SSH keys, and raise file-descriptor limits if the client docs require it.
  4. Install the supported Stellar client from upstream releases only.
  5. Configure a full-node (or RPC-node) profile — avoid enabling validator/signing keys on a public API host.
  6. systemd or the project’s supervised process model; open P2P; whitelist RPC.
  7. Verify tip/sync with the native status RPC and compare to a public explorer.
  • Treat official docs as source of truth for flags and ports
  • Prefer managed RpcNode RPC when you do not need custom infra

Using Stellar RPC without self-hosting

RpcNode exposes managed native JSON-RPC / HTTP APIs for Stellar. Create an endpoint in the cabinet, restrict IPs if needed, and call the same methods your stack already uses.

Catalog environments for Stellar: . Create an endpoint in the RpcNode cabinet for the environment you need, or use this guide to plan a self-hosted deployment.

Typical methods teams start with: chain tip, account/balance reads, transaction broadcast.

Self-hosting vs managed Full Node RPC

Self-hosting gives maximum control and can reduce per-request cost at huge scale, but you own upgrades, peers, disk growth, and incident response. RpcNode Toolkit cuts the install to a few clicks (agent → Add server → Add node → node page) while you still run the hardware.

Managed RpcNode Full Node RPC trades that ops burden for a stable HTTPS endpoint, usage visibility, and the same method surface your SDK already speaks. If you are comparing providers, also see RpcNode’s comparison page.

Stellar integration checklist

Use this short checklist when wiring Stellar into production.

  • Pick the correct environment () — never mix testnet keys with mainnet funds
  • Store RPC URLs and keys in secrets management; rotate on staff changes
  • Add IP allowlisting for server-side backends
  • Alert on tip lag / getHealth (or equivalent) failures
  • Load-test eth_getLogs / getProgramAccounts-style heavy calls before launch
  • Decide full vs archive needs early — RpcNode is Full Node oriented
  • Confirm Stellar server requirements (CPU/RAM/disk) before self-hosting
  • Or install with RpcNode Toolkit in a few clicks — free self-hosted panel

Stellar full node FAQ

Can I install a Stellar full node in a few clicks?

Yes. Stellar is in the free RpcNode Toolkit catalog. Install the Linux host agent, Add server, Add node (Stellar → environment → server), then finish install and sync on the node page. See rpcnode.dev/toolkit.

What is a Stellar full node?

A Stellar full node verifies and stores blockchain data for Stellar, then serves queries about blocks, accounts, and transactions. RpcNode runs Full Node RPC so apps can use that data over HTTPS.

Is RpcNode Stellar RPC available now?

Stellar is listed in the RpcNode network catalog. Check the product for current managed RPC availability for your account, or use this guide to plan self-hosting meanwhile.

Full node vs archive node for Stellar?

Full nodes verify the chain and answer tip-oriented RPC. Archive or indexed stacks keep deeper history for analytics. RpcNode focuses on managed Full Node RPC for Stellar.

Can I accept native token payments on Stellar?

RpcNode also ships crypto payment infrastructure and address watching on supported networks. When Stellar RPC is active for your account, you can combine payments with the same Full Node-backed data plane.

What are the Stellar full node server requirements?

See the “Stellar full node server requirements” section for CPU, RAM, disk, bandwidth, and OS minimum specs. If you only need HTTPS RPC, managed RpcNode Full Node endpoints avoid buying that hardware.