NodePilot

Platform

Every fleet NodePilot runs. Open one to see it exactly as its owner does.

Fleets

Nodes

Start Node Installation

1 · Name2 · Machine3 · Install

Let's name your node. This is how it appears in your dashboard.

Node name

Letters, numbers, spaces and dashes.

What is this node's role?

Sentry

A p2p shield in front of a validator, or a plain full node. Holds no keys.

Validator

Signs blocks and holds your signing key. Built with the most restrictive guard, never auto-updated, and moved last in a fleet rollout.

RPC

Serves RPC traffic. Holds no keys.

How should NodePilot run this node?

Managed

NodePilot installs and runs Polygon's official bor + heimdall builds and keeps them healthy. If this box already has Polygon chain data, it's reused — no multi-TB re-download. (Start fresh anytime via Re-sync from snapshot.)

Monitor my existing node

You already run bor/heimdall. NodePilot only monitors it — it never installs, changes, or wipes anything.

What kind of machine will run this node?

Dedicated machine

This server runs only this node. Standard Polygon ports (8545, 26657, 30303…) are used.

Shared machine

This server runs other things too. NodePilot scans for free ports and configures the node to avoid conflicts.

Provisioning status

Transactions (24h)

Category mix — last hour

Category	Count	Share

Machine activity

Range

Uptime vs SLA

Block propagation p95 (s)

CPU %

Memory %

Disk I/O (MB/s)

read write

Network (MB/s)

in out

RPC latency p95 (ms)

Blocks behind network

Range Chart

Transactions

Categories & trend vs previous window

Category	Count	POL moved	Trend

Top tokens (drivers)

Token	Transfers	Volume	Trend

Most-called contracts (activity drivers)

#	Name	Contract	Calls

Peer count (24h)

bor heimdall

Peers (live detail)

bor: no per-peer bandwidth

	Client	Peer	IP	Ver	Dir	Recv B/s	Send B/s	Connected	State

Window

Incident timeline

Opened	Incident	Detail	Duration	Resolution

Remediation log healing runs on the node's agent

Time	Rule	Action	Target	Mode	Result	Detail

Node tuning

Peer connections

Saved versions

System

Services

Issues & Troubleshooting click to expand steps

All nodes

System Administration

You are the system owner (Sys Admin). These are fleet-wide settings — independent of any node, and separate from a node's own admin role (which is set per node under Node access).

Bor releases

Only vetted builds can be deployed. The system default applies to nodes that have not chosen their own target — each owner picks theirs under Manage node, so promoting here never moves another customer's nodes.

Vet a private build — issued to validators ahead of the public release

? ? ? ? ? Visible only to fleets confirmed as running a validator. The agent downloads it, checks it against the published checksum, and pins the image so a later public build carrying the same number cannot replace it.

Show archived

Heimdall releases

Vet a private build — issued to validators ahead of the public release

? ? ? ? ? Visible only to fleets confirmed as validators. The agent downloads it, checks it against the published checksum, and pins the image so a later public build carrying the same number cannot replace it.

Show archived

Fork requirements

What the chain demands, recorded once. Every fleet is measured against it with whatever build it is allowed to have — so a fleet that cannot yet install a fix is still told it is required, rather than finding out at the fork.

client? ? ? ? activates? ?

Fleets & private build access

Polygon issues some builds to validators ahead of the public release. A fleet confirmed here can take those; every other fleet sees public releases only. Confirmed per fleet — it describes the operator, not any one machine.

Accounts & node owners

System-wide accounts — create/remove owners, grant Sys Admin, reset passwords (billing / security / account). Customers add their own node teammates under Manage node.

? ? Sys Admin?

Node access — Sys Admin override

Fleet-wide override of per-node roles. Customers normally manage their own node's team under Manage node → Users & access.

Agent version

You publish the agent; the fleet owner applies it. Updating someone else's node restarts software on a machine they are responsible for, and an uptime record we can stand behind has to say who chose to do that — so there is no button here that does it for them.

NodePilot

Set your password

Change password

Choose where to store node data

Manage node

Set up node

Agent update

Billing & subscription

No nodes yet

No peer data

No incidents

No remediation activity