OutSystems licensing is the set of commercial terms under which OutSystems sells its low-code and AI development platform, now presented on its pricing page as the OutSystems Agentic Systems Platform, together with the OutSystems 11 (O11) platform that preceded OutSystems Developer Cloud (ODC). Subscriptions are priced on three drivers that the pricing page lists in this order: the scale and complexity of the apps, measured in Application Objects (AOs); the number of non-anonymous end users, with internal and external users counted separately; and additional capabilities such as extra runtimes, 24x7 support, higher uptime and compliance add-ons.[1] The unit that makes the model distinctive is the AO: a count of screens, database tables, API methods and some other objects across the production apps of a customer.[2]
OutSystems is unusual among the vendors in the wiki in that its compliance mechanics are public. The Subscription Compliance Terms, which are incorporated into the Master Subscription Agreement, describe renewal notice, a grace period, a reinstatement fee, quarterly remote usage verification for self-managed customers and the price at which excess usage is invoiced.[4] Those terms, and the way the Master Subscription Agreement defers the meaning of “Application Object” and “Users” to documentation pages, are covered in OutSystems subscription compliance and contract terms.
Editions
OutSystems describes three commercial lines on its pricing page: the platform subscription, add-ons, and a free Personal Edition.[1] The fair use page names the platform subscription for ODC the ODC Platform Edition and lists the default configuration of O11 editions.[5]
| Line | What the documents state |
|---|---|
| Platform subscription (ODC Platform Edition) | Development, non-production and production runtimes; fully managed OutSystems cloud, on-premises, private cloud, or sovereign and regulated cloud deployment; 99.5% uptime guarantee; 8x5 professional support; ISO 27001; starts with 100 internal users[1] |
| Add-ons | Additional non-production and production runtimes, upgrade to 24x7 support, upgrade to 99.95% uptime, compliance certificates (SOC2 Type II, PCI DSS and others), more internal and external users[1] |
| OutSystems Personal Edition | Free, up to 100 internal users, for exploring and learning[1][7] |
| OutSystems 11 Standard and Enterprise (2023) | One development, one non-production and one production environment, each with a Class 1 front-end[5] |
| OutSystems 11 Enterprise (2022) | Eligible for renewals only[5] |
The catalog rows are ODC Platform Edition, OutSystems 11 Standard (2023), OutSystems 11 Enterprise (2023) and OutSystems 11 Enterprise (2022, renewals only). The pricing page does not use the name “ODC Platform Edition”. It presents the platform as the OutSystems Agentic Systems Platform, and the fair use page and the FAQ use the ODC name; the catalog treats these as the same subscription because both documents describe the same 100-internal-user starting point.[1][7] That equivalence is an inference, not a statement by OutSystems.
Metrics
The metrics recorded in the catalog are:
- Application Object (AO): “a measurement of the complexity of your applications”, counted in production runtimes. See OutSystems Application Objects.[2]
- Internal end user and External end user: non-anonymous end users, counted separately.[1]
- Runtime (stage): the location where apps run and data is hosted, with development, non-production and production stages.[1]
- Compute instance (ODC), Database compute and storage (ODC), Custom code execution duration and Agent Execution: resource defaults per stage on the fair use page.[5]
- Front-End and Database Class (OutSystems 11): the server classes of O11 Cloud environments.[5]
The Master Subscription Agreement states that “Application Object” and “Users”, as used in an Order, have the meaning given on specified OutSystems web pages.[3] The contractual definition can therefore change when the page changes, and the date shown on the AO page, 2026-09-06, is the effective date recorded in the catalog.[2]
Counting and floors
Three counting points follow from the documents. First, AO capacity applies to production runtimes only: development and non-production runtimes allow unlimited AOs but may not run production apps, and if a customer has several production runtimes it sums the AO usage of each against the total it has licensed.[2] Second, end users are counted when they are non-anonymous, and internal and external users are separate pools; ODC starts with 100 internal users and the free edition supports up to 100 users.[1][7] Third, ODC includes default resource capacity per stage: 15 compute instances (30 with High Availability), 16 GB of database compute, 500 GB of database storage, 30,000 seconds of custom code execution per day and 10,000 Agent Executions per month.[5] Each additional 150 AO pack adds compute instances to each stage.[5]
The pricing page states that the licensing model aligns with application complexity, number of users, environments, deployment needs, compute resources and enterprise requirements rather than charging separately for every feature or tool.[1] The pricing page also says that the integrated development environment and CI/CD tools are included with any subscription at no extra cost, so developers are not licensed as a separate metric in the public documents.[1]
Virtualization and partitioning
The public documents contain no virtualization or partitioning rules. The relevant boundary is the runtime stage. The Master Subscription Agreement forbids deploying or operating applications in production using a non-production environment, which matches the AO rule that capacity applies to production runtimes only.[3]
Cloud, self-managed and bring-your-own deployment
The pricing page lists deployment choices as fully managed OutSystems cloud, on-premises, private cloud and sovereign and regulated cloud, and says self-hosting is available in certain plans.[1] Customers that use the Software on-premise or in a self-managed environment cooperate in a remote usage verification once each calendar quarter; the Subscription Compliance Terms say this is not needed for a customer in an OutSystems Cloud hosted environment.[4] The pages reviewed describe no bring-your-own-licence rights for hyperscaler clouds.
Programs
Subscription Compliance Terms cover renewal and excess usage. Quarterly usage verification applies to self-managed customers. The Detachment right lets a customer take a source-code copy of its applications on exit.[3] Customers that buy through a reseller are subject to the End-User License Agreement, under which usage limits come from the Order between the reseller and OutSystems.[6] The contracting OutSystems entity and governing law depend on where the customer is domiciled; customers in the Americas other than Latin America and Brazil contract with OutSystems, Inc. under New York law.[9] Trials and the Personal Edition are governed by the Software License Trial Agreement.[8]
Out of scope
This article does not cover list prices, which OutSystems does not publish, partner agreements, the Forge repository terms, professional services or the support terms and service level page, which could not be read by the tools used. It does not cover the content of the AO page beyond what is summarised in OutSystems Application Objects, and it does not cover AI and trial terms, which are in OutSystems AI agents, Mentor and trial licensing.