At a glance
Connect Nodofi Studio to this node
In Studio, right-click a project → Send to Node…, then enter one of these addresses and the key below.
••••••••••••
Anyone with the key can send apps to this node, so keep it private. Apps themselves are public: anyone who knows a node's address and an app's UID can request it.
Apps on this node
Publishing rules
What this node will and won't host — shown to a publisher before they send or submit an app here (a "Send to Node…" dialog links to it, and requires agreeing before sending). Optional, but the clearer this is, the easier it is to reject or later remove something that doesn't fit, on stated grounds rather than a surprise. Not sure what to write? Pick a starting point below — from relaxed to extremely strict — then edit it to fit.
Pending submissions
Apps sent here by someone without this node's key — anyone can propose one, but nothing goes live until you review and approve it.
Reachability
Running from home, behind a router, with no domain? The address above only works for people on your own network unless you've set up port forwarding — and even then, it breaks if your internet provider changes your address, which most home connections do. A relay fixes this: this node connects out to it (which works through almost any router or firewall) and anyone can then reach it by its permanent ID below, no matter where this computer physically is or what its address is right now. This node's ID is cryptographic, not just a random number — it's derived from a key only this node holds, so nobody else can claim it (see Identity below).
Identity & registry
This node's ID (above) is the fingerprint of a key pair generated just for this node, kept only here — proving current possession of that key is what lets a relay refuse to let anyone else claim this node's ID. Registering with a node registry is what actually puts that proof to use: the relay asks the registry to confirm a connection claiming this ID really holds its key before letting it in, and a registry entry also carries a name people recognize instead of a bare ID. It re-announces itself every couple of minutes, which doubles as a "this node is alive" heartbeat.
Only set this if this node has a real domain or public IP that people outside your own network can actually reach — not the LAN addresses shown above. Someone browsing the registry can then connect to this node directly instead of going through the relay. Leave it blank if this node is only reachable through its relay.
Other nodes (peers)
Nodes you know. App browsers that ask this node can discover these too, so the network grows by word of mouth. One address per line, like http://192.168.1.20:8800.
Remote access
This admin page normally only opens on the computer that runs this node — reaching it any other way (a domain, a reverse proxy) is refused outright. A username and password (set up the first time this node was ever opened — see /admin/setup if you're seeing this before that) let you manage it from anywhere instead, without an SSH tunnel. It stays available once set up; the only thing to do here is rotate it for a new username and password. An authenticator app is a separate, optional step — add it once you're signed in, from here or from a fresh browser tab, so scanning its QR code is never fought through over curl. You can also turn remote access off entirely below — the account, password and authenticator setup are all kept, just unreachable from anywhere but this computer until it's turned back on.
Signed in as . Sign in remotely at with that
username and its password, plus a current code from your authenticator app.
Authenticator app:
Reachable from off this computer:
Ghost protection
(Beezifi Security)Puts /admin/login — the one page on this node reachable from the whole internet —
behind Beezifi's own rules (bot detection, IP/country blocklists, rate limits, geofencing, all configured in your Beezifi
dashboard, not here). A request Beezifi rejects gets a "ghost response" back — a fake page, a redirect, or a plain block —
with no hint a real login even exists, before this node's own rate limiting, password check or TOTP above ever run.
Nothing else on this node is affected, on or off.
Leave blank to keep the key already saved here — this page never shows it back.
Management tokens
Lets a fleet manager (like Nodofi Node Manager) reach this node's admin API remotely without signing in interactively — the same admin surface a remote session already has, nothing wider, and it stops working the instant remote access above is turned off. Each token is shown once, right after you create it — paste it into the fleet manager immediately, because this page can never show it again. Create a separate token per manager you link, so revoking one never disturbs another.
| Label | Created | Last used |
|---|
Payments (MooChedda / USDC)
Set these so publishers can price apps sold from this node. Changing the commission here only affects apps sent (or re-sent) after the change — an app already listed keeps the rate its publisher agreed to.
How this works: anyone can propose an app for this node to host without needing the key above (see Review queue) — nothing they send goes live until you approve it. If you set a fee here, they must pay it before their app is even queued for your review, straight to the payout wallet above; this node checks it's a real, settled MooChedda payment, so it actually costs someone something to flood you with junk submissions. The fee is not refunded if you reject what they sent — but fixing and resubmitting the same app doesn't cost them again, only a genuinely new submission does. 0 = free to submit (still requires your approval to go live).
App performance
Counts and timings are kept on this computer for 30 days. To also save them to your Nodofi Studio account (and see them there), open App Performance in Studio and link this node. Speed is how long this node takes to answer, not the network.
About this node
A Nodofi Node is a small, independent server for decentralised app hosting. You send an app to it from Nodofi Studio; anyone who knows this node's address and the app's UID can then request that app over Socket.IO, and their page assembles and runs it directly from this computer — no central server in between. Every node stands on its own: this dashboard is where you manage the apps it hosts, who can reach it, and how it's protected.
Nodofi Inc.
Nodofi builds decentralised infrastructure for hosting and running applications — nodes, relays and a marketplace that let anyone contribute compute and anyone else use it, without a central point of control.
© Nodofi Inc. All rights reserved.