Commercial License Vocabulary

The per-seat vs. concurrent licensing choice significantly affects total cost of ownership — per-seat simplifies compliance but can be expensive for large organisations with irregular usage; concurrent is complex to manage but cost-effective for shift workers or infrequent users.

The break-even calculation: if your 100 users use the software at an average utilisation rate of 20% (20 concurrent users at peak), concurrent licensing at the same per-seat cost would be 80% cheaper. But concurrent licensing requires a license server (or vendor-managed session tracking), and organisations must monitor and manage license checkouts. Per-seat is the dominant SaaS model because it's simple: one user = one login = one subscription. Concurrent licensing is more common for expensive professional software (CAD, ERP, simulation tools) where a small number of specialists use the software intensively while others rarely need it.

Key vocabulary:
• per-seat license — a license purchased for each named individual user regardless of simultaneous usage
• concurrent user license — a license purchased for a number of simultaneous users; allows more total users than licenses
• license utilisation — the percentage of purchased licenses that are in active use at any given time

Enterprise licenses are comprehensive commercial agreements, not just a headcount upgrade — they address the procurement, compliance, security, and support requirements that large organisations impose as prerequisites for deploying software widely.

Enterprise software procurement involves more than pricing: legal must review the data processing agreement (GDPR/data residency), security must review the vendor's compliance certifications (SOC 2, ISO 27001), IT must assess SSO integration and SCIM provisioning for automated user management, finance must structure multi-year payment terms, and procurement must negotiate SLAs with penalty clauses. The "unlimited users" component is often the easiest part to negotiate. More contentious: data portability terms (can you export all your data if you leave?), IP ownership of data you generate using the tool, indemnification clauses, and audit rights. Understanding the full scope of enterprise license negotiations is critical for technical professionals involved in vendor evaluation.

Key vocabulary:
• enterprise license — a negotiated commercial agreement providing unlimited or high-volume access with enterprise-grade features and SLAs
• SSO (Single Sign-On) — authentication integration that allows users to log into the software using their existing corporate identity provider
• SCIM (System for Cross-domain Identity Management) — a protocol for automatically provisioning and deprovisioning user accounts from a corporate directory

OEM licensing is the commercial mechanism that enables software products to be built on top of other software components — without OEM rights, embedding and redistributing third-party software would breach the standard license terms.

OEM licenses have distinct commercial structures: (1) Royalty-per-unit — you pay the vendor a fee for each product instance that ships with their component (common for device-embedded software); (2) Site license — flat annual fee for unlimited embedding within your product; (3) Revenue share — you pay a percentage of revenue attributed to features powered by their component. The legal substance of an OEM license: the right to sublicense the component to your end customers, the right to include it in your installer or binary, and often the right to brand it under your product name. Without these rights, embedding the software technically breaches the "no redistribution" terms of standard EULA licenses.

Key vocabulary:
• OEM license — a license granting rights to embed and redistribute software as part of another product
• royalty-per-unit — an OEM pricing model where a fee is paid for each product shipped containing the licensed component
• sublicense — the right to pass on license rights to your customers (allowing them to use the embedded component)

The perpetual vs. subscription distinction has major business continuity implications: perpetual licenses give you a guaranteed fallback (keep using the old version), while subscriptions create vendor dependency (stop paying = lose access to everything).

Financial implications: perpetual licenses have higher upfront cost but potentially lower total cost of ownership over many years if the software remains fit for purpose. Subscriptions have lower upfront cost but accumulate into higher long-term spend. Enterprise procurement teams frequently model the "break-even year" — the point at which the subscription's cumulative cost exceeds the perpetual license cost. The risk profiles differ: with perpetual, the risk is that annual maintenance stops being worth the cost (software becomes outdated). With subscription, the risk is price increases, vendor exit from market, or "rug pull" of the product. Most enterprise software has moved to subscription (SaaS), but some categories (CAD, simulation, specialised tools) still offer perpetual models.

Key vocabulary:
• subscription license — time-limited access that requires ongoing payment; access ends when payment stops
• perpetual license — a one-time purchase granting indefinite right to use a specific version of the software
• annual support / maintenance — a recurring fee paid alongside a perpetual license to receive updates and technical support

SaaS contract renewals are high-stakes procurement events that require active management — auto-renewal traps, price increase clauses, and scope changes in terms of service can create significant unexpected costs or data loss risks.

The auto-renewal trap is the most common procurement failure: a SaaS contract automatically renews for another annual term unless cancelled 30, 60, or 90 days before renewal. Missing the cancellation window locks the company in for another year at whatever price the vendor has set. Best practice: calendar all renewal dates with a 120-day early warning, start vendor review at 90 days, negotiate at 60 days, make a decision at 30 days. Price increase terms matter: "CPI + 5%" is very different from "vendor may increase pricing at renewal at their discretion." Data portability is critical: some vendors make data export intentionally difficult once you decide not to renew — negotiating explicit data export rights (machine-readable format, within 30 days of termination) in the original contract prevents this leverage.

Key vocabulary:
• auto-renewal clause — a contract term that automatically extends the subscription unless the customer actively cancels before a deadline
• notice period — the time before renewal by which the customer must notify the vendor of non-renewal intent
• data portability — the contractual right to export your data in a usable format upon contract termination

'Pay-per-use' licensing is fundamentally different from other models. Instead of a fixed cost, users pay directly for what they consume – often based on metrics like API requests or transactions. This contrasts with 'concurrent user' licenses where you pay for the number of people actively using the software simultaneously, and 'per-seat' which is a flat fee per individual.

David's question highlights a crucial aspect of source code licenses. 'Source code access' doesn't automatically grant rights to modify and redistribute commercially. The license document must explicitly state whether such rights are included. Requesting a clarification on permitted use cases and explicit commercial redistribution terms is vital for legal compliance.

A 'volume' license typically implies pricing discounts based on the quantity of software purchased. It often correlates with the size or scale of the user base or infrastructure – frequently related to server count or number of users. This contrasts with 'per-seat' which is tied to individual users and 'enterprise' licenses, which usually refer to a specific number of users.

A 'named user' license directly correlates software usage with individual developers. This is in contrast to other models like 'concurrent user' licenses which allow multiple simultaneous users without needing separate keys for each. The key benefit of named user licensing is precise tracking and control – it's crucial for compliance and billing accuracy. Incorrect options misrepresent the core concept of associating a license with a specific individual.

'AGPLv3' stands for Affero General Public License version 3. This is a copyleft license, meaning that if you modify or redistribute the software (even commercially), you must make your changes and modifications available under the same AGPLv3 terms. This ensures that the open-source nature of the code remains preserved throughout any derivative works. Options A, C, and D misrepresent the core restrictions imposed by this type of license.

The fundamental difference lies in the payment structure. A 'perpetual' license offers permanent ownership but necessitates ongoing costs for maintenance and support. A 'subscription' license combines access to the software with these recurring fees, simplifying budgeting. Option A is a common misconception; cost isn't determined by the license type alone. Options B & D are inaccurate.