A proprietary EULA states: "This license is granted on a per-seat basis." What does this mean for a team of 12 developers?
Per-seat licensing means each individual user requires their own license. For 12 developers: 12 seats = 12 licenses needed. Common variations:
Named user — license tied to specific named individuals (non-transferable within a billing period)
Concurrent user — only N users can be logged in simultaneously, regardless of total user count
Device/node — licensed per machine, not per person
Exceeding seat count is a license violation, even if "nobody is actually checking." Audits do happen, and penalties can include back-payment plus fines.
2 / 5
An EULA contains the clause: "Licensee shall not use the Software to perform benchmark tests or publish the results of any benchmark tests." What is this clause called and why does it exist?
Benchmark restriction clauses prohibit publishing performance test results. Vendors include them because:
Performance benchmarks could reveal weaknesses compared to competitors
Benchmarks run on non-production configurations might not represent real-world performance fairly
They prevent "unfair" comparisons in competitor marketing
These clauses are controversial — many security researchers and developers consider them anti-competitive. Notable examples: Oracle, Microsoft SQL Server, and some VMware EULAs historically contained these. When evaluating enterprise software, check for benchmark clauses before publishing internal performance tests.
3 / 5
An EULA states: "Licensee may not reverse engineer, decompile, or disassemble the Software." Under which circumstance might this clause be legally unenforceable in the EU?
EU Directive 2009/24/EC (the Software Directive) preserves the right to decompile software for interoperability — even if the EULA says otherwise. Article 6 allows decompilation when: the information is necessary to achieve interoperability with independently created software, the information is not already available, and the decompilation is limited to the parts necessary. This is why anti-reverse-engineering EULA clauses are more enforceable in the US (where DMCA governs) than in the EU. In the US, courts have sometimes upheld these clauses; in the EU, the statutory right generally prevails.
4 / 5
A SaaS EULA states: "Vendor reserves the right to modify or discontinue the Service with 30 days' notice." What risk does this create for enterprise customers?
Data portability — enterprise migrations can take months; 30 days is rarely enough
No guaranteed refund — the clause does not imply refunds; check the subscription/payment terms separately
Applies regardless of tier — the clause says "the Service," not "free tier"
When reviewing SaaS contracts, negotiate for: longer notice periods (90-180 days minimum for enterprise), explicit data export provisions before termination, and SLA credits or refunds if service is discontinued. The EULA is the floor, not the ceiling — most vendors will negotiate these terms.
5 / 5
A vendor offers software under both a commercial license and the AGPL-3.0. Under the AGPL version, your company built a SaaS product. What obligation does this create?
AGPL-3.0 (Affero GPL) extends the copyleft requirement to network use. Under regular GPL, if you do not distribute the software, you have no obligation to share source. Under AGPL: if users interact with the software over a network (i.e., your SaaS product), you must make the complete corresponding source code available under AGPL. This is exactly why vendors offer AGPL + commercial license dual-licensing: companies that don't want to open-source their SaaS must buy the commercial license. This is the MongoDB, Elastic, and Grafana dual-licensing model.