Licensing
How NativeOps seats work — what a license covers, and what it doesn't.
A seat is one plugin activated on one machine. Licenses are sold per plugin, per seat, with updates included for the duration of the license term.
The model
- Per machine, not per user. Any user account on an activated machine can use the plugin. Two workstations need two seats.
- Floating by deactivation. Moving to a new machine is deactivate-then-activate from the dashboard — no support ticket required.
- Watermark mode is not a trial clock. An unactivated operator never expires; it cooks full-rate with a watermark. Evaluate as long as you like.
Render nodes cook headless with the same seat type — there is no separate
render license. If a machine opens the .toe, it needs a seat.
What a key looks like
NOP-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
NOP-1C285B2D-6CE6-4BC7-B8BE-ADB6A7E304DAThe NOP- prefix, then a UUID — 32 hex characters, uppercase, in the
usual 8-4-4-4-12 grouping. Case and hyphens are part of the key.
Keys are plugin-scoped: a Photon RTXPT key will not activate Matter. Every key you own is listed in the dashboard with its activation state and the machine it's bound to.
FAQ
One seat is one machine at a time. Deactivate on the desktop, activate on the laptop — it takes about a minute in the dashboard. If you switch machines daily, a second seat is the honest answer.
The operator keeps working at the last version released during your term. Renewing restores update access — nothing on your machine deactivates.
Yes — activation has an offline path built for media servers that never touch the internet. See Activation → Offline.
Planned, not live. Contact us with your institution and we'll sort something out manually in the meantime.