Oracle Application Express License – Is it Free?

Oracle Application Express License – Is it Free?

Executive Summary: Oracle Application Express (APEX) is a low-code development platform included with Oracle Database. There is no separate license fee for Oracle APEX – it’s provided as a no-cost feature of all Oracle Database editions.

However, “free” comes with context: you can use APEX without additional cost only if you have a licensed Oracle Database (or utilize Oracle’s free database offerings in limited scenarios).

This advisory explains the nuances of APEX licensing for enterprise IT Asset Management, clarifying when APEX is truly free and what considerations to keep in mind to ensure compliance and cost-effectiveness.

Understanding Oracle APEX and Its Licensing Context

Oracle Application Express (APEX) is Oracle’s flagship low-code tool for building web applications rapidly.

It runs inside the Oracle Database – meaning APEX is essentially part of the database software stack. From a licensing perspective, this integration is crucial: APEX inherits the licensing of Oracle Database.

There’s no separate product license just for APEX. In practical terms, if your enterprise owns a valid Oracle Database license (Standard Edition, Enterprise Edition, etc.), you automatically have the right to use APEX on that database at no extra cost.

Insight: Think of APEX as a free add-on or feature of Oracle Database. For example, just as PL/SQL or Oracle SQL are included in the database license, APEX is also bundled.

There’s no user-count or application-count licensing for APEX – you can build unlimited apps for unlimited end-users, as long as the underlying Oracle Database is properly licensed.

This makes APEX very attractive for Oracle customers: an organization already paying for Oracle Database can leverage APEX to build numerous internal applications without purchasing additional application platform licenses.

Actionable takeaway: If your company is already invested in Oracle Database licenses, take advantage of APEX to maximize the value of those licenses.

You’re essentially getting a powerful application development platform “for free” on top of the database you’ve paid for.

APEX as a Free Feature of Oracle Database

Is Oracle Application Express truly free? The answer is yes – with a big caveat. Oracle APEX is free to use with any Oracle Database edition that you have licensed. This includes:

• Oracle Database Enterprise Edition (typically licensed per processor or per user in an enterprise) – APEX is included at no extra charge.
• Oracle Database Standard Edition 2 (SE2) – APEX is included here too, with no additional cost, under SE2’s more affordable license model.
• Oracle Database Express Edition (XE) – Even Oracle’s free limited database edition includes APEX at no cost. (XE is Oracle’s free-to-use edition with resource limitations; we’ll discuss its limits shortly.)
• Oracle Autonomous Database and Oracle Cloud Database Services – APEX come built-in with Oracle’s cloud database offerings and do not require a separate license. If you’re paying for an Oracle cloud database service (or using a free tier of it), you have the right to use APEX on it freely.

In summary, APEX itself requires no purchase.

The only licensing requirement is that the Oracle Database it runs on must be properly licensed (or be an allowed free database). Oracle’s official stance is that APEX is a “fully supported, no-cost feature” of Oracle Database. For enterprises already running Oracle databases, there is no incremental cost to deploy APEX applications.

There are also no separate support fees for APEX – if you have an Oracle Database support contract, it covers APEX support as well. This unified support means you can log service requests for APEX issues under your database support agreement.

Example scenario: A global enterprise with an Oracle Database Enterprise Edition license can build an internal employee portal or a custom CRM using APEX without incurring additional licensing costs.

Whether the app serves 100 users or 10,000 users, Oracle’s license cost remains the same (it’s tied to the database processor or user licenses, not the number of users using APEX). This is a big contrast to many third-party low-code platforms that charge per user or app.

Actionable takeaway: Confirm that your Oracle databases are licensed correctly, and you can confidently deploy APEX applications on them without extra fees.

Ensure your Oracle contracts or ordering documents explicitly cover the databases where APEX will run – if they do, you’re in the clear to use APEX enterprise-wide.

“Free” Usage Options and Limitations

What if you don’t already have an Oracle Database license?

Can you still use Oracle APEX for free? Oracle provides a couple of avenues for using APEX at no cost, primarily for non-production or small-scale needs:

• Oracle Database Express Edition (XE): This is Oracle’s free edition of the database, which includes APEX. You can download and use XE without incurring any license fees, even in production environments. However, XE has technical limitations: it can only use up to 2 CPU threads, 2 GB of RAM, and store up to 12 GB of user data. It also doesn’t come with Oracle Support. This makes XE + APEX suitable for departments, prototypes, or small applications, but not for large enterprise-scale deployments. An ITAM professional should be aware that running APEX on XE is legal and free, but the environment is intentionally limited in capacity. It’s a great way to develop or pilot APEX applications at zero cost, and some small businesses even use it in production if the usage fits within XE’s limits. For larger needs, you’ll need a full Oracle DB license.
• Oracle APEX on Oracle Cloud Free Tier: Oracle Cloud Infrastructure (OCI) offers an Always Free tier, which includes an Always Free APEX Service. This is essentially a managed Oracle APEX environment in the cloud, backed by a small Autonomous Database instance. It allows you to build and run APEX applications with no cost, as long as your usage stays within the free tier limits (for example, a certain amount of CPU and storage). This is another excellent option for experimenting with or developing APEX apps without licenses. The free cloud APEX service has resource caps (e.g., 1 OCPU and limited storage) but is fully managed by Oracle and even includes the latest features automatically.
• Downloading APEX separately: Oracle allows you to download the APEX software package directly from their website for free. Anyone can download the APEX runtime and development environment. However, note that even though APEX software is free, it must be installed on an Oracle Database to run. So if that database is not XE or not otherwise licensed, you cannot use that APEX in production without buying a database license. In other words, downloading APEX for free is mainly useful for installing it on top of an existing Oracle DB or for trial purposes.

Example scenario: Suppose a team within a large enterprise wants to try building a solution with APEX but the organization hasn’t committed to Oracle Database yet.

The team could start by using Oracle XE on a small server or spin up an Always Free APEX Service on Oracle Cloud.

They could develop a proof of concept without any upfront license costs. If the app demonstrates value, they can then migrate to a fully licensed Oracle Database (on-premises or cloud-based) for production deployment. This way, they only incur license costs once they decide to scale up beyond the free resources.

Actionable takeaway: Leverage Oracle’s free options (XE and Cloud Free Tier) for development, testing, or very small applications.

This minimizes cost while you evaluate APEX’s fit for your needs. Just be mindful of the limits – both XE and the free cloud service have capacity constraints.

Plan for a path to a licensed database once your application outgrows these free environments.

On-Premises vs. Cloud Deployment – Cost Considerations

Whether you deploy APEX on-premises or in the cloud, the licensing principle remains the same: APEX itself is free; the usage of Oracle Database is what may incur costs.

However, the way you pay for that underlying database can differ:

• On-Premises: In a traditional on-prem setup, your organization needs to have Oracle Database licenses (purchased perpetual licenses or a ULA, plus support contracts as applicable). These are typically licensed by processor cores or by Named User Plus counts, depending on your contract. Once you have the database installed and licensed on your servers, adding APEX on top doesn’t change the licensing at all – no new fees are incurred. The costs to consider here (beyond the DB license) are infrastructure (server hardware and storage) and possibly the Oracle HTTP Server or Oracle REST Data Services (ORDS) for running the APEX web interface – although those are also provided free of charge. Most enterprises use ORDS (a Java mid-tier component) to front APEX; ORDS itself is free to use. The key cost driver on-prem is ensuring every processor running an Oracle database for APEX is licensed according to Oracle’s policies (which can be expensive if using Enterprise Edition on a large multi-core machine). Some organizations save cost by using Standard Edition 2 for APEX databases (SE2 has a lower-cost, fixed-socket license, ideal for smaller servers) instead of Enterprise Edition, if SE2’s capabilities and limits meet the application’s needs.
• Oracle Cloud (OCI): Oracle offers APEX in the cloud in two main ways. First, any Oracle Autonomous Database service (whether transaction processing or data warehouse flavor) includes APEX. If your enterprise has an Autonomous Database subscription, you can use APEX on it at no extra charge. The cloud subscription is typically a monthly cost based on CPU and storage usage. Second, Oracle offers a dedicated service called APEX Application Development, essentially a platform-as-a-service specifically designed for APEX applications, which bundles the database and APEX together. This service has a straightforward consumption-based pricing: for example, a small APEX service with 1 OCPU and some storage starts at roughly $120 per month (and scales upward with more capacity). In OCI, you also benefit from an Always Free allowance (discussed earlier) for small usage. The advantage of Oracle’s cloud is simplicity – you don’t separately license the database; you just pay for the cloud service as you use it (or not at all if within free limits). For ITAM, this shifts the concern from license compliance to cloud subscription management. If your company has unused on-prem Oracle licenses, Oracle even allows a Bring Your Own License (BYOL) model to get discounts on the Autonomous Database service.
• Third-Party Cloud (AWS/Azure): You can run Oracle Database with APEX in other clouds as well. Options include using Oracle on Amazon RDS or running Oracle Database on a cloud VM. In these cases, you typically must bring your own Oracle DB license or use the cloud provider’s license-included instances (for example, AWS offers an “License Included” Oracle database on RDS, where the hourly rate hides the Oracle license cost). Either way, you’re paying for the right to use the database, either via your Oracle agreement or via the cloud bill. APEX again adds no additional cost. If leveraging AWS or Azure, ensure you count those deployments in your Oracle license inventory (unless you use a license-included service where AWS/Azure is effectively reselling the license for that usage).

Actionable takeaway: Choose the deployment model that aligns with your cost strategy. On-premises gives you control, but it requires an up-front license investment (or existing licenses).

Oracle Cloud can offer predictable subscription costs for APEX and might be cost-efficient for short-term or variable workloads (plus there’s a free tier).

If using other clouds, be diligent in applying your Oracle licenses properly or using license-included offerings to stay compliant.

Hidden Costs and Compliance Pitfalls

While Oracle Application Express itself doesn’t add cost, enterprise ITAM professionals should remain vigilant about a few indirect costs and licensing pitfalls:

• Oracle Database License Compliance: Since APEX encourages building many apps and potentially expanding Oracle Database usage, ensure that any database instance hosting APEX applications is fully licensed. APEX might spur new projects and deployments – for example, a department quickly sets up a new Oracle database to host an APEX application. It’s easy to overlook that your Oracle license entitlements must cover every such instance. Keep an inventory of where Oracle databases (with APEX) are installed, and verify you have the appropriate licenses (per CPU or user). Oracle license audits will check for database usage; even though APEX itself is free, running it on an unlicensed database would be a compliance violation.
• Support and Patching: Using APEX in production ideally means having support. If you’re using a paid Oracle Database with support, you’re covered for patches and assistance on APEX issues. However, if you choose to run APEX on Oracle XE or an Oracle database without a support contract, you won’t have Oracle’s help if something goes wrong. This isn’t a licensing fee, but it’s a risk/cost consideration – many enterprises will factor in the value of Oracle Support. Ensure that mission-critical APEX apps are running on databases with active support contracts so you can get timely updates (APEX releases frequent updates that often fix bugs and security issues).
• Capacity and Scalability Costs: APEX itself can handle enterprise-scale usage (large companies use it for significant applications), but the underlying database and infrastructure must scale. As your APEX apps grow, you may need more CPU cores, more database licenses, or a move to a higher edition. For example, reaching the limits of Standard Edition 2 (which is capped at 16 CPU threads per server and a maximum of 2 sockets) may necessitate an upgrade to Enterprise Edition licenses, which are substantially more expensive. Similarly, outgrowing the free cloud or XE will mean transitioning to paid resources. It’s important to anticipate these scaling costs early. APEX’s “free” nature can lead to rapid adoption—make sure your organization isn’t surprised by the need to license additional database instances down the line.
• Optional Oracle Features: Be aware that some Oracle Database features are licensed separately (like Oracle Advanced Security, Partitioning, etc.). Using APEX doesn’t inherently require any of these extra-cost options – APEX uses standard database features. But suppose your APEX application explicitly uses an Oracle feature that isn’t covered by your base license (for instance, calling Oracle Spatial APIs, or using Oracle BI Publisher for fancy reporting). In that case, you might trigger the need for those licenses. This is a rare scenario, but an architect or asset manager should double-check that APEX application requirements don’t inadvertently pull in any “paid” database options or packs.
• Vendor Management and Contract Clarity: Ensure that your Oracle contracts and ordering documents reflect your use of Oracle Database for APEX. While APEX itself might not be listed (since it’s not a separate licensable item), it’s good practice to document internally that you are utilizing APEX. In any communications with Oracle, if relevant, have them acknowledge that APEX usage is covered under your existing licenses. Most Oracle sales reps will confirm that, but having it in writing (even in an email) can be helpful for clarity. Also, be aware of any Oracle policy changes. As of now, Oracle APEX is free with the database – a fact that has been true for years and is unlikely to change, given Oracle’s strategy. However, always stay updated via Oracle’s official licensing documentation.

Actionable takeaway: Treat an APEX deployment with the same level of rigor as any other Oracle software deployment. Free doesn’t mean consequence-free.

Keep tabs on where it’s used, ensure underlying licenses and support are in place, and avoid complacency about compliance.

By doing so, you’ll continue to reap the cost benefits of APEX without risking unbudgeted surprises.

Comparing APEX to Other Low-Code Platforms (Licensing and Cost)

Many enterprises evaluate Oracle APEX against other low-code or rapid development platforms. One of the biggest differences is the cost model.

Here’s a quick comparison of Oracle APEX’s licensing versus a few popular alternatives:

Why APEX stands out: If your organization already owns Oracle Database licenses (which are admittedly expensive), APEX lets you build as many applications and onboard as many users as needed without ever increasing your licensing spend.

In contrast, other low-code platforms will increase in cost as you add users or applications or require higher tiers of the platform. This can make APEX extremely cost-effective from an ITAM perspective in an Oracle-heavy environment.

However, if your organization does not use Oracle Database at all, adopting APEX would mean incurring the significant cost of an Oracle Database license solely to run APEX.

In such cases, the other platforms – with their licensing fees – might be more financially justifiable or simpler.

For example, a company without any Oracle may find it cheaper to pay for a few Power Apps user subscriptions than to license an Oracle database server. It all depends on scale and existing investments.

Actionable takeaway: Evaluate the total cost of ownership. APEX can drastically reduce incremental platform costs if you have an Oracle infrastructure, whereas other low-code tools might be better fits for organizations trying to avoid Oracle licensing.

From an IT asset management perspective, always compare the fully loaded costs: database licenses, support, and hardware for APEX versus subscription fees and potential cloud costs for others. Each model has trade-offs in cost, scalability, and vendor dependence.

Recommendations (Practical Tips for Managing APEX Licensing)

1. Leverage APEX Where You Already Have Oracle – If your enterprise has Oracle Database licenses, use APEX to maximize ROI. It’s essentially “free” functionality you’ve already paid for. Build internal apps on APEX instead of buying new third-party tools whenever they fit the requirements.

2. Keep a License Inventory of APEX Deployments – Track all database instances that host APEX applications. Ensure each is licensed (or an approved free instance). This way, if an Oracle audit occurs, you can demonstrate that a proper DB license supports every APEX environment or falls within free usage rights.

3. Use Oracle XE and Free Services Strategically – Employ Oracle Database XE or Oracle’s Always Free APEX Service for non-production, training, or small-scale projects. This avoids the need for costly licenses for experimental work. Just plan migrations for when projects need to scale beyond the free limits.

4. Consider Standard Edition 2 for Cost Savings – Many APEX applications can run on Oracle SE2 instead of Enterprise Edition. SE2 has a lower cost (and even a socket-based licensing cap). If your APEX app doesn’t require Enterprise-only features, deploying it on SE2 can significantly cut licensing expenses.

5. Stay Updated on APEX and Oracle Licensing – Oracle occasionally updates licensing policies or introduces new services (for instance, the dedicated APEX cloud service). Subscribe to Oracle’s communications or licensing advisory forums. Ensure your team knows that as of now, APEX is free, so there’s no confusion, but also stay alert in case Oracle’s stance evolves.

6. Educate Developers and Architects – Make sure those building APEX apps understand the licensing context. They should be aware that using APEX incurs no user costs, which is beneficial. However, if they spin up a new Oracle Database instance for an app, they need approval to ensure it is properly licensed. Also, educate them about avoiding use of database features that aren’t licensed in your environment (for example, if your Oracle DB license doesn’t include certain options, developers should not use them in APEX apps).

7. Monitor Resource Usage – Implement monitoring on your APEX databases for CPU, storage, and user count growth. This helps predict when you might need to scale up to additional licenses or move to a different infrastructure. Being proactive means you can budget in advance rather than react to capacity issues (which could force a rushed license purchase).

8. Review Contracts for Cloud vs On-Prem – If you shift an APEX workload to Oracle Cloud, review how your on-prem licenses might be re-utilized. Oracle’s BYOL programs might let you repurpose licenses in the cloud with cost benefits. Conversely, if you opt for a cloud subscription for APEX, adjust your on-premises license counts if some are now unused (perhaps to save on support renewals or to redeploy elsewhere).

9. Engage Oracle or Experts for Clarity – Don’t hesitate to contact your Oracle account manager or a licensing consultant if unsure about an APEX deployment’s compliance. Obtaining a written confirmation that “APEX is included, no extra license required,” as stated publicly, can provide peace of mind to management.

Checklist: 5 Actions to Take

For ITAM professionals managing Oracle APEX, here’s a step-by-step checklist:

1. Verify Current Usage: Inventory all instances of Oracle APEX in your organization. Identify the underlying Oracle Database for each (on-prem server, virtual machine, AWS RDS, Oracle Cloud, etc.).
2. Confirm License Coverage: For each identified database running APEX, verify that you have a valid Oracle Database license or that it’s an approved free instance (Oracle XE or a free cloud). Document the license number or support CSI tied to each, for audit readiness.
3. Assess Scale and Limits: Check the size and load of each APEX deployment. Are any nearing the limits of their environment (e.g., an app on Oracle XE hitting the 12GB data ceiling)? If so, plan to upgrade to a licensed edition or a scaled-up service before it becomes an emergency.
4. Optimize Deployment Choices: Match each APEX application’s needs to the most cost-effective infrastructure. For example, small departmental app? – Maybe keep it on SE2 or Oracle Cloud APEX Service. Enterprise-critical app? – Ensure it’s on a robust licensed Enterprise Edition or Autonomous DB for reliability. Ensure you’re not “over-licensing” (paying for EE when not needed) or under-licensing (running a heavy workload on an XE due to oversight).
5. Update Policies and Educate: Update your organization’s IT usage policies to specify that Oracle APEX is an approved platform, but it must be deployed on approved database instances. Educate the relevant development and infrastructure teams about the free nature of APEX and the licensing requirements for the database. This prevents well-meaning teams from, say, installing APEX on an unlicensed test server or assuming they can start a production service on XE without review.

By following this checklist, you’ll maintain control over Oracle APEX usage and ensure your company reaps its benefits without compliance worries.

FAQs

Q1: Is Oracle Application Express (APEX) free to use?
A: Yes, APEX is free in the sense that Oracle does not charge for the APEX software or runtime. However, it runs on Oracle Database – so as long as you have a licensed Oracle Database (or are using Oracle’s free database edition), you do not pay anything extra for APEX. There’s no separate APEX license fee and no cost per user or application.

Q2: Do we need to purchase a specific license for APEX?
A: No. There is no separate licensing SKU for Oracle APEX. It is included with all editions of Oracle Database. If you have the database, you have the rights to APEX. If you don’t have an Oracle Database license, you would need to acquire one to deploy APEX in production (or use the free Oracle XE database, which has limits). In short, you license the database, and that covers APEX usage.

Q3: Can I run APEX in production on Oracle’s free Express Edition (XE)?
A: Technically, yes, you can use Oracle XE (which includes APEX) even for production, and it’s free of charge. Oracle XE’s license allows it to be used anywhere, but its technical restrictions (1 installation per machine, capped CPU/RAM/Storage) mean it’s intended for small-scale use. Enterprises typically use XE for development or very limited deployments, and if the application grows, they upgrade to a paid Oracle Database edition. Also note, Oracle XE comes with no support from Oracle.

Q4: How is APEX provided in Oracle Cloud or other clouds?
A: On Oracle Cloud, APEX is available by default in the Autonomous Database services and the dedicated APEX Application Development service. In both cases, you don’t separately license APEX – you just pay for the cloud service usage (or use the free tier). On AWS or Azure, if you deploy an Oracle Database instance (via VM or a service like RDS), you either use your own Oracle license or pay for a license-included instance. Once that database is running, you can install APEX on it freely. The key is that the database must be properly licensed through the cloud’s chosen model.

Q5: If APEX is free, why consider alternatives, or what’s the catch?
A: The “catch” is that APEX binds you to Oracle Database. If your organization already uses Oracle DB, this is a benefit with little downside. But if not, adopting APEX means introducing Oracle Database into your architecture, which can be a significant cost and complexity (licenses, DBAs, etc.). Alternatives like Power Apps, Mendix, or OutSystems don’t require Oracle Database and have their pricing models. Those might be preferable if avoiding Oracle is a goal. Additionally, alternatives may offer different capabilities or ease of use that could be important. In essence, APEX is cost-effective for Oracle shops, whereas non-Oracle shops need to weigh the total cost of integrating Oracle technology just to use APEX.

Read more about our Oracle License Management Services.

Do you want to know more about our Oracle Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit