Reference
Editions and limits reference
What Lite, Pro and Enterprise include, what counts against each limit, what happens at a limit, the per-company limits on automatic Lite codes, and what happens at expiry, revocation and the end of the activation window.
Covers YuviRed 1.0 for Windows. One installer serves every edition; the license decides the edition. Edition terms below are the owner-approved terms recorded in the documentation facts sheet; the limits and behaviors are checked against the server's code.
The three editions
| Lite | Pro | Enterprise | |
|---|---|---|---|
| Price | Free | US$1,500 per year | Custom |
| Expiry | None: "YuviRed Lite is free and never expires." | Has an end date; no grace after it | Has an end date; terms as agreed |
| Computers (endpoints) | 10, plus the server itself | 50, plus the server itself | As stated in the license |
| AI agents under AMS | 5 | 50 | As stated in the license |
| How you get it | Request an activation code on https://yuvired.com with a verified work email address (or a license file) | Request at https://yuvired.com/request; YuviRed approves it, you pay, then the license is issued | Contact YuviRed |
| Trial | Not applicable | No trial | As agreed |
| Renewal | Not needed | Manual, at https://yuvired.com/request | Manual |
| Support | Email support@yuvired.com, reasonable efforts, no response-time promise | Same | As agreed |
How the server enforces the plan: a plan license is a signed license whose tier names the plan. The server refuses, at activation and again at every check, a Lite license that allows more than 10 computers or 5 AI agents or that carries an expiry date, and a Pro or Enterprise license that has no expiry date. A license must be bound to one server (its installation ID), and must allow at least one computer and state an AI agent limit. A database edit cannot widen a plan.
What counts against each limit
Computers (the endpoint limit)
- A computer counts when it is enrolled and its lifecycle is
activeorquarantined. - The server's own agent does not count. On Lite at most one endpoint, the one enrolled with the server's own token, is exempt. If the server is listed under Endpoints it does not use a computer seat. A Lite server therefore monitors 10 other computers plus itself.
- A Windows Subsystem for Linux (WSL) distribution that the server has linked to its host computer shares the host's seat and does not count again (the host must be active). A virtual machine or a container with its own agent counts as its own computer, even when linked. An unlinked inner collector, or one whose host is retired or deleted, also counts.
- A decommissioned or archived endpoint does not count, and it may not report either. Removing an endpoint (Endpoints page, Remove endpoint) is what frees a seat, and it deletes that computer's history. The console has no separate Decommission control.
AI agents (the AMS limit)
- An AI agent counts only when it holds a seat: it must be known to be running, meaning a running process or a network connection was seen. An agent known only from a configuration or key file is unseated and is not counted.
- An agent detected beyond the limit is marked over_limit: it stays visible with its evidence and does not count.
- The correlation job (setting Agent Activity Tracking) is the only thing that assigns seats. Turning it off stops new agents from being linked.
Where you see the numbers
- Configuration, License panel: Computers used and AI agents used, each "N / limit". A counter turns red above the limit.
- Agent Deployment, Add Computer panel: "Computers: N of 10" and "AI agents: N of 5" (limits follow the license), with the note "If the server itself is listed under Endpoints, it does not use a computer seat."
- Active license limits are read from the license in force; on a Lite server with no license yet (inside the 7-day window) the compiled Lite limits apply. While the server is locked the counters are not shown.
What happens at a limit
The limit is enforced when a NEW computer or AI agent tries to join. Nothing already enrolled is switched off.
| Situation | What happens | What you can do |
|---|---|---|
| Computer limit reached (for example 10 of 10 on Lite) | The new computer is refused at enrolment with HTTP 403 and the plain message license seat limit reached. Add Computer shows "Every computer seat is in use. A new computer is refused until one is free. To free one, open Endpoints and remove a computer you no longer use. Removing it deletes that computer's history." A download that would exceed the free seats is refused: "Only N computer seats are free." | Remove a computer you no longer use, or move to Pro. |
| Computers already enrolled | Keep reporting. Nothing is stopped. | |
| AI agent limit reached (for example 5 of 5 on Lite) | A newly detected AI agent is marked over_limit: visible with evidence, not counted, not seated. | An archived agent does not count; whether the console lets you archive an agent is covered in ams.md (not verified here). Or move to Pro. |
| Server locked (not activated, expired, revoked, changed) | New computers are refused (license activation required, license expired, license revoked, license server changed). The Add Computer panel shows 0 free seats. Computers already enrolled keep reporting. | See statuses-and-errors.md section 2. |
| Lite license that is not valid on this server | New computers refused: "This license is not valid on this server, so new computers are refused." The console stays open. | Activate a license for this server. |
| A server that held a Pro or Enterprise license | Does not take a free Lite license: "this server has held a Pro or Enterprise license, so it does not take a free Lite license. Contact YuviRed to renew the paid license". | Renew the paid license. |
Enrolment checks run under a lock, so two computers enrolling at the same moment cannot both take the last seat.
The activation window (a new server)
- A new server gets 7 days from its first start in which the console works with the Lite limits (10 computers, 5 AI agents). A banner shows the days left.
- After the 7 days with no activation, the console stops serving (HTTP 402
license_activation_required). Computers already enrolled keep reporting, and the software falls to monitoring only: the browser extension is told to only observe, no new blocking action reaches a computer, and blocks applied earlier stay until they are rolled back. New computers are refused (except the server's own agent). - Ways to activate: an activation code (valid 7 days from issue, activates one server, usable once) typed into the license screen, or a license file for a server without internet access, made at https://activate.yuvired.com/license-file from the code and the server's installation ID.
- A fresh database starts the 7 days again (the first start is recorded in the database), so a purge reinstall counts as a new server with a new installation ID. A server that was activated once never gets the window again on the same database. The server's own clock decides; a clock set back extends the days left.
- Pro and Enterprise licenses are issued by YuviRed after approval (and, for Pro, payment). A Pro or Enterprise code made by YuviRed is activated the same way.
Per-company limits on automatic Lite codes
YuviRed's activation service, not your server, applies these when someone at a company asks for an automatic Lite code on https://yuvired.com. The server only shows the service's answer.
| Limit | Value | When exceeded |
|---|---|---|
| Servers per company | 2 Lite servers | server_allowance_used: "Your company already has 2 YuviRed Lite servers. To add another server, contact YuviRed support and tell us why you need it." Activating the same server again (same installation ID) does not use a second slot. |
| Verified people per company | 2 people | email_allowance_used: "Two people at your company already use YuviRed Lite. To add another person, tell us why you need it and the YuviRed team will reply by email." |
| Codes per day per company | 3 | daily_limit_reached: "Your company has reached today's limit for YuviRed Lite downloads. Tell us what you need and the YuviRed team will reply by email." |
| Free email addresses | Not accepted | free_email_domain: "Use your work email address..." If the business has no work address, contact support. |
Other fixed numbers: an activation code is valid at most 7 days and works for one server once; a website verification code lasts 30 minutes and allows 5 attempts; a company's codes are counted by the email domain. Rate limits (service defaults): 3 website requests per email address per hour, 20 per network address per hour, and overall ceilings ("Try again in an hour"). The three limits above are the activation service's defaults (its settings ACTIVATION_MAX_SERVERS_PER_COMPANY, ACTIVATION_MAX_EMAILS_PER_COMPANY and ACTIVATION_MAX_AUTOMATIC_PER_DOMAIN_PER_DAY); YuviRed can set them differently, including to zero, in which case the refusal reads "To add a YuviRed Lite server for your company, contact YuviRed support and tell us why you need it." A refusal always offers a contact route. Per-company limits apply to automatic Lite codes only; Pro and Enterprise licenses are issued by YuviRed by hand, and a server activated with a code YuviRed made by hand also counts as one of the company's servers.
At expiry
- Lite never expires. A Lite license cannot carry an expiry date, and the server refuses one that does.
- Pro and Enterprise have an end date and no grace after it. Banners appear 30, 14 and 7 days before: "Your YuviRed Pro license ends in N days (date). When it ends, the console is unavailable until a new license is activated. Enrolled computers keep reporting, and YuviRed only monitors until then. To renew, email support@yuvired.com." The plan state shows Ends soon.
- On the end date the server locks: HTTP 402
license_expired, the license screen opens, enrolled computers keep reporting, and monitoring only applies (extension observes, no new blocks, earlier blocks stay). New computers are refused ("license expired"). - To unlock: activate a new license (renew at https://yuvired.com/request). The renewal is manual; nothing renews itself.
- The server's own clock is trusted: moving it back extends the license, moving it forward ends it early.
At revocation
- Lite: a local administrator cannot revoke it (the server answers HTTP 409 "the free YuviRed Lite allowance cannot be revoked"), and the console shows no revoke button on a YuviRed server (the Revoke Active License button belongs to the Docker appliance edition's panel). Only YuviRed can revoke a plan license, in its reply to the daily check-in.
- When YuviRed revokes (the reply names this server's exact serial): the console locks with
license_revoked: "YuviRed revoked the license for this server. The console is unavailable until a new license is activated. Enrolled computers keep reporting, and YuviRed only monitors until then." If you think it is a mistake, email support@yuvired.com. A revoked license can never be activated again. - A server that cannot check in (for example no internet) is never revoked remotely, and a revocation or a "newer version" notice can take up to about 25 hours to appear after YuviRed sets it.
- The daily check-in: once every 24 hours an activated server sends six facts: format, installation ID, version, serial, computer count and AI agent count. It never sends computer names, user names, endpoint names, addresses or prompts. A failed check-in changes no limit and locks nothing. The last attempt and last success are shown on the license panel (Last check-in).
- A newer version named in the reply shows as a banner. Nothing installs itself.
When the server's hardware changes
A restore onto new hardware, a copied disk, a motherboard swap or a hypervisor change that alters the virtual firmware identity gives the server a new installation ID. Until a license bound to the new ID is activated the console is locked (license_server_changed) and the state is Server changed. Moving back does not undo it. Email support@yuvired.com with the installation ID. A boot that cannot read the firmware once can look like a change and lock the server the same way.
Things these limits do not do
- No limit stops a computer that is already enrolled from reporting, except that a decommissioned or archived computer is refused.
- The console is the only thing a lock closes; detection data keeps arriving.
- There is no trial of Pro and no grace period after a Pro license ends.
- Per-company limits cannot be seen or changed from the console. They live in YuviRed's activation service.