Run a Node

This guide walks you through setting up a complete Ogmara node — from a bare server to a fully-featured deployment with media storage, push notifications, and a web frontend. Each step builds on the previous one, but you only need to complete Server Prep, Install, and Configuration to have a working node on the network.

Full Stack Overview

A complete Ogmara node deployment consists of five components. The L2 node is the only required piece — everything else adds capabilities.

Full Ogmara Node Stack:

  1. L2 Node (core)         — stores messages, connects to network
  2. IPFS (media)           — image/video uploads and serving
  3. Push Gateway (notif.)  — mobile push notifications
  4. Web Frontend (access)  — serve the web app to users
  5. Reverse Proxy (prod.)  — SSL, domain name, routing

Server Prep + Install + Configuration give you a working node.
Each additional component adds features.

You can add components incrementally. Start with just the L2 node, verify it works, then add IPFS, push notifications, and the web frontend when you are ready.

Get on the network

🧱

1. Server Prep

Requirements, ports, dependencies, system user, swap, and firewall — everything that must be in place before installing the node.

📡

2. Install — Docker

Pull the ogmara/ogmara:l2-node-latest image, bind-mount the config and data dirs, and run as your host user. The recommended path.

🔧

2. Install — Source

Build the binary from the l2-node repo with cargo build --release and install a systemd unit. Use this if you can't or don't want to run Docker.

📝

Configuration

Fill in the four required blocks of ogmara.toml (Klever endpoints, contract address, public URL), opt into production features, and safely switch between testnet and mainnet.

✅