There are three Oracle license types — Full Use, Application Specific Full Use (ASFU), and Embedded Software License (ESL) — and the one printed on your Order Form decides what you are allowed to run, what you paid, and how much audit exposure you carry. Most enterprises do not know which they hold until Oracle's LMS team tells them. Former Oracle insiders explain the differences, the price gaps, and the compliance traps Oracle relies on.
Short answer: Oracle sells software under three license types. A Full Use license grants unrestricted use for any application; an ASFU license is discounted but locked to one named third-party application; and an ESL is embedded inside a vendor's product with no direct customer access. Price falls and restrictions rise as you move from Full Use to ASFU to ESL.
Direct answer: Oracle's three license types are Full Use, Application Specific Full Use (ASFU), and Embedded Software License (ESL). Full Use is the standard commercial license with no application restriction. ASFU is a discounted license confined to one named third-party application. ESL is Oracle embedded invisibly inside a vendor's product, with no customer-facing access.
An Oracle license type is the category of usage rights attached to a license, and it is fixed at the point of sale on the Order Form. The license type does not change because you move the software to a bigger server or point a new tool at it. It is a contractual boundary, not a technical one — which is exactly why so many compliance gaps go unnoticed until an audit. The same Oracle Database Enterprise Edition binary can be licensed as Full Use for one customer and ASFU for another; only the contract distinguishes them.
Oracle designed these three tiers to sell the same technology into very different buyers at very different prices. A bank standing up its own database estate buys Full Use. A hospital buying a clinical system that happens to run on Oracle buys ASFU through the application vendor. A manufacturer buying a storage appliance with Oracle quietly inside it holds an ESL it may not even know exists. Each tier trades flexibility for discount, and each carries its own audit exposure. For the full picture of how database metrics interact with these types, see our Oracle Database Licensing Guide.
Definition: An Oracle Full Use license is the standard commercial license sold directly under your Oracle Master Agreement, granting the right to run the program for any purpose — custom applications, third-party applications, reporting, and integration alike. It is the most expensive and most flexible Oracle license type.
Full Use is the license most enterprises think of as "an Oracle license." You buy it on the Processor metric or the Named User Plus (NUP) metric, it appears on your own Oracle Order Form, and it carries no restriction on which application the software serves. You can run your ERP, a custom data warehouse, an analytics layer, and a dozen integrations on the same Full Use database without breaching scope — provided you have licensed enough processors or users.
Because Full Use carries no application restriction, it is the only license type that gives you genuine deployment freedom. It is also the benchmark Oracle uses when it calculates a back-license claim: when an ASFU or ESL deployment is found out of scope, Oracle prices the shortfall at Full Use rates. Full Use licenses are perpetual when bought that way, and Oracle Enterprise Support is charged at 22% of net license value per year (Oracle Technology Price List, 2026). The flexibility is real, but you pay for every bit of it — which is precisely why Oracle steers application-bundled deals toward ASFU instead.
Our Oracle License Optimization service maps every deployment to its actual license type and flags out-of-scope use before Oracle's LMS team finds it.
Definition: An Oracle ASFU (Application Specific Full Use) license is a discounted Oracle license sold by an Oracle partner bundled with one specific third-party application. It grants full functionality of the Oracle program but only when used to run that single named application — any other workload breaches the license.
ASFU exists because Oracle wants its database under as many applications as possible without giving away Full Use economics. An independent software vendor (ISV) or value-added distributor (VAD) buys Oracle at a steep discount and resells it bundled with their application — a clinical system, a billing platform, a logistics suite. The customer gets a fully functional Oracle database at 30–60% of the equivalent Full Use list value (Oracle Licensing Experts benchmark, 2026), with one hard condition: the database may only serve that one application.
The trap is in the word "only." ASFU does not stop working if you point Power BI at it, build a custom integration, or load its data into a separate warehouse — but every one of those uses is outside the license grant. Oracle treats out-of-scope ASFU use as unlicensed and prices the remediation at Full Use rates. This is one of the most common and most expensive findings we challenge in audit defense work. The restriction also limits your support relationship: ASFU support frequently routes through the application vendor rather than Oracle directly, which can complicate patching and escalation. We cover the deeper mechanics in our dedicated Oracle ASFU licensing guide.
ASFU scope trap: Connecting a reporting tool, ETL job, or second application to an ASFU database is the single most common way enterprises drift out of compliance. The deployment keeps running, no error appears, and the exposure compounds silently until Oracle's audit measures it — at Full Use prices.
Definition: An Oracle ESL (Embedded Software License) is an Oracle program embedded inside an ISV or OEM product, where the end customer never administers Oracle directly. The vendor licenses Oracle on a royalty basis, and the database is locked behind the application — direct access falls outside the ESL grant.
An ESL is the most restrictive and most heavily discounted Oracle license type. The Oracle software is invisible to the end user: there is no SQL*Plus prompt, no schema you administer, no database you tune. The application vendor packages Oracle as a component of their product — an appliance, a medical device, a network platform — and pays Oracle a per-unit royalty under an Oracle embedded license agreement. As far as the customer is concerned, they bought the vendor's product, not an Oracle database.
The boundary on an ESL is total opacity. The moment you open the embedded database to do something the application does not natively expose — querying it directly, adding your own schemas, connecting external tools, or repurposing it for another workload — you step outside the embedded grant and create a Full Use exposure. Because ESL deployments are often undocumented in the customer's own license records, they are easy to forget and dangerous to disturb. If your organization runs appliances or packaged products that "happen to use Oracle," treat them as ESL until proven otherwise, and never let an administrator log in directly without checking the contract first.
The three Oracle license types sit on a spectrum: as the price falls, the restrictions tighten and your direct relationship with Oracle fades. The table below sets out the practical differences buyers need to weigh before signing — or before responding to an audit.
| Attribute | Full Use | ASFU | ESL (Embedded) |
|---|---|---|---|
| Permitted use | Any application or workload | One named third-party application only | Hidden inside one vendor product; no direct use |
| Sold by | Oracle directly, under your OMA | Oracle ISV / VAD partner | ISV / OEM under embedded royalty agreement |
| Indicative price vs Full Use | 100% (list benchmark) | ~30–60% of Full Use list | Lowest; royalty-based, often a fraction of ASFU |
| Direct database access | Full | Full, but only for the named app | None — locked behind the application |
| Support route | Oracle directly (22% of net license value/yr) | Often via the application vendor | Via the embedding vendor |
| Main audit risk | Under-counted processors / NUP | Out-of-scope use beyond the named app | Direct access or repurposing the embedded DB |
| Upgrade to broader rights | N/A — already unrestricted | Trade-up to Full Use (pay the difference) | Buy Full Use to use directly |
Read down the price row and the logic is obvious: Oracle discounts the license in exchange for narrowing what you may do with it. Read down the audit-risk row and the buyer's problem is equally clear — the cheaper the license, the easier it is to breach without noticing. That asymmetry is Oracle's playbook, and it is why an evidence-based review of license type pays for itself.
Direct answer: Check the Order Form and the licensed program name. ASFU and ESL lines name the specific application or carry an "Application Specific Full Use" or "Embedded" designation, and support often routes through the vendor. Full Use lines name the Oracle product alone, sit under your own Oracle Master Agreement, and use Oracle's standard list metrics.
The authoritative source is always the contract, not the install. Pull every Oracle Order Form and look at three things. First, the program description: a Full Use line reads "Oracle Database Enterprise Edition — Processor," while an ASFU line ties the product to a named application or carries an ASFU marker. Second, the seller: Full Use comes from Oracle on your OMA; ASFU and ESL come through a partner. Third, the support contract and CSI: if your support flows through the application vendor rather than Oracle directly, you are almost certainly on ASFU or embedded terms.
Where the paperwork is missing — common after acquisitions, vendor changes, or a decade of staff turnover — reconstruct the position from the application landscape. Any database that exists solely to run one purchased application is a candidate for ASFU; any Oracle instance you cannot directly administer because it is wrapped in an appliance is a candidate for ESL. Getting this right before Oracle does is the entire point of a forensic, evidence-based license review, and it is the foundation of every successful Oracle audit defense engagement.
Direct answer: Yes — Oracle allows ASFU licenses to be traded up to Full Use, but you pay the difference between the discounted ASFU value and the equivalent Full Use list price, plus the support uplift. Oracle frequently raises this trade-up during audits, treating any out-of-scope ASFU use as requiring Full Use coverage.
A trade-up is the legitimate path when your needs outgrow the ASFU restriction — for example, when you want to consolidate several applications onto one database or open the data to enterprise reporting. Oracle credits the value already paid for the ASFU license against the Full Use price and you settle the gap. The mechanics are straightforward; the economics are where buyers lose money, because Oracle controls both the credit it applies and the list price it charges, and rarely volunteers the most favorable framing.
The dangerous version of this conversation happens during an audit. When Oracle finds an ASFU database serving more than its named application, it does not offer a tidy trade-up — it quotes the full Full Use back-license value plus back-support, often with limited credit for the ASFU spend. This is negotiable, but only with evidence and leverage. Knowing the prior ASFU investment, the actual usage history, and Oracle's own trade-up policies turns a punitive claim into a managed commercial negotiation. That is core to our Oracle contract negotiation work, and you can see the financial swing in our client case studies.
Direct answer: The dominant risk is scope creep. ASFU and ESL grants are confined to one application, yet customers routinely connect reporting tools, build integrations, or reuse the database for a second system. Oracle treats every out-of-scope use as unlicensed and quotes the Full Use back-license value — one of the most expensive findings in an Oracle audit.
Across our engagements, roughly 1 in 3 enterprises running an ASFU-licensed application has at least one out-of-scope connection (Oracle Licensing Experts engagement data, 2026). The patterns repeat: a BI tool pointed at the application database for "just a few reports," an integration that reads ASFU data into a separate platform, a test or DR copy quietly serving a different purpose, or an embedded database opened up for direct queries after a vendor migration. None of these throw an error. All of them are unlicensed under ASFU or ESL terms.
The defensible position is built before Oracle calls. Document exactly which application each ASFU license serves, lock down direct connections to embedded databases, and challenge any audit finding that treats incidental or in-application use as a separate workload. Oracle's audit scripts measure what is installed and connected — they do not interpret your contract for you, and they do not distinguish licensed use from out-of-scope use. That interpretation is where claims are won or lost. To pressure-test your own estate before an audit notice arrives, start with a confidential Oracle compliance review, and read more tactics on the Oracle Licensing Experts blog.
We map every database to its license type, find the out-of-scope connections, and build the evidence to defend or right-size before Oracle audits. Talk to a former Oracle insider.
Oracle sells software under three license types: Full Use, which grants unrestricted use for any application; Application Specific Full Use (ASFU), which restricts the software to one named third-party application at a discount; and Embedded Software License (ESL), where Oracle runs hidden inside a vendor's product and the customer has no direct access. Price falls and restrictions tighten from Full Use to ESL.
Yes. ASFU licenses typically price at 30–60% of the equivalent Full Use list value (Oracle Licensing Experts benchmark, 2026). The discount exists because the license may only be used with one named third-party application. The moment the database serves any other workload, Oracle treats the use as requiring Full Use coverage and the discount disappears.
Not without breaching the license. ASFU permits only the single named application. Connecting a BI tool, building a custom integration, or loading the data into a separate warehouse is out-of-scope use. The database keeps working, but Oracle treats every external connection as unlicensed and prices remediation at Full Use rates during an audit.
Usually not. ASFU and ESL support commonly routes through the application or appliance vendor rather than Oracle directly, because the vendor owns the Oracle relationship. This can complicate patching, version upgrades, and escalation. Oracle Enterprise Support is still calculated at 22% of net license value per year (Oracle Technology Price List, 2026), but you may not deal with Oracle at all.
Check your Oracle Order Forms. ASFU and ESL lines name the specific application or carry an "Application Specific Full Use" or "Embedded" designation, and support often flows through the vendor. Full Use lines name the Oracle product alone, sit under your own Oracle Master Agreement, and use standard list metrics such as Processor or Named User Plus.
No. An Embedded Software License gives the customer no right to administer or query the Oracle database directly. The software is locked behind the vendor's application. Logging in to run queries, add schemas, or connect external tools steps outside the embedded grant and creates a Full Use exposure that Oracle can claim during an audit.
Oracle prices the out-of-scope use at the Full Use back-license value, often adding back-support and limited credit for the original ASFU spend. The claim is negotiable with evidence of actual usage, prior investment, and Oracle's own trade-up policies. Independent, buyer-side audit defense routinely reduces these claims well below Oracle's opening position.
Audit alerts, license-type traps, ASFU scope findings, and negotiation tactics from former Oracle insiders. Corporate email required.
Written by the Oracle Licensing Experts Team — former Oracle executives, LMS auditors, and contract managers with 25+ years of combined Oracle licensing experience. Not affiliated with Oracle Corporation. All advisory is independent and 100% buyer-side.