Oracle ASFU — Application Specific Full Use — is a restricted-use license that lets you run Oracle technology only with a specific third-party (ISV) application, at a lower price than Full Use. It permits the same technical features as Full Use but legally confines them to the named application; the moment you use the database for anything else, you breach the grant. ASFU and the related Embedded (ESL) license can cost 40–70% less than Full Use, which makes them attractive — and makes the migration trap, where buyers later repurpose an ASFU database, one of the most expensive Oracle audit findings we see. This article explains what each grant permits and when to choose which.
An ASFU license is Oracle technology (typically Database or specific options) sold by or alongside an independent software vendor's application, licensed for use only with that application. It is "full use" in the technical sense — you get the complete product, not a cut-down edition — but "application specific" in the legal sense, because the grant is contractually limited to the ISV solution it was bought for. You buy ASFU when your Oracle footprint exists purely to run a packaged third-party product and you have no intention of using the database for anything else.
The discount exists because Oracle is trading scope for volume: by restricting what you can do, Oracle can price below the Full Use list and still capture the ISV channel. That trade is genuinely good value — provided your usage stays inside the box. It is the staying-inside-the-box part that the audit team watches.
Three grant types come up in ISV-driven Oracle estates, and conflating them is where buyers lose money. Full Use is unrestricted. ASFU is restricted to a named application but still visible to you as a normal Oracle license you administer. Embedded (ESL) is a more deeply restricted, often "black-box" license where the ISV embeds Oracle and you may not even administer it directly. The comparison table below is the one we hand clients.
| Dimension | Full Use | ASFU | Embedded (ESL) |
|---|---|---|---|
| Use scope | Any application | One named ISV application | One ISV application, often black-box |
| Relative cost | Baseline (highest) | ≈30–60% of Full Use | Lowest; bundled into ISV price |
| Who administers it | You | You | Usually the ISV |
| Can you add other apps? | Yes | No — breach | No — breach |
| Convertible to Full Use? | n/a | Yes, by paying the uplift | Sometimes; negotiated |
| Support | Oracle direct | Oracle or via ISV | Via ISV |
Relative cost ranges are indicative; actual ASFU pricing is set by the ISV's agreement with Oracle. Always verify the specific ordering document.
We map ISV-embedded Oracle estates and the conversion exposure inside them. Scoping calls are no-obligation.
The trap is repurposing. An ASFU database bought to run, say, a banking or hospital application gets quietly extended — a team builds a reporting layer on it, a second application is pointed at it, or a developer uses the spare capacity for an unrelated project. Every one of those steps takes the database outside the ASFU grant and into unlicensed Full Use territory. Because ASFU is technically identical to Full Use, nothing breaks and nothing warns you; the breach is invisible until Oracle's LMS team reads the contract during an audit and reprices the entire footprint at Full Use rates, often with back support.
We see this most often after consolidation, virtualization, or a cloud migration that mixes ASFU and Full Use workloads on shared infrastructure. The defensible position is to inventory every ISV-linked Oracle license, tag it ASFU/Embedded/Full Use, and enforce a hard rule that ASFU databases run their named application and nothing else. When a repurposing finding has already surfaced, that inventory becomes the backbone of Oracle audit defense, capping the claim at the workloads that genuinely stepped outside the grant. The audit mechanics behind these claims are detailed in Oracle LMS tactics and the broader response framework in Oracle audit defense.
Our framework for Oracle licensing, audit defence and conversion negotiations.
Choose ASFU when three conditions hold: your Oracle footprint exists solely to run a packaged ISV application, you are confident that will not change over the contract term, and the ISV's ASFU pricing is materially below Full Use. Choose Full Use when you expect to extend the database, run multiple applications, or want freedom to repurpose capacity later. The decision is really about optionality — ASFU trades future flexibility for present discount, so the right answer depends on how stable your architecture genuinely is.
That last point is the one buyers skip. Fixing the conversion uplift at purchase converts a future audit landmine into a known, budgeted option. It also relates directly to how unlimited agreements are structured — if you are weighing broad Oracle flexibility, compare the PULA vs ULA options and the Oracle license cost baseline before committing to a restricted grant.
ASFU can be a powerful cost lever — it is one of the few legitimate ways to run full-featured Oracle technology well below Full Use list — but only if it is governed. An unmanaged ASFU estate is a liability dressed as a saving. In our license-optimization work we treat ASFU databases as a distinct, ring-fenced category: inventoried, tagged, monitored for scope creep, and excluded from the general capacity pool that other workloads draw on. Cross-vendor, the same ring-fencing discipline applies to restricted SAP grants — see our companion guidance on SAP license optimization.
Weekly compliance intelligence for IT leaders.
