Oracle ASFU license, the 2026 buyer side guide.

Oracle ASFU is a narrow scope Oracle Database or Middleware license granted at a discount to ISV partners for embedded use only. The audit risk lives in the gap between the use case the ISV sold and the use case the enterprise actually runs.

Read this alongside the Oracle Knowledge Hub, the Oracle ULA framework, and the full license type reference. The ASFU license type predates Oracle Cloud. The terms have aged. The audit risk has not.

This guide walks through what ASFU actually is, the coverage rules that determine scope, the price and metric math, the audit triggers that LMS chases, and the buyer side moves before and during the next Oracle engagement.

What ASFU actually is

ASFU is a license type Oracle grants to ISV partners under a Full Use Distribution Agreement. The ISV bundles the Oracle Database or Middleware binary with their own software, ships the bundle to the end customer, and Oracle invoices the ISV at the ASFU price. The end customer holds the use right inside the four corners of the ISV application.

A short history

The ASFU program traces back to the late 1990s when Oracle sought broader Database distribution through application partners. The intent was a defensible price point that respected the partner relationship. The terms have shifted incrementally over twenty years. The core construct has not.

• Origin. Late 1990s ISV embedding program.
• Intent. Broader Database distribution through application partners.
• Construct. Discounted license, scope tied to the named ISV application.

The paper trail

ASFU sits on three documents. The Oracle Full Use Distribution Agreement governs the ISV. The end customer order document references the ISV agreement. The end customer signs an Oracle ordering document that bakes the scope language. Read every page. Scope language varies.

• FUDA. Oracle to ISV agreement, not visible to most buyers.
• End customer order. References FUDA scope.
• Definitions exhibit. The actual scope language sits here.

Coverage and restrictions

ASFU coverage starts narrow and stays narrow. The named ISV application is the only software allowed to interact with the licensed Oracle component. Anything that reads, writes, or replicates outside that boundary is out of scope unless the ISV agreement explicitly permits it.

What ASFU typically allows

The ISV application reading and writing the Oracle Database. The ISV native reports. Backup, restore, and disaster recovery for the ISV workload. Patching the Oracle product under standard support terms.

• ISV application access. The point of the license.
• Native ISV reports. Reports the ISV ships and supports.
• Backup and DR. Standard data protection for the ISV workload.
• Patching and support. Under the standard Oracle support agreement.

What ASFU typically blocks

Direct end user query access outside the ISV application. Custom reports built outside the ISV stack. Third party integration tools writing to the database. Use of the same database instance for non ISV workloads. Schema extensions that support use cases the ISV did not sell.

• Direct query access. Power users running SQL outside the ISV application.
• Custom external reports. Anything written outside the ISV native stack.
• Third party integrations. ETL tools, BI tools, replication agents.
• Workload sharing. Non ISV workloads sharing the licensed instance.
• Schema sprawl. Custom tables that support out of scope use cases.

License metrics and pricing

ASFU uses the same license metrics as Full Use Oracle products. Processor and Named User Plus are the dominant pair. Pricing is the ISV negotiated discount off Oracle Technology Global Price List. The discount range is the part that varies most.

Metric mechanics

Processor metric uses the standard Oracle Core Factor table. Named User Plus uses the standard per user definition with the Oracle minimum applied. ASFU does not change the metric definitions. It only changes the price and the scope.

• Processor. Standard Core Factor multiplier.
• Named User Plus. Standard per user count and minimum.
• Minimums. Same minimums as Full Use unless explicitly waived.

License metric reconciliation is where the ASFU audit conversation starts. Document the deployed footprint before LMS does.

Audit risks and triggers

Oracle License Management Services treats ASFU as a high yield audit target. The reason is structural. Scope is narrow. Customer practice drifts. The audit converts the drift into license demand.

The five recurring triggers

The same five drift patterns appear across most ASFU audits. Custom reports outside the ISV stack. Third party integration tools. Use case expansion after deployment. Workload sharing on the licensed instance. M&A driven extension into new business lines.

• Custom external reports. Power BI, Tableau, or homegrown reporting.
• Integration tools. Informatica, Talend, Fivetran, Kafka connectors.
• Use case expansion. A new department starts using the application.
• Workload sharing. A non ISV workload on the same database instance.
• M&A extension. An acquired entity gets onboarded onto the ASFU stack.

What LMS will request

LMS requests an inventory of every Oracle Database and Middleware instance, the ASFU agreement references, the use case scope statement, and the network topology that touches each instance. The buyer side artifact set must match.

• Instance inventory. Every Oracle Database and Middleware install.
• Agreement references. Per instance ASFU contract pointer.
• Use case scope statement. One paragraph per ASFU agreement.
• Network topology. What connects to each instance and from where.

ISV partner posture

The ISV partner is the unseen third party in every ASFU audit conversation. The ISV negotiated the FUDA. The ISV defines the application boundary. The ISV often holds the scope clarification that decides the audit outcome.

Posture varies by partner

Some ISVs negotiate broad scope language that helps the end customer in audits. Others ship the bare minimum scope that satisfies Oracle and leaves the end customer exposed. The buyer side stance is to ask the ISV for the scope language before signing.

• Broad scope ISV. Negotiated extension to standard reporting tools.
• Narrow scope ISV. ISV application native access only.
• Co terminus ISV. Scope follows the ISV product roadmap.

“The cheapest ASFU on day one becomes the most expensive ASFU on audit day. Read the scope language. Read the FUDA reference. Read what the ISV actually negotiated.”

Conversion paths

Three conversion paths exist when scope no longer fits. Buy additional Full Use licenses to cover the out of scope workload. Convert the entire ASFU footprint to Full Use through Oracle. Migrate the out of scope workload to a separate database instance.

Comparing the three paths

Path A adds Full Use licenses for the delta. Path B retires the ASFU and replaces with Full Use. Path C keeps the ASFU clean and stands up a new licensed instance.

• Path A. Add Full Use licenses for the delta workload only.
• Path B. Convert ASFU to Full Use across the whole footprint.
• Path C. Stand up a separate Full Use instance for the new workload.

Economics

Path A is usually cheapest if the delta is small. Path B is usually most expensive and rarely favors the buyer. Path C trades license cost against operational complexity. The right answer depends on the workload, the use case, and the renewal timing.

• Path A cost driver. Size of the out of scope workload.
• Path B cost driver. Full Use list price minus an ASFU credit at Oracle’s discretion.
• Path C cost driver. Hardware, support, and ops cost of a second instance.

What to do next

1. Build the ASFU register with every Oracle Database and Middleware instance.
2. Document the named ISV application and the use case scope per instance.
3. Map every connecting tool, integration, and external report to the right instance.
4. Flag every workload that may sit outside the ISV scope.
5. Engage the ISV for scope clarification on flagged workloads.
6. Model conversion paths before any Oracle conversation begins.
7. Set a quarterly review cadence on the ASFU register.
8. Contact Redress Compliance to scope an ASFU readiness review.

Frequently asked questions

What does ASFU stand for and what is it?

ASFU stands for Application Specific Full Use. ASFU is an Oracle Database or Middleware license granted at a discount to an Independent Software Vendor for resale embedded inside a named application. The end customer can use the Oracle product only with that named ISV application and only for the use cases the ISV ships.

How is ASFU different from a Full Use license?

Full Use grants the right to use the Oracle product across any workload subject to the standard Oracle terms. ASFU restricts use to the named ISV application and the use cases that ISV application supports. Any workload outside that scope needs a separate Full Use license at the standard list price.

What is the typical ASFU discount?

ASFU discounts on Oracle Database Enterprise Edition typically run 50 to 80 percent off the Full Use list price, depending on the ISV deal terms. The discount reflects the narrowed scope and the fact that the ISV is responsible for the sale and the support relationship.

What are the most common audit triggers on ASFU?

Custom reports built outside the ISV application that read directly from the ASFU database. Third party integration tools writing into the ASFU database. New use cases adopted after the original deployment. M&A activity where the buyer extends database use beyond the original ISV scope.

Can ASFU be converted to Full Use?

Yes. Oracle will price a conversion, typically as a credit of the original ASFU spend against a Full Use purchase at then current list. The conversion math rarely favors the buyer. The buyer side stance is to validate every alternative before accepting the Oracle conversion quote.

How should we document ASFU compliance?

Maintain a per ISV register that captures the named application, the ASFU agreement reference, the licensed metric and quantity, the deployed footprint, and a use case scope statement. The register is the first artifact Oracle License Management Services will request in an audit.