System requirements
- SystemWindows 10 or Windows 11, 64-bit (x64).
- PermissionsInstalls per user, without administrator rights; nothing is written to system folders.
- NetworkThe client loads the app from
app.noderaip.com and keeps a heartbeat with the server, so it must be online while running.
- DisplayMinimum window 1280 × 720; verified at Windows 100% / 125% / 150% scaling.
- AccountA Nodera account (email registration). The client and the merchant workspace share one account.
Installation steps
-
Download the installer
Click the button above and save Nodera-Setup-x.y.z.exe to this computer. Download only from noderaip.com; never use an installer someone forwarded to you.
-
Verify the file
Compute the SHA-256 as described under “Verify the installer” and compare it character by character with the value shown on this page. If it differs, do not run the file.
-
Run the installer
Double-click the installer. It installs into your user folder, and a Nodera shortcut appears on the desktop and in the Start menu.
About the Windows protection prompt
The installer is not yet code-signed, so on first run Windows SmartScreen may say “Windows protected your PC”. Once the SHA-256 matches, click More info, then Run anyway. When code signing is in place this prompt goes away and this page will be updated.
-
Sign in and bind this machine
Launch the client and register or sign in with your email. After the first sign-in this computer is bound as your trusted device; the same machine can then sign in directly, but fund operations such as gathering, exchange and cash-out still require the fund password.
Verify the installer
Open PowerShell in the folder holding the installer and run the command below (replace the file name with the version you downloaded):
Get-FileHash .\Nodera-Setup-x.y.z.exe -Algorithm SHA256
The Hash column of the output must match the SHA-256 shown at the top of this page exactly (case does not matter). Any difference means the file is corrupted or has been replaced; download it again.
Why verify
The installer is currently unsigned, so Windows cannot confirm for you that it came from Nodera. The SHA-256 is written to the manifest by the release pipeline and is the one thing you can check yourself before installing.
Privacy note: the machine code and this machine's details
Nodera uses a “machine code” to identify a computer, so that terminals and activation cards can be bound to it,
terminal counts managed within quota, and risk detected. To do this the client reads the hardware attributes below.
Beyond these, the client does not read or upload anything else on your computer.
- What is read
-
The minimum hardware identifiers needed to derive the machine code:
- Windows
MachineGuid (the machine identifier in the system registry)
- Motherboard UUID
- BIOS serial number
- CPU identifier
- System disk identifier
The network adapter's MAC address is not used as the primary key of the machine code.
- Why it is read
-
After normalisation, the server derives a stable machine code (
machine_id) from these attributes.
It is used only to bind terminals to this computer, to cap the number of terminals on one machine by its
“n + n” quota, to register this computer as your trusted sign-in device, and to decide whether re-confirmation
is needed after a major hardware change. The machine code is never a security credential on its own; the
server checks it together with the installation's device key and the account binding.
- What you will see
-
The machine code shown in the client and on terminal cards is masked by default, for example
HW-82F1-****-921A; click to copy the masked code. The full underlying hardware serials are never
sent to the client; in the back office, raw BIOS, motherboard and disk serials are available only to the
security-audit role on demand and are hidden from regular support staff. Every machine-code search, unbinding
and change is written to the security log.
- What is not read
-
The client does not read your files, browsing history, contacts, clipboard or keystrokes, and collects nothing
beyond the hardware identifiers above. The heartbeat, online state and network conditions (bandwidth, latency)
sent to the server while tasks run are used only for task metering and contain no personal files. The device
key created at the first trusted sign-in is kept in Windows protected storage (DPAPI) and never leaves this computer.
- Changing or unbinding a machine
-
You can remove a trusted device in the client's settings, or ask support to handle a machine change or unbinding.
The old machine, its terminals, cards and activity log are kept and are not erased by a machine change.
FAQ
Do I have to register after installing?
Yes. Register a Nodera account with your email and sign in; after the first sign-in this computer is bound as a trusted device. You can sign in and look around without an activation card, but no terminal will go live.
How many terminals can one computer run?
One machine can bind several logical terminals within its “n + n” quota, and each terminal is activated by one activation card. The exact quota, and whether extra slots can be unlocked, is shown in the app.
How much is an activation card, and how do I pay?
Activation cards come in annual, quarterly and monthly terms, all priced in USDT. Exact prices and available payment methods are as quoted in the app; this site does not list prices.
What if I change computers or reinstall Windows?
First remove the trusted device in the old computer's client settings; if the old computer is no longer usable, contact support to handle the machine change or unbinding. Your terminals, activation cards and records stay with your account.