Oracle APEX Service Cloud: Autonomous APEX, Low-Code Platform Licensing & Cost Guide 2026

Oracle APEX Licensing Basics: What Is Actually Free?

Oracle APEX is explicitly licenced as a no-additional-charge component of Oracle Database. Every Oracle Database license — Enterprise Edition, Standard Edition 2, and Oracle Database Free Edition — includes APEX at no extra cost. This means the APEX framework itself, the APEX development environment, the APEX runtime, and all APEX features are included in whatever Oracle Database license you hold. Oracle has consistently maintained this position since APEX's introduction as HTML DB in Oracle Database 10g.

Oracle APEX licensing provides two usage rights: developer access (building applications in the APEX development environment) and end-user access (using applications built with APEX). Both are included in the Oracle Database license. There is no Named User Plus metric or Processor metric that specifically applies to APEX users separately from Oracle Database — APEX users are counted as Oracle Database users, subject to the standard metric rules for the edition of Oracle Database being used.

This is the most important point to understand: APEX is not separately licenced, but APEX users are Oracle Database users. A Named User Plus license for Oracle Database EE covers one person accessing the Oracle Database — including through APEX applications. If your NUP license count does not cover all users accessing Oracle Database through APEX applications, you are non-compliant on Oracle Database NUP, not on APEX specifically. Oracle's LMS scripts identify APEX user activity in the APEX_WORKSPACE_ACTIVITY_LOG and AWR tables, and APEX user counts are incorporated into NUP compliance calculations during audits.

On-Premise Oracle APEX: Enterprise Edition, Standard Edition 2 and Free Edition

Oracle APEX is available on Oracle Database Enterprise Edition, Standard Edition 2, and Oracle Database Free Edition (the renamed Oracle Database Express Edition). The APEX features available vary by database edition, as APEX capabilities that depend on Enterprise Edition-specific database features cannot be used on SE2 or Free Edition.

Oracle Database Enterprise Edition with APEX provides full APEX functionality including all APEX Workspace features, REST Enabled SQL, APEX Search, ORDS (Oracle REST Data Services) integration, and Oracle AI Assist in APEX (in APEX 24.x+). Enterprise Edition also allows APEX to access EE features like Advanced Queuing, Workspace Manager, and Oracle Text — each of which carries its own license obligations when used through APEX.

Oracle Database Standard Edition 2 with APEX provides full core APEX functionality but restricts access to features dependent on EE database options. Importantly, APEX on SE2 cannot access features like Oracle Text for full-text search (Oracle Text is a separately licenced EE option), Oracle Workspace Manager, or the Diagnostics Pack. SE2 with APEX is appropriate for departmental applications and medium-complexity enterprise applications where EE database option features are not required.

Oracle Database Free Edition (the community version with 2 CPU thread limit, 12 GB user data limit) includes APEX and is suitable for APEX development, prototyping, and small production workloads. Oracle explicitly states that Free Edition may be used in production for qualifying workloads. The 12 GB data limit is the binding constraint for production APEX on Free Edition — not a license fee constraint.

Oracle APEX Service on OCI: Pricing Model and When to Use It

Oracle APEX Service is a fully managed, dedicated APEX environment on OCI. It is distinct from deploying Oracle APEX on an Oracle Database instance in OCI — APEX Service is a service-level product where Oracle manages the underlying Oracle Database, ORDS, and APEX framework, and customers interact only with APEX workspaces and applications.

Oracle APEX Service is priced on an OCPU/hour basis for the compute resources allocated to the APEX Service environment, plus OCI storage costs for the underlying Oracle Database used by APEX Service. Oracle structures APEX Service with dedicated compute resources allocated to each APEX Service instance, unlike the shared infrastructure model of some competing low-code platforms.

APEX Service on OCI does not require the customer to hold a separate Oracle Database license — the Oracle Database underlying APEX Service is included in the APEX Service pricing. This is an important distinction from deploying APEX on a BYOL Oracle Database instance in OCI, where the customer must bring their own Oracle Database EE or SE2 license and pay separately for OCI compute resources. For enterprises without existing Oracle Database EE licenses, APEX Service may be more economical than a BYOL approach that requires new license purchases.

APEX Service compute costs accumulate as OCPU-hours, meaning the service can be paused or stopped when not in use to reduce costs — a cost optimization pattern that Oracle promotes for development and test APEX Service environments. Production APEX Service environments running continuously accumulate OCPU costs 24/7, making right-sizing the OCPU allocation important for cost control.

Oracle APEX on Autonomous Database: The Cost and Capability Advantage

Oracle Autonomous Database (ADB) — both Autonomous Transaction Processing (ATP) and Autonomous Data Warehouse (ADW) variants — includes Oracle APEX at no additional cost. APEX workspaces can be provisioned directly within any Autonomous Database instance, making ADB the recommended Oracle-managed path for APEX application development and deployment on OCI.

The commercial advantage of APEX on ADB versus APEX Service is that ADB is a more general-purpose platform — the same ADB instance serving APEX applications can also serve OLTP workloads, data integration via ORDS, and Oracle Analytics Cloud (OAC) integration. APEX Service is purpose-built for APEX-only workloads, while ADB provides APEX as one capability within a broader database services portfolio.

APEX on Autonomous Database benefits from Oracle's AI integration in ADB — including AI Vector Search (covered in our Oracle Database 23ai licensing guide), Oracle AI Assist for APEX application development (accelerating APEX declarative development using generative AI), and Select AI (natural language query in APEX applications backed by OCI Generative AI). These AI capabilities are included within the Autonomous Database subscription and do not require separate license fees for the APEX integration — though OCI Generative AI token consumption for Select AI queries is charged separately.

Autonomous Database's auto-scaling capability is particularly valuable for APEX applications with variable user loads. ADB can scale OCPU and storage independently, and APEX workloads benefit from auto-scaling during peak usage without the manual intervention required for on-premise Oracle Database capacity management. Our Autonomous Database licensing guide covers ADB pricing, OCPU scaling, and storage cost management in depth.

Oracle Database Options Risk When Using APEX: What to Watch For

APEX is included in Oracle Database at no extra cost, but APEX applications can inadvertently activate separately licenced Oracle Database options through their data access patterns. This is the primary Oracle APEX compliance risk that enterprises must manage, particularly in environments where APEX is used to build operational applications on top of an existing Oracle EE database.

Oracle Text and APEX Search. APEX's built-in search functionality can use Oracle Text for full-text indexing and search. Oracle Text is a separately licenced Oracle EE option. If an APEX application uses the APEX_SEARCH package or creates Oracle Text domain indexes on database columns, and the Oracle Database instance does not have an Oracle Text license (which is often not realized as a separate charge since Oracle Text is installed by default), this creates compliance exposure. Our Oracle Text licensing guide covers the specific SQL commands that trigger Oracle Text license obligations.

Oracle Workspace Manager. APEX Workspace Manager integration allows APEX applications to manage workspace versions for historical data tracking. Oracle Workspace Manager is an EE feature but is not separately licenced — however, enterprises should verify that Workspace Manager usage in APEX does not conflict with their SE2 license if APEX is deployed on SE2, since Workspace Manager is not available in SE2.

Diagnostics Pack via APEX performance monitoring. APEX developers who use Oracle's built-in APEX performance monitoring pages — which surface AWR data and Active Session History — may be inadvertently accessing Diagnostics Pack functionality if the CONTROL_MANAGEMENT_PACK_ACCESS parameter is set to DIAGNOSTIC+TUNING. APEX performance monitoring does not explicitly require the Diagnostics Pack, but if Diagnostics Pack-level data is being surfaced in the APEX development environment, Oracle's LMS team will assert that the pack is in use. Our Diagnostics Pack guide covers the parameter settings to protect against this assertion.

Oracle APEX vs Microsoft Power Apps vs Salesforce Platform: Cost Comparison

Oracle APEX is frequently evaluated against Microsoft Power Apps, Salesforce Platform (formerly Force.com), OutSystems, and Mendix for enterprise low-code application development. The cost comparison is genuinely favorable to APEX for enterprises already standardized on Oracle Database — the marginal cost of APEX on an existing Oracle Database license is zero.

For enterprises already standardized on Oracle Database EE, APEX on-premise is essentially free — the only incremental costs are the ORDS server infrastructure and any OCI compute if APEX is hosted in OCI. For enterprises without Oracle Database licenses, the cost comparison shifts: acquiring Oracle Database EE licenses purely to gain access to APEX is economically irrational when Power Apps or a competing low-code platform can serve the application development need without Oracle Database overhead. The APEX economics work in Oracle Database environments, not as a standalone platform investment.

The strategic consideration for CIOs is whether Oracle APEX can reduce the proliferation of third-party low-code platform licenses in Oracle Database-centric enterprises. We have seen enterprises successfully consolidate departmental Power Apps and Salesforce Platform applications onto Oracle APEX, reducing total low-code platform license spend by 60–80% while improving data integration with Oracle ERP systems. Our Oracle License Optimization practice supports this consolidation strategy as part of broader Oracle commercial restructuring engagements.

Enterprise Oracle APEX Deployment: License Considerations for Large-Scale Use

Enterprise-scale APEX deployments — where hundreds or thousands of internal users access APEX applications built on Oracle Database EE — require careful attention to the interaction between APEX user counts and Oracle Database Named User Plus metrics.

In Oracle Database EE with Named User Plus licensing, each person who accesses the database — including through APEX applications — counts as a named user. The NUP minimum is 25 named users per Processor license. For an Oracle Database EE instance on a four-processor server (with Core Factor Table adjustment), the NUP minimum is 100 named users. If 500 people access APEX applications on that database, 500 NUP licenses are required — not just 100.

Oracle Database EE Processor licensing is an alternative to NUP that may be more economical for large APEX user populations. Under Processor metric, the license fee is fixed based on the number of Processors (core-adjusted) hosting Oracle Database, regardless of the number of users accessing APEX applications. For APEX deployments with large, diffuse user populations — employee self-service portals, customer-facing APEX applications — Processor metric is almost always more economical than NUP.

External user APEX applications — where Oracle Database customers build public-facing applications using Oracle APEX and those applications are accessed by non-employees — require attention to Oracle's Application User licensing metric. For external-facing APEX applications where it is impractical to license every external user as an NUP, Oracle may agree to Application User Plus metric licensing as part of a negotiated agreement. Our Oracle Contract Negotiation service has structured APEX-specific license metrics in Oracle agreements for enterprises with large external user APEX application portfolios.