Skip to main content

Plans and entitlements

Concepts

Your signed license is the source of what your deployment may use. This page explains plans, add-ons, limits, and what applies today. For activation steps, see License management.

Plans​

A license names one plan:

PlanIntended for
FreeEvaluating AIControls on a self-hosted Kubernetes install. No license file needed.
TeamA single team governing its AI traffic: budgets, virtual keys, routing, sessions, and detection.
BusinessSeveral teams: adds SSO, roles, policy routing, session replay, and enforcement.
EnterpriseThe full self-managed product, including Advanced Security and Workloads, with contract-specific limits. Hosted tenants have separate deployment restrictions.

A trial is a time-limited license for evaluating a plan. It carries an expiry date and trial quotas, and a grace period follows expiry (see Grace period).

A new hosted organization starts on a 15-day Team trial. Nirmata can extend a trial on request, up to 90 days from its start.

Add-ons​

Some capabilities are sold separately on Business and are included in Enterprise:

  • Advanced Security
  • Workloads

An add-on can have its own expiry date on the license; if omitted, it follows the license's validity.

On Business, an administrator can try Advanced Security for 14 days, once per organization. See Start an add-on trial.

Limits​

A plan sets limits such as gateway identities and requests per month, seats, teams, history retention, and upstreams per provider pool. A license can override a plan's default for any limit, which is how contract values are applied. Monthly limits count in calendar months (UTC).

A paid plan's running traffic never stops because of a plan limit. A limit blocks new additions, trims history, or turns off one optional behavior, and the Admin UI says which. A dash means the plan sets no limit.

LimitFreeTeamBusinessEnterpriseAt the limit
Gateway identities5--Contract valueFree: requests are refused with 402. Today the 5 identities are a lifetime cap; only the request cap resets monthly. A monthly identity cap applies once plan-based enforcement is available. Enterprise: traffic continues and the install is flagged for billing review.
Gateway requests1,000 a month--Contract valueFree: requests are refused with 402 until the month resets. Enterprise: as for gateway identities.
Seats-50500Contract valueAdmins see a banner from 90%. Past the plan plus 10%, creating a user or approving a developer access request is refused with 402. Virtual keys and service-account credentials are still issued and mark the month for billing review. Existing people keep working.
Teams-3UnlimitedUnlimitedCreating a team past the number is refused with 402.
Raw retention-30 days365 daysContract valueAudit events, snippets, and full-capture blobs are kept for the smaller of your configured retention and the plan's.
Trend retention-180 days365 daysContract valueCost and productivity charts accept any range, show data only inside the window, and mark the earlier part as locked. Nothing is refused.
Upstreams23UnlimitedUnlimitedSaving a provider configuration that raises the number of enabled upstreams past the number is refused with 402. Upstreams you already have keep routing.
Full-capture sessions--3 per seat a monthContract valueNew sessions are recorded without full capture until the month resets. Sessions already captured keep capturing.
Workload agentsDiscovery only-Number bought with the Workloads add-onFair useEnabling enforcement on one more workload is refused with 402. Re-enabling a workload never counts, and discovery continues.
Judge and Analyst calls--Your own keyYour own keyAIControls sets no cap. Without a key they stay off, and deterministic detection continues.

A trial uses 10 identities and 10,000 requests a month unless its license sets other values. Plan limits describes what each limit counts. Entitlements API returns the values and current usage.

What applies today​

  • Plan-based enforcement is the default. Features, limits and locked controls follow the resolved plan and add-ons, as described below. An Enterprise license keeps every feature, and an unlicensed self-hosted install gets the Free plan. Installs that never selected a mode move to it on upgrade.
  • An admin can opt out to compatibility mode until v1.22.0, when it is removed along with ui.tier. Compatibility mode decides from the legacy ui.tier and proxy.mode settings, not the resolved plan, so the Team, Business and Enterprise limits for seats, teams, retention, upstreams, full-capture sessions and workload agents are not active. See Plan-based enforcement and the compatibility opt-out.
  • What still applies in compatibility mode is the Free-tier caps (5 identities for the life of the install, 1,000 requests a month), trial quotas, and a limit of 2 upstreams unless the legacy tier is Enterprise (refused with 403). An Enterprise license's monthly identity and request values still flag the install for billing review without refusing traffic.
  • The Admin UI shows the license's plan on Setup → System → License.
  • The Free tier is described in License management. Its request cap is monthly; its identity cap counts over the life of the installation.
  • Older licenses keep working. Existing Trial and Enterprise licenses need no change.
  • A license can require a newer AIControls version. If it uses a plan or limit your version doesn't know, the upload is rejected and you need to upgrade first.

What plan-based enforcement gates​

Plan-based enforcement is the default, so these gates apply unless an admin has opted out to compatibility mode, in which case nothing below changes. A feature your plan doesn't include is refused with HTTP 402 and a message naming the plan or add-on that includes it:

Plan or add-onWhat a plan without it can't do
TeamStart, view or approve sessions and session requests, create or change budget rules, create or change model routes and run routing tests, issue virtual keys
BusinessReplay a session, revoke or resume a session
Advanced Security add-on (included in Enterprise)Triage baseline alerts and incidents, delete anomaly events, manage suppressions, export the triage record, export or ticket incidents, notify a user about a finding, revoke access from a finding or incident, run the Analyst, change risk scoring, read or export workload compliance evidence
Workloads add-on (included in Enterprise)Enforce, contain or release workloads, use the kill switch, change workload access and act on access recommendations, change runtime bindings, blueprints and onboarding, set the unregistered-workload and workload-caller policies

Some things stay open on every plan:

  • Detections and alerts. Security findings, incidents, alerts and their evidence stay readable, so a threat is never hidden behind a plan.
  • Workload discovery and inventory on self-hosted installs: discovery scans and scope, and the Workloads pages' discovery and inventory reads. Workload compliance evidence is an Advanced Security surface, so it needs that add-on as well.
  • Clean-up. You can still list and revoke virtual keys, delete a budget rule or model route, and list, read and revoke your own sessions after a downgrade.

Locked features​

A feature that isn't included is locked, not removed:

  • The refusal says what unlocks it. The 402 body names the feature, the lowest plan that includes it, and the add-on if one does.
  • Existing data stays readable. Findings, incidents, alerts and the history a feature already recorded stay visible after a downgrade or an add-on expiry, and you can still list and revoke what you created.
  • Every role can see what is locked. Entitlements API reports each feature's state, with the plan or add-on it needs. In compatibility mode it reports the state of the gates that apply today.

Without Advanced Security, the behavioral baseline, attack-sequence scoring, the access Judge and automatic SIEM export and ticket creation pause. Their existing data is kept, and they resume when the add-on is active again. The access Judge falls back to the deterministic access rules, as it does when the Judge is turned off.

When a hosted subscription ends​

On Nirmata-hosted AIControls, your plan follows your subscription. A failed payment, a cancellation and a lapse each have a defined effect, and your data is kept until the end of a 30-day window.

StageWhat happens
Payment failsYour plan keeps working. The owner is emailed a link to the account page to update the payment method, and Stripe retries the payment over 14 days.
A retry succeedsThe renewed license is applied and nothing changes for your team.
Retries run out, or you cancelThe subscription ends. A cancellation at the end of the period stops the 14-day tail: the license ends on the last day you paid for.
LapseThe license expires past its grace period. The tenant becomes read-only: everyone can still sign in, view and export, but changes are refused and AI traffic through the gateway is blocked. The owner is emailed.
30 days laterFor a self-serve tenant that had a paid license (subscribed online), the tenant and its data are permanently deleted. The owner is emailed 7 days and 1 day before. Tenants on an invoiced or manual agreement, and tenants that never had a paid license, are not deleted this way.

While a tenant is read-only, requests that change anything (saving a policy, adding a user, uploading a license in the console, and personal changes such as profile, preferences, credentials, connections, and connecting a datasource, identity provider or GitHub account) return a "subscription ended" error, and AI requests return the same expired-license error as before. Viewing dashboards, your own activity and the audit log, exports, and revoking your own sessions and access tokens keep working.

The admin MCP server follows the same rule: its read tools keep working, and tools that change state or run paid generation (aicontrols_explain_security_finding, aicontrols_explain_security_window) return a JSON-RPC error with error.code -32010. Its error.data.code is tenant_read_only, or tenant_state_unknown while the license state has not been read.

If a hosted tenant cannot read its license state at startup, changes are paused with a "retry shortly" error (HTTP 503) until the state is read. Viewing keeps working.

Subscribing again at any point in the 30 days restores full access with your data intact and cancels the deletion. A Nirmata administrator can extend the 30 days for a tenant; the extension is recorded in the billing audit.

A card dispute does not change the license while it is open. Nirmata handles the response, and an administrator decides what follows if it is lost. Refunds are never automatic: a Nirmata administrator approves each one, with a reason.

Self-hosted installs are not affected: an expired self-hosted license behaves as described in License management.

For the steps administrators and owners take, see Manage Licenses.

The config-file tier is deprecated​

Setting ui.tier in the configuration file to unlock features without a license is deprecated, and from v1.22.0 AIControls refuses to start with it set. Load a license before upgrading to v1.22.0. See Config-file tier.