Setup
Install the node with a cleaner setup path
Move from purchase to a healthy node without guesswork: install the runtime, activate the license, and prove the stack in a safer first mode.
Bootstrap path
The one-line command pulls a signed bundle from the portal, extracts the ZeroTrade repo, and runs the production installer on the host.
Host preparation
The installer provisions the service user, system packages, config root, runtime directories, nginx, systemd units, and the Python environment.
Activation handshake
After payment the operator inserts the issued account id and license key, then the local node performs a signed handshake against the portal.
Proof-first rollout
A clean deployment starts in demo, replay, or paper mode so the operator can verify heartbeat, uplink, replay, and Oracle readiness before anything else.
Setup Notes
The public setup guide should stay simpler than the full operator docs
Customers need a calm path, not a wall of server trivia. The public bootstrap still points to the product domain for downloads, but the installed node can live on the host name you actually control.
The portal can stay on the product domain while the installed node uses your own IP, domain, or subdomain.
Install, activate, open zerotrade, and prove the stack in replay or paper mode before adding extra complexity.
The node works fine locally. Remote browser access is a separate SSH tunnel pattern, not a requirement to get started.
The normal remote path is ssh ubuntu@example.com or ssh ubuntu@serverIP, then an SSH tunnel if you want the browser panel on your own machine.
The node can live on the same Ubuntu server as the public ZeroTrade site. The important part is keeping the node panel local-only instead of making it a public web page.
Core Commands
The short public command path
Downloads the current ZeroTrade bundle from the portal and runs the production installer.
Installs the node and pulls the default Gemma 4 E2B model so Oracle can run locally on a 16 GB class host without cloud keys.
Confirms packages, services, health heartbeat, mode posture, and recent runtime output after install.
Preflight checklist
Safe defaults out of the box
Public site traffic stays open on the operator’s chosen web surface, while protected agent and Oracle APIs remain local-only unless the operator deliberately chooses an IP allowlist during install.
That means the portal can stay reachable without exposing sensitive node control routes by accident.
The private node panel stays local on 127.0.0.1:8010 and is intended to be reached through SSH tunnel rather than public internet exposure. That means the browser URL works on your home PC after the tunnel is open, not as a public website by itself.
If you type that URL in your browser before the tunnel exists, you should expect it not to load the server panel. The browser path only becomes real once SSH is forwarding your local machine to the server.