Application objects (OutSystems Support)
Catalog row in Vendor License Sources · Cited
- Kind
- Documentation
- Format
- HTML
- Applies to
- How Application Objects are counted in OutSystems 11 and OutSystems Developer Cloud, and AO limits. Page shows "Last updated: Sep 6, 2026". The page is rendered by script; the excerpts were transcribed from the rendered page.
- Evidence
- Each screen, entity, API method and custom Event counts as 1 AO
- AO capacity applies to production runtimes only
- AO usage is summed across all production runtimes
- Each entity and API method counts once per runtime
- Disabled applications keep counting until they are deleted
- All selected entities of an ODC connection count when the connection is referenced
- Library AO treatment differs between OutSystems 11 and ODC
- Library AO treatment differs between OutSystems 11 and ODC (2)
- Custom Events count as AOs in ODC but not in OutSystems 11
- Custom Events count as AOs in ODC but not in OutSystems 11 (2)
- API methods consumed through AI Models count as AOs
- API methods consumed through AI Models count as AOs (2)
- O11 entities imported into ODC through Data Fabric do not count
- O11 entities imported into ODC through Data Fabric do not count (2)
- Forge components may contribute to the AO count
- AO limits and usage are shown in the Customer Portal, Service Center or ODC Portal