Licence & updates

What you bought, what it covers, and how the machine you are on is registered.

Your account

Sign up at nemonix.ai/signup with the account code from your mail. From the dashboard you can see your licences, the machines they are on, and your invoices.

Activating a machine

The installer asks for your account and licence key once and activates the machine. Later you can do it yourself, without the interface:

nemocode license activate     # reads email, password and licence key, one per line on stdin

The licence is bound to the machine, not to a folder or a project. Nemocode recognises the machine by an identifier derived from the system; the identifier itself is not stored.

Machines, moving, logging out

A licence is bound to the machines you activate it on. How many depends on the tier. If all places are taken, the way to use it on the machine in front of you is to move the licence there — no new key needed:

nemocode license move         # reads email and password, one per line on stdin

With an online licence moving is self-service; an offline licence goes to us for a decision.

When you stop using a machine, log out:

nemocode logout               # or: /licence, then l

That deletes the local licence and frees the machine's place on the server at once, without a support ticket. Freeing a place by yourself works once every 30 days per licence; a second request within that time is filed for us to decide. If the licence server cannot be reached at that moment, the local licence is deleted anyway, but nothing is freed on the server: sign in again with nemocode license relogin and log out once more when you are online, or write to us. Nemocode stops working on that machine until you come back:

nemocode license relogin      # same machine again, no new key; email and password on stdin

The licence page

/licence (or l on the Status tab of /config) shows the state of this installation: status, tier, the date updates are included until, this machine and the licence it is bound to, and the licence server. r checks with the server now, l logs out (press twice to confirm) and s signs in again with your email and password.

The update window

You own the version you bought, permanently. Newer versions are included for twelve months. After that Nemocode keeps working exactly as it is; to move to a newer version you extend the window.

The download checks this for you: if a release is outside your window, it tells you instead of failing.

Updating

nemocode update            # install the newest release you are entitled to
nemocode update --check    # only report
nemocode update --force    # reinstall even if already current

Inside Nemocode, /update does the same and asks before replacing anything. It fetches the build for your platform, verifies it against a checksum published next to it, and replaces the programs. If the checksum does not match, it refuses. Your projects, settings and memory are untouched. If a release lies outside your update window, it tells you so instead of failing.

Export and health

nemocode export backup.json   # every project's settings, sessions list and memory as JSON
nemocode doctor               # prerequisites, provider credentials, server health

Without a file name nemocode export writes to the terminal. In the interface: /export and /doctor. The export is a readable snapshot of what Nemocode knows about your projects — keep it somewhere you trust.

Server and logs

nemocode server status|start|stop|restart
nemocode logs [server|tui] [-f]     # last lines, or follow
nemocode service install            # start the server at login (launchd / systemd)

Nemocode runs a small local server; nemocode starts it when needed. The service option keeps it running across reboots, which scheduled jobs need.

Release mail

When a new version ships you get one mail: the version, what changed in it, and the one command to update. It goes to everyone with an active licence who has used Nemocode recently, and it is the only mail we send about releases.

Teams

A team licence gives you seats under one company workspace. You invite people by mail; each redeems their own seat and gets their own account. You can see who holds which seat and take one back when someone leaves.

Getting help

Write to [email protected]. If it is about a specific run, the version (nemocode --version), the output of nemocode doctor and what you saw is usually enough — see nemocode logs above.