VNetArmor Editions and Licensing¶
VNetArmor has three public product editions: Community, Standard and Enterprise. Lab is a separate, time-limited evaluation edition. Developer and historical editions are retained for internal use or backward compatibility.
Edition capabilities¶
The following values are edition-level capability ceilings. Individual SKUs or licences may impose lower limits or disable otherwise permitted modules.
| Capability | Community | Standard | Enterprise |
|---|---|---|---|
| Core and Managerd | Yes | Yes | Yes |
| Logging, TLS, WAF, rate limiting, routes and L4 ACL | Yes | Yes | Yes |
| GEO filtering entitlement | No | Yes | Yes |
| Analytics entitlement | No | Yes | Yes |
| SIEM export entitlement | No | No | Yes |
| Adaptive AI entitlement | No | No | Yes |
| Maximum routes | 10 | 250 | 5,000 |
| Maximum rate-limit rules | 10 | 250 | 5,000 |
| Maximum GEO rules | 0 | 100 | 5,000 |
| Maximum backends | 8 | 128 | 5,000 |
| Maximum WAF policies | 10 | 100 | 5,000 |
An entitlement indicates licensing eligibility, not necessarily the availability of a corresponding feature in every released software version. Check the applicable release documentation before planning a deployment.
GEO filtering also requires an appropriate GEO data source. Third-party GEO database licensing is separate from VNetArmor licensing.
Community Edition¶
Community is free and uses a non-expiring licence term. An authenticated customer with an organisation can request a Community licence through the Portal.
The Portal returns an existing active Community licence for the same organisation and SKU when one is available, rather than issuing another licence.
Community licences are signed and use the normal VNetArmor activation model. A non-expiring term does not remove activation, entitlement or licence-status requirements.
Community is a separate product edition, not a Lab trial. Community licences are not converted in place to Standard or Enterprise.
Lab evaluation¶
Lab is an internal, time-limited evaluation edition, separate from Community. The tested Lab SKU has a 40-day licence term.
The paid-order licence creation path checks for a previously issued trial for the registered email within the customer organisation.
A move from Lab evaluation to Standard or Enterprise is a product-policy objective. An automated self-service edition-conversion workflow has not been verified. Contact VNetArmor for the applicable commercial licensing process.
Standard and Enterprise¶
Standard and Enterprise licences are issued against commercial order items. The licence is signed at issuance; subsequent activation binds it to a deployment fingerprint.
Licence duration follows the purchased SKU. The tested Standard and Enterprise SKUs use annual terms.
Current public Enterprise host and container SKUs use per-node allocation. Historical Enterprise licences may retain pooled allocation where applicable for backward compatibility.
Edition and artifact compatibility¶
Edition-tagged artifacts require an exact match between the artifact, SKU and licence editions. Enterprise does not automatically inherit Standard or Community artifact entitlements.
Historical artifacts without edition tags continue to rely on explicit SKU entitlements.
Software-version upgrades, commercial renewals and changes of product edition are different operations. Access to an artifact does not itself authorise a change of edition.
Runtime enforcement¶
The Portal issues signed licences containing edition, module and policy-limit information. Runtime enforcement depends on the installed Core and Managerd versions and their supported licensing implementation.
Operators should verify activation, licence status and effective capabilities against the installed release rather than assuming that every Portal entitlement is enforced identically by every historical runtime version.