The ASFU license, full use of the program and none of the estate
Application Specific Full Use licensing trades scope for price: full use of the Oracle program, but only inside the one application it was bundled with, and Oracle audits exactly where that boundary is crossed. Not one of the findings we defended began with somebody deciding to break a license; they began with a reporting request nobody checked against the ordering document.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 20 to 30 ASFU reviews defended 2024 to 2025.
Executive summary
The discount is real and unpublished. Full Use Enterprise Edition lists at $47,500 per Processor; Oracle publishes no ASFU rate card, and the band we observe on ISV quotes runs 30 to 50 percent below the Full Use list line. The worked case: 32 x86 cores at the 0.5 factor is 16 Processor licenses, $760,000 at Full Use list against $380,000 to $532,000 under the observed ASFU band. The grant lives on one or two lines of the ordering document, and those lines get read first.
The boundary breaks by accident, and the packs break it silently. A BI or analytics connection broke the grant in 30 to 40 percent of our reviews, integration and ETL layers most of the rest, and in 50 to 70 percent the management packs were already recording usage because CONTROL_MANAGEMENT_PACK_ACCESS ships defaulted to DIAGNOSTIC+TUNING on Enterprise Edition, a $200,000 exposure on the worked example's 16 licenses for options never printed on the order.
Conversion is arithmetic Oracle runs after the finding. The opening conversion demand in the worked example was $1,094,400, 2.4 times the original ASFU fee, with support stepping up $66,880 a year and staying there, and openings across the file ran 2 to 3x. Settlements landed well under the openings, but only where the customer produced a connection inventory inside the first two weeks.
Three events break the boundary for you. The ISV disappears, an acquisition consolidates the database into a wider estate, or the application moves to AWS or Azure, where the core factor stops applying and the license count doubles. Two protections belong in the original paper: a capped conversion price to Full Use, asked for at first purchase or never, and the Customer Support Identifier in your own name rather than the ISV's, because patch access dies with the ISV's Oracle relationship otherwise.
The six order fields that decide the exposure
| What to read | Where it sits | What it costs if missing or wrong |
|---|---|---|
| The named application | The program line: for use solely with the named ISV product | Every other use is unlicensed, priced at Full Use list, not your ASFU rate |
| The program list | One row per Oracle program on the order | Unlisted options are unlicensed: Diagnostics and Tuning alone are $200,000 on 16 licenses |
| Metric and quantity | Processor or NUP, with the counted number | An order sized to the ISV reference architecture leaves a shortfall the auditor finds first |
| The conversion price | Almost never present: asked for at first purchase | Without a cap, Oracle sets the number after it has the finding |
| The CSI owner | My Oracle Support, Support Identifiers | A CSI in the ISV's name ends your patch access when the ISV stops paying |
| Cloud and hosting rights | The ISV's distribution agreement, not your order | A move to EC2 or Azure without written confirmation exits the grant |
Where the boundary breaks, connection by connection
The grant permits everything a DBA does in support of the one named application, and nothing else: a second application, a report, a feed, or a replica each cross the line. The break arrives as ordinary work, a BI tool pointed at the database for reporting, an ETL layer feeding a warehouse, an integration ticket closed without anyone reading the order, and the packs compound it silently, because the Enterprise Edition default records Diagnostics and Tuning usage from first boot unless CONTROL_MANAGEMENT_PACK_ACCESS is set to NONE. The wider grant taxonomy, Full Use, ASFU, Embedded, and hosting, sits in the license types guide, priced against the technology price list.
The Oracle CIO complete playbook
The five year Oracle plan the ASFU estate sits inside: the grant map, the audit calendar, the conversion economics, and the contract levers that cap them.
Get the white paper →The three breaking events, and the paper that survives them
The ISV's disappearance ends the distribution relationship your license and patches ride on; an acquisition consolidates the ASFU database into an estate whose other uses void the grant; and a cloud migration exits it doubly, first because hosting rights live in the ISV's distribution agreement rather than your order, and second because the cloud counting rules drop the core factor, doubling the license count on the same workload. The protections are cheap exactly once: the capped conversion price written into the original order, and the CSI in your own name. Both cost nothing at first purchase and cannot be bought at the finding, which is when most buyers first look for them. The core factor arithmetic underneath both counts is its own discipline.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across ASFU reviews, 2024 to 2025
Across roughly 20 to 30 ASFU reviews Fredrik Filipsson defended in 2024 and 2025, no finding began with somebody deciding to break a license:
A reporting or analytics tool pointed at the ASFU database, with integration and ETL taking most of the rest.
$1,094,400 against the original ASFU fee, with support stepping up $66,880 a year and staying.
The defenses that worked were prepared, not argued: the connection inventory produced inside the first two weeks, which separated negotiated settlements from list price findings; the pack access parameter set deliberately rather than left at default; and the order lines read before the integration ticket closed rather than after the audit letter opened. ASFU remains the right choice for a self contained packaged application with no wider plans, because the discount is real and durable exactly as long as the boundary is.
Your first five moves
- Read the program line and the program list today, because the whole grant lives on one or two lines of the ordering document.
- Set CONTROL_MANAGEMENT_PACK_ACCESS deliberately on every ASFU database, because the Enterprise Edition default records options you do not own.
- Build the connection inventory now, every tool and feed touching the database, the artifact that separates settlements from findings.
- Get the CSI into your own name and the conversion cap into the paper, both cheap at purchase and unbuyable at the finding.
- Reprice the grant before any migration or acquisition, because the cloud doubles the count and consolidation voids the boundary. The Oracle practice runs the review with you.
Frequently asked questions
What is an Oracle ASFU license?
Application Specific Full Use: full use of the Oracle program, sold through a partner or ISV, restricted to the one named application on the ordering document. It carries your company name, your CSI, and your processor count, which is why Oracle audits you rather than the ISV, and the observed price band runs 30 to 50 percent below Full Use list.
How is ASFU different from an Embedded license?
By who touches the database: an ESL hides the database inside the partner product on the ISV's paper with no direct customer access, while ASFU puts the order on your paper with your DBAs administering it. If your DBAs log in, you received an ordering document, and the CSI is in your name, you are ASFU, whatever the ISV called it.
What breaks an ASFU license?
Any use beyond the named application: a second application, a report, a feed, or a replica. In our reviews a BI or analytics connection broke the grant in 30 to 40 percent of cases, integration and ETL layers most of the rest, and the management packs were already recording unlicensed usage in 50 to 70 percent because the Enterprise Edition default was never changed.
What does ASFU to Full Use conversion cost?
Oracle's opening demand ran 2 to 3 times the original ASFU fee, 2.4x in our worked example at $1,094,400, with support stepping up permanently. Settlements landed well below the openings, but only where the customer produced a connection inventory inside the first two weeks. A conversion cap negotiated at first purchase removes the arithmetic entirely.
Can an ASFU database move to the cloud?
Not without checking two documents: hosting and cloud rights live in the ISV's distribution agreement rather than your order, and the move to an Authorized Cloud Environment drops the core factor, doubling the license count on the same workload. Written confirmation before the migration is the difference between a move and a finding.
When is ASFU the right choice?
When a single packaged application runs on Oracle technology with no plan to use the database elsewhere: the 30 to 50 percent discount is real and durable for a self contained deployment. The exposure begins with wider plans, reporting, integration, consolidation, or cloud, which is why the boundary belongs in the architecture review, not just the contract file.
