Your own nodes, the easy way.
Download the app, add a Linux box, pick a network. Jumpgate installs the clients and serves RPC from them.
Free and open source. Other platforms
- Download the app
- Add a box Try it
- It syncs and serves
jumpgate [1 Fleet] 2 Hosts 3 Signers 4 Gateways 5 Jobs 6 Settings ? help HOST LINK NET SYNC LAG PEERS DISK FW ▸box-a gate PulseCha… synced 0 48/72 [████│░░░] 61% warn box-b gate Ethereum synced 0 52/88 [███│░░░░] 38% ok
Running a node by hand, and with jumpgate
By hand
- Pick two clients and wire them together with a JWT secret.
- Write systemd units and get the permissions right.
- SSH in as root every time something needs a look.
- Tail logs, count peers and watch the disk while it syncs.
- Put a proxy in front, with fallbacks for when your node is down.
With jumpgate
- Pick a network and clients. Jumpgate installs and wires them.
- Hardened units, written for you, running as an unprivileged account.
- Pair once, then turn root SSH off. Every command after that is signed.
- Sync, peers, disk and live logs for every box in one view.
- One gateway that asks your node first and falls back to public endpoints.
Who it’s for
Run your own node
Stop sending every wallet call through someone else’s RPC. Add a box, pick Ethereum or PulseChain, and point your wallet at one URL that asks your node first.
Start here →Build on your own RPC
Develop against a node you control, over HTTP or WebSocket. Archive mode keeps full history for indexers and explorers.
Start here →Sell RPC access
Serve keyed, metered RPC from a process of its own, away from the key that runs your fleet, with HTTPS on a domain you own.
Start here →
Everything a node needs. None of the toil.
Nine things jumpgate does so you don’t have to.
A live table of four boxes with their network, sync state, peers and disk.
Fleet
Every box at a glance
Sync state, lag, peers, disk and the firewall grade for every box, in the app, the terminal or the CLI. A box that falls behind or goes quiet stands out, and its live logs are one click away. No logging in to each server to check on it.
Choosing PulseChain, with reth and lighthouse-pulse picked.
Setup
Pick a network. Pick clients. Done.
Choose a network and a supported execution and consensus pair. Jumpgate installs both, wires them together and starts them. You never write a config file.
On a box with 3.8 TB free, a full PulseChain node fits and an archive node does not.
Sizing
Full or archive, sized to the box
Full keeps recent state for wallets and everyday RPC; archive keeps full history for explorers and indexers. Setup checks the disk has room before anything installs, so a big node never fills a small box halfway through.
Live bars showing the share of PulseChain calls each node carried in the last minute.
Gateway
One endpoint, many nodes
Point any wallet or script at one URL per chain, over HTTP or WebSocket. The gateway sends each call to your best-scoring node and keeps public endpoints as a fallback, so a node that’s down or syncing doesn’t take your app with it. There’s no load balancer to run.
The gateway on rpc.example.org with a Let's Encrypt certificate and two API keys counting calls.
Relay
Sell RPC access on your own domain
The relay serves keyed, metered RPC as a process of its own, away from the key that controls your fleet. Issue API keys from the app, meter every call, and serve HTTPS on a domain you own with a Let’s Encrypt certificate.
A phone and a laptop reach box-b through a WireGuard tunnel.
Private access
Your boxes, from your phone
Set up a WireGuard server on one of your boxes and enroll your phone and laptop, or paste a provider’s .conf to bring your own overlay. Reach your boxes without opening them to the internet.
The controller sends signed intents; the gate on the box checks them and answers with signed receipts. Below, the gates' latest log lines.
Trust
Every command signed. Every answer too.
Pairing installs a small gate on the box. It lets through only commands signed by your controller key that its policy allows, and signs every reply. Host keys are confirmed once by fingerprint; a changed key is refused, never learned again.
The jobs inbox: a migration on box-b waits for an answer.
Durable jobs
Jobs that ask before risky steps
Long operations run on the box as fixed steps. A running step keeps going if you close the TUI or your laptop sleeps, and the box’s gate keeps a signed log of every outcome. When a step can’t choose safely, the job stops and waits for your answer.
Runs on its own
BootnodePlanned
A discovery-only peer that helps your nodes and the network find each other.
smallest boxTxpool relayPlanned
Spreads your transactions from several of your boxes via peer-to-peer gossip, with no full node.
$8 boxMempool watcherPlanned
An observe-only probe that records what’s pending.
$8 boxUptime watchPlanned
Checks your endpoints and boxes from somewhere else and alerts you when one stops answering.
$8 box, elsewherePortal nodePlanned
Shares slices of chain history and beacon data, built for small devices.
$8 box · Ethereum
Rides on your nodes
Message boardPlanned
A free, censorship-resistant, short-lived message board that runs on your PulseChain reth node. Proof of work keeps spam out, not gas fees.
On your reth node msgboard.xyz (opens a new tab)Checkpoint serverPlanned
Lets your other boxes’ beacon nodes sync in minutes from a source you control.
beside your beacon nodeExplorerPlanned
A lightweight block explorer over your own node.
beside your nodePrivate sendPlanned
Submits transactions straight to block builders instead of the public mempool.
Ethereum first
Coming soon
Small jobs for small boxes
Single-purpose modules for small boxes, or riding on the nodes you already run. None of them is in jumpgate yet; each one is planned.
Built to be checked
- Open source, MITEvery line is on GitHub.
- Signed release tagsEach release tag carries a signature.
- Checksums and provenanceA SHA-256 and a build attestation for every file. Verify a download.
- Your key stays homeThe signing key never leaves your computer. Where it lives.
- Signed commands onlyPaired boxes run nothing else. What is checked.
The apps aren’t code-signed yet, so check each download instead. Why and how.
Questions
Do I need to know Linux?
A little. You need a Debian or Ubuntu server you can reach as root over SSH. Jumpgate does the setup. What a box needs
What does it cost?
Nothing. It’s free and open source (MIT). You pay only for your own servers. Install
Which networks and clients?
Ethereum mainnet, PulseChain and PulseChain Testnet v4, each with a choice of supported clients. Set up a box
Is my key safe?
It stays on your computer, in your OS key store, 1Password or an owner-only file. Boxes only check its signatures. The controller key
Can I run it on a server?
Yes. The terminal build is one binary with the TUI and the CLI; reach the web app through an SSH tunnel. Opening the web app
Can I run a node on my Mac or PC?
Nodes run on Linux, so use a WSL2 or Lima VM and pair it like any other box. A node on your desktop
Can I run a validator?
Not yet. Jumpgate runs nodes for RPC; validators aren’t supported. Docs
Ready when you are
Free and open source. Runs on your own machines.
Other platforms & terminal builds
| Platform | File | Link |
|---|---|---|
| Desktop app | ||
| macOS, Apple Silicon | Jumpgate-macos-arm64.zip | Download |
| macOS, Intel | Jumpgate-macos-amd64.zip | Download |
| Windows, x64 | jumpgate-windows-amd64.zip | Download |
| Linux, x86-64 | jumpgate-linux-amd64.tar.gz | Download |
| Linux, arm64 | jumpgate-linux-arm64.tar.gz | Download |
Terminal (TUI + CLI): run jumpgate to open the TUI | ||
| macOS, Apple Silicon | jumpgate_darwin_arm64.tar.gz | Download |
| macOS, Intel | jumpgate_darwin_amd64.tar.gz | Download |
| Linux, x86-64 | jumpgate_linux_amd64.tar.gz | Download |
| Linux, arm64 | jumpgate_linux_arm64.tar.gz | Download |
| Windows, x64 | jumpgate_windows_amd64.zip | Download |
| Windows, arm64 | jumpgate_windows_arm64.zip | Download |
Checksums: checksums.txtHow to verify a downloadInstall notes