OutSystems is one of the few vendors in the wiki that publishes the rules for what happens when a customer’s use of the software exceeds, or outlasts, its licence. This article summarises four public documents: the Master Subscription Agreement (MSA), the Subscription Compliance Terms, the End-User License Agreement (EULA) used for purchases through resellers, and the Governing Law and Jurisdiction page. The Subscription Compliance Terms state that they are “incorporated by reference into the Master Subscription Agreement or the equivalent signed master agreement”, so a customer with a negotiated agreement should check whether it replaces them.[2]
Editions
Contract documents do not distinguish editions, but they distinguish contracting routes. A subscription is obtained “solely by execution or acceptance of an Order”, each Order being a discrete contract unless stated otherwise.[1] A customer buying through an authorized reseller is bound by the EULA, which makes its rights “subject to the usage limits defined in the applicable Order for the purchase of the Subscription”.[3] The EULA says its clauses bind the end user to the extent they are not incompatible with another written agreement with OutSystems, and that when a subscription is bought through a reseller and the reseller agreement is inconsistent with the EULA, the EULA prevails on the subject matter.[3] The row is Purchase through a reseller under the EULA.
Metrics
The MSA does not define the billing metrics itself. It says “Application Object” and “Users”, as used in an Order, have the meaning set out on OutSystems web pages: the Support page on Application Objects and an OutSystems 11 documentation page on End User management.[1] The practical consequence is that the counting rules are maintained outside the contract. The Application Objects page used in the catalog is dated 2026-09-06.[5] Rows: The meaning of Application Object in an Order is set by the Support page and The meaning of Users in an Order is set by an End User management page. See OutSystems Application Objects.
Counting and floors
Licence grant and restrictions
The MSA grants a limited, non-exclusive, non-transferable licence without sublicensing rights to use the Software during the Subscription Term “for the sole purpose of building Applications for Customer’s own business processes, including access by internal users and external users”. For self-managed Software, the customer may install on servers it manages and make one backup copy. The scope “remains subject at all times to the Subscription Compliance Terms”.[1] The restrictions bar modifying, translating or migrating the Software; circumventing technological measures that control access or measure use; using the Software to provide third-party training or to build or operate a competitive product; disclosing benchmark results; and deploying or operating applications in production using a non-production environment.[1] The EULA contains equivalent restrictions, including the bar on building or operating a competitive product.[3]
Customers may give agents, consultants and third-party implementation partners access to the Software solely to help develop applications for the customer’s use within the Order scope. The customer remains responsible, their use is deemed use by the customer, and no right to sublicense is granted.[1]
Scope of use and verification
The Subscription Compliance Terms state that the Software is subject to the “volume, scope, and territory of use (if any) specified in the applicable Order”.[2] For a customer using the Software in an on-premise or self-managed environment, the customer cooperates with a secure, remote usage verification “no more than once each calendar quarter”. OutSystems gives 30 days notice, the customer transfers its Usage Data to an online verification site, and OutSystems reviews the results with the customer. The terms say this approach avoids “the need for an on-site audit or access to Customer systems”, and that the process is not needed for a customer using the Software within an OutSystems Cloud hosted environment.[2] The EULA contains the same quarterly verification, with at least 30 days written notice.[3] The MSA lets OutSystems and affiliates collect and use Usage Data, which is anonymized to remove Personal Data, for statistics, troubleshooting, product improvement and compliance verification.[1] The rows are Self-managed customers cooperate with a remote usage verification once per quarter and the programme Quarterly usage verification.
Excess usage
The Subscription Compliance Terms set out a sequence when usage exceeds the licence at any time in the term, or continues after expiry.[2]
- OutSystems states a preference to “negotiate and sign a new Order” covering the unlicensed usage rather than invoice unlicensed usage and compliance fees.
- If no new Order is signed, OutSystems reserves the right to invoice the unlicensed usage at the then-current list price, from the date of first unlicensed use to the end of the then-current Subscription Term, or to the date of last use if used after termination or expiry.
- If the customer does not cure within 60 days of written notification, either by a new Order or by paying the invoice, OutSystems may add a compliance fee of five percent of the Fees due for the unlicensed usage.
- The customer agrees to issue a purchase order, if its processes require one, for all Fees due, including the compliance fee.
The EULA contains an equivalent clause for resellers: if Usage Data shows that the customer exceeded its licensed usage at any time during the term or continued after expiry, the reseller may invoice the additional usage at the then-current list price from the date of the first unlicensed use.[3] Rows: Excess usage may be invoiced at list price from the first unlicensed use and The EULA allows compliance verification once per quarter with reseller invoicing of excess use.
Renewal and termination
Term and renewal
Unless the Order says otherwise, the Subscription Term renews automatically for periods equal to the initial term, for the same configuration and quantity, at the renewal fees in the Order or, if none are agreed, those in a renewal notice sent at least 60 days before the end of the term, unless either party gives non-renewal notice at least 30 days before the end.[1] The Subscription Compliance Terms add that OutSystems customarily emails the Bill To contact about 60 calendar days before expiry, without any contractual obligation to do so, and does not suspend access or delete applications at the end of the term but allows a grace period of 30 calendar days.[2]
If the customer wants to renew but cannot complete the paperwork or purchase order by the end of the term, OutSystems may assess a reinstatement fee equal to five percent of the Fees for the Renewal Subscription Term. That fee is not counted towards the applicable subscription fees, including agreed limits on price increases or uplift caps.[2] Rows: A 60-day renewal notice and a 30-day grace period apply at the end of a term and A reinstatement fee of 5% applies if a renewal is not signed by expiry.
Payment and cancellation
All Orders are non-cancelable and, upon payment, payments are non-refundable, except as the Agreement states otherwise. Fees are due within 30 days of invoice unless the Order says otherwise, and non-payment of undisputed Fees allows OutSystems, on 30 days written notice, to suspend access until paid.[1] Either party may terminate for uncured material breach after 30 days written notice.[1]
Detachment
On termination or expiry, access ends, but the customer is entitled to “detach a copy of its Applications” in source code format and to obtain its Customer Content, subject to the specifications in the documentation. The customer must give written notice, pay all remaining Fees and complete the process within 30 days after the end of the term; the Software is then de-installed or destroyed.[1] The Subscription Compliance Terms confirm that a customer that does not renew may exercise Detachment within the 30-day grace period.[2] The programme row is Detachment right.
Virtualization and partitioning
The contract documents contain no virtualization or partitioning rules. The nearest rule is the bar on circumventing the technological measure that controls access to, or measures use of, the Software.[1]
Cloud and self-managed
The verification regime differs by deployment: remote verification applies to on-premise and self-managed customers and is not needed in OutSystems Cloud hosted environments.[2] For OutSystems Cloud customers, the Subscription section of the ODC Portal and the AO figures in the Customer Portal and Service Center are the operational view of usage, as described in OutSystems Application Objects.[5]
Programs and governing law
The OutSystems entity with which a customer contracts, the governing law and the courts depend on where the customer is domiciled.[4] The page, headed “Updated: 5 November 2025”, gives the following for five of its regions:[4]
| Customer domiciled in | Contracting entity | Governing law |
|---|---|---|
| United Kingdom or Ireland | OutSystems Limited | England and Wales |
| Benelux or Poland | OutSystems Benelux B.V. | Dutch law; courts of Utrecht after mediation under the SGOA regulations |
| Germany, Switzerland and Austria | OutSystems Germany GmbH | German law; courts of Munich by default |
| Americas except Latin America and Brazil | OutSystems, Inc. (Boston) | New York law; courts of the State of New York |
| Brazil | OutSystems Brasil Ltda. | Brazilian law, with mandatory mediation |
The page lists further regions that are not summarised here. It excludes the UN Convention on Contracts for the International Sale of Goods and the Uniform Computer Information Transactions Act.[4] The row is Customers in the Americas contract with OutSystems, Inc. under New York law.
Other terms with licensing relevance
The MSA says the AI Features serve the customer’s development and maintenance of applications and that OutSystems does not use or retain Customer Content or Confidential Information to train or fine-tune the AI models.[1] It treats intellectual property in applications and customer content as owned by the customer.[1]
Out of scope
This article does not cover the Software License Trial Agreement or the Early Access terms, which are summarised in OutSystems AI agents, Mentor and trial licensing, nor the support terms and service level page, which could not be read, nor the Data Processing Agreement. It does not state prices, the definition of Users or how a customer’s negotiated agreement may depart from these public documents.