Oracle License Types: Full Use, Proprietary Hosting, ESL, and ASFU Explained

Oracle License Types

Global CIOs, CFOs, and procurement leaders face a complex landscape of Oracle license types. These range from unrestricted Full Use licenses to specialized agreements, such as Proprietary Hosting, Embedded Software Licenses (ESL), and Application-Specific Full Use (ASFU) licenses.

This advisory provides a clear overview of each model, including its usage limits, cost implications, and strategic considerations, to help enterprises optimize their Oracle spend and avoid compliance issues. Understanding these license models upfront can prevent costly surprises down the road.

Oracle License Types Overview

Oracle offers four primary licensing models for its database and middleware products: Full Use, Application Specific Full Use (ASFU), Embedded Software License (ESL), and Proprietary Application Hosting (PAH).

Each comes with distinct usage restrictions, cost structures, and support terms.

The table below provides a quick comparison:

Table: Oracle license models and their typical cost discounts and usage limits.

Example: A global manufacturer initially utilized an ASFU license for an Oracle-powered ERP module, resulting in a nearly 50% reduction in database licensing costs.

However, when they later needed to integrate that Oracle database with other systems, the ASFU restrictions forced them to purchase new Full Use licenses (costing over $500,000).

The early savings were offset by the unplanned licensing spend – a cautionary tale about the importance of anticipating future needs.

Full Use Licenses – Unrestricted (at a Premium)

• Unlimited Internal Use: Full Use licenses have no functional restrictions – you can deploy Oracle for any internal application or purpose.
• Highest Cost: This license is purchased at full list price with no built-in discounts. Oracle also charges ~22% of the license cost per year for support, so ongoing fees are significant.
• Not for Resale/Hosting: You cannot use a Full Use license to provide services to third parties (e.g., hosting Oracle for clients) without a special agreement. Full Use is intended for your company’s internal use only.

Application Specific Full Use (ASFU) – Discounted for One Application

ASFU licenses provide Oracle software at a lower cost in exchange for restricted usage. An ASFU license is obtained through an Oracle partner/ISV and is contractually tied to a specific application.

For example, suppose you purchase a CRM system that utilizes an Oracle Database. I

In that case, the vendor may include an Oracle ASFU license, allowing the database to be used exclusively for that CRM system.

Key characteristics of ASFU include:

• Discounted Cost: ~50% off Oracle list price in exchange for use limited to one specific application.
• Customer Holds License: You (the customer) are the licensee under ASFU and typically pay Oracle annual support (around 22% of the discounted license price).
• Restricted Use Only: The Oracle software can only be used with the designated application; it cannot be repurposed for other systems or converted into a full, unrestricted license.

Embedded Software License (ESL) – Oracle Inside, Invisible to Users

An ESL (Embedded Software License) enables an ISV to include Oracle technology as a built-in component of its product.

In an ESL scenario, the end user does not separately license Oracle; it’s bundled and hidden inside the vendor’s appliance or software. Key aspects of ESL:

• Strictly Bundled Usage: Oracle software under an ESL can only be used as part of the ISV’s application. It is not available for any separate use by the customer, meaning the Oracle component can’t be repurposed or extended beyond the vendor’s solution. (For example, a medical device might ship with an Oracle database for its internal data; an ESL ensures the hospital cannot use that database for custom queries or outside applications.)
• Huge ISV Discount: ISVs pay only ~10–20% of Oracle’s list price (or a small royalty) under ESL, allowing them to bundle Oracle at a very low cost in their products.
• Vendor-Managed Support: The ISV holds the license and is responsible for all Oracle maintenance, patches, and support for the customer.
• No Customer Flexibility: Customers cannot expand or reuse the embedded Oracle outside of the vendor’s solution.

Proprietary Hosting (PAH) – Oracle Licensing for Service Providers

In the Proprietary Application Hosting (PAH) model, an ISV or service provider obtains special licensing to include Oracle software as part of a hosted service (such as a SaaS platform) for multiple end customers.

• For SaaS/Cloud Providers: Allows an ISV or MSP to use Oracle in services for third parties (multi-tenant SaaS) – a feature not permitted under a standard Full Use license.
• Royalties vs. Licenses: Instead of upfront licenses, the provider typically pays Oracle a monthly or annual fee based on usage (a royalty or revenue share) under a negotiated PAH agreement.
• Provider Manages Compliance: The provider holds the Oracle license and is responsible for support and compliance. End customers simply use the service; the provider works with Oracle for any support on the backend.

Recommendations

• Map Needs to License Type: Align your Oracle license types with usage needs. Use Full Use licenses for broad or changing requirements, and ASFU/ESL for fixed-purpose, vendor-tied solutions to save money.
• Demand Transparency from Vendors: When purchasing software that includes Oracle, ask the vendor to specify the license model provided (e.g., Full Use, ASFU, ESL, etc.). Ensure the contract spells out any usage limits to prevent misunderstandings.
• Plan for Future Needs: If there’s a chance you’ll expand the use of an Oracle-powered system, account for that upfront. It might be wiser to negotiate a more flexible license now (or an upgrade path) than to face a costly change later.
• Budget for Support Costs: Include Oracle support fees (approximately 22% of license cost annually) in your cost projections. For ASFU and ESL licenses, clarify who pays and manages support – you or the vendor – so support doesn’t lapse.
• Enforce Compliance: Implement processes to monitor Oracle usage and ensure it stays within permitted bounds. Educate IT teams about any special license restrictions (such as “only for Application X”) so they don’t accidentally violate the terms.
• Consult Experts for Big Decisions: For major Oracle deals or audits, consider engaging independent licensing experts to ensure informed decisions. They can identify negotiation opportunities (e.g., better discounts or contract terms) and help you avoid costly pitfalls in the fine print.
• Review and Update Agreements: Periodically revisit your Oracle licensing agreements. As your business evolves (e.g., cloud migrations, acquisitions, new products), you may need to adjust license models or negotiate new terms to stay optimized.

Checklist: 5 Actions to Take

1. Inventory Oracle Usage: Catalog all Oracle software instances in your organization and note their license types (Full Use, ASFU via vendor, ESL embedded, PAH service, etc.).
2. Confirm Restrictions: For each instance, review the contract or license terms to ensure compliance with the relevant restrictions. Document what each license allows and prohibits (e.g., “Database X – Oracle ASFU, tied to Acme CRM only”).
3. Project Growth: Anticipate how your use of each Oracle-powered system might expand. Flag any system where current license restrictions could hinder planned growth or integration.
4. Engage Stakeholders: If you identify a potential license mismatch (such as needing to use an Oracle database beyond its current allowance), discuss it with your vendor or Oracle account representative. Explore options now – such as adding licenses or switching models – rather than when urgency strikes.
5. Educate and Enforce: Share the basics of Oracle license types with your procurement, IT, and compliance teams to ensure a comprehensive understanding. Ensure that new projects involving Oracle technology undergo a license review to select the appropriate model from the outset.

FAQ

Q1: How is an ASFU license different from a Full Use license?
A1: An ASFU (Application Specific Full Use) license is purchased at a discount through an ISV and is legally restricted to one specific application. A Full Use license is purchased directly from Oracle (or a reseller) at full price and can be used for any internal purpose or application. In short, ASFU is a cheaper, limited-scope Oracle license tied to a vendor’s product, whereas Full Use is the more expensive “anything goes” license.

Q2: Can we later convert an ASFU or ESL license into a Full Use license?
A2: No, Oracle does not allow converting restricted licenses (ASFU/ESL) into Full Use. If you need to repurpose Oracle software beyond its original scope, you must purchase new licenses under the applicable model. This is why choosing the right type upfront is important – once an Oracle license is tied to an application, it cannot be broadened to general use.

Q3: If Oracle is bundled through a vendor, who handles support and updates?
A3: With ASFU, you (usually via the vendor) maintain an Oracle support contract and get updates from Oracle. Under ESL, the ISV provides all support and updates (customers cannot go to Oracle directly). In a PAH service, the provider supports you, and Oracle supports the provider. With Full Use, your company has a direct support contract with Oracle.

Q4: Can we use our own Oracle licenses instead of the vendor’s bundled license?
A4: In most cases, no. Oracle ASFU/ESL licenses are tied to the vendor’s product and contract. You generally cannot substitute your existing Oracle licenses, as the solution’s pricing and terms are based on the bundled model. Only if the vendor and Oracle agree to a special BYOL (Bring Your Own License) exception can you use your license, which is uncommon.

Q5: What if we use an embedded Oracle database beyond its allowed scope?
A5: That would violate the license. In such cases, you would likely need to purchase the appropriate Full Use licenses to cover the unapproved usage (and pay any associated fees to become compliant). The ISV might also face penalties from Oracle. Always treat an embedded or ASFU-licensed Oracle component as off-limits for any use outside its intended application.

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