The Oracle price list, one PDF and the clauses behind it
Oracle publishes the Technology Global Price List as one PDF, effective April 16, 2026: Database Enterprise Edition at $47,500 per Processor, WebLogic Suite at $45,000, SOA Suite at $57,500. What decides your bill is not the headline rates but the floors, the middleware lines nobody reads, and the support clauses that make the number permanent.
Prepared by Redress Compliance · August 6, 2026 · Oracle advisory. Based on 60 to 80 quotes, renewal packs, and settlement models worked 2024 to 2026.
Executive summary
The crossover is built into every line. Every Database line prices Named User Plus at exactly one fiftieth of the Processor price, $950 against $47,500 on Enterprise Edition, so the Processor metric wins the moment you pass 50 real users per Processor.
Underneath sit the floors: 25 Named User Plus per Processor on EE, 10 per server on SE2, and you license the higher of the floor and your real headcount.
Support makes the discount point worth double. Support is 22 percent of net license fees, not list, so one dollar off the net license is worth about $2.10 across a five year hold: the license saving plus five years of support the discount never generates.
That multiplier is the real return on every negotiated point, and it is why the discount line deserves more scrutiny than any other number in the approval pack.
The clauses make the number permanent. Matching Service Levels blocks de-supporting part of a license set, and the repricing clause means dropping 37.5 percent of an estate can cut the support bill by nothing at all.
Oracle publishes no discount schedule and no cap on the annual support increase, and the one published mechanism that reduces a technology support bill is Support Rewards, at 25 or 33 cents per OCI dollar.
The quotes fail on the multiplier, not the rate. Across our 60 to 80 quote and renewal reviews, the discount line was the only number in the approval pack, while the Processor count after core factor, which multiplies every other figure, was almost never restated or verified by the buyer.
The price list is arithmetic; the bill is the inputs, and the inputs are yours to check.
Reading the list, the lines that carry estates
| Line | Per Processor | Per Named User Plus | The note |
|---|---|---|---|
| Database Enterprise Edition | $47,500 | $950, 25 per Processor floor | The anchor line, multiplied by cores after the core factor |
| Database Standard Edition 2 | $17,500 per socket | 10 per server floor | The fenced alternative one in three EE estates should be on |
| WebLogic Suite | $45,000 | The one fiftieth ratio holds | The middleware line HA architectures quietly require |
| SOA Suite | $57,500 | The ratio holds | The integration line nobody restates until the audit does |
| Options and packs | Each its own line | Each with the same ratio | Metering silently under the editions, per the pack rules |
The one fiftieth ratio is the metric decision, pre-made. Oracle prices Named User Plus at exactly one fiftieth of Processor on every Database line, so the crossover is always 50 real users per Processor, floors permitting.
There is no per product judgment call to make: count the users, count the processors after core factor, and the metric picks itself.
The support math, where the list becomes permanent
The 22 percent runs on net license fees, which cuts both ways: discounts propagate into the support stream, one dollar off net worth $2.10 over five years, and the stream itself then compounds at an uncapped annual increase Oracle publishes no schedule for.
The clauses around it are the system the support drop guide works in full: Matching Service Levels binding the license set, the repricing clause repricing survivors of any partial reduction, and the 150 percent reinstatement taxing every round trip.
The worked consequence deserves restating: dropping 37.5 percent of an estate can cut the support bill by nothing, because the survivors reprice at the smaller volume's discount with a floor.
The published exceptions are two: third party support, which leaves the system entirely, and Support Rewards, 25 cents per OCI dollar, 33 with a ULA, the one mechanism Oracle itself publishes for reducing a technology support bill.
The Oracle CIO complete playbook
The estate strategy the price list plugs into: the metric and edition decisions, the discount propagation math, the support clause system, and the negotiation sequence across the Oracle relationship.
Get the white paper →How quotes actually fail, the multiplier problem
Across the 60 to 80 quotes, renewal packs, and settlement models we worked through, the approval pack pathology was consistent: the discount percentage was the only number anyone examined, while the quantities it multiplied went unverified.
The Processor count after core factor multiplies every figure on the quote, and it was almost never restated by the buyer: the count arrived from Oracle's assumptions about cores, virtualization boundaries, and minimums, and the discount negotiated hard against a base nobody had checked.
The correction order is fixed: quantities first, the counting rules of the database licensing guide applied to your actual estate, then the metric per the one fiftieth ratio, then the edition fit, and the discount last, where its $2.10 multiplier finally lands on an honest base.
A deep discount on an inflated count is the most expensive bargain in enterprise software.
- 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 the quote reviews showed, 2024 to 2026
The discount line, negotiated hard, while the multiplying quantities passed unverified from Oracle's assumptions.
The five year worth of one net license dollar, the reason discount points outvalue most concessions traded for them.
The third pattern was the middleware blind spot: WebLogic and SOA lines entering estates through architecture decisions, HA topologies and integration layers, without ever passing through a procurement review, then surfacing at audit prices.
The price list is public and stable; the estates that use it as a checklist, line by line against what actually runs, meet their quotes prepared, and the rest meet them surprised.
Your first five moves
- Restate the quantities on every quote: Processors after core factor, virtualization boundaries applied, floors checked, before any rate conversation.
- Let the one fiftieth ratio pick the metric, per database, at the real user count against the floors.
- Price every discount point at $2.10 and trade accordingly; the support stream is where the negotiation's value actually compounds.
- Map the middleware lines to the architecture, WebLogic and SOA especially, before the audit maps them for you.
- Model the support clauses before any reduction, Matching Service Levels and repricing first, with Support Rewards and third party support as the published exits. The Oracle practice and audit defense services run the list with you.
Frequently asked questions
What does Oracle Database Enterprise Edition cost per processor?
On the Technology Global Price List effective April 16, 2026, Enterprise Edition lists at $47,500 per Processor and $950 per Named User Plus, with a 25 NUP per Processor floor. The Processor count runs cores times the core factor, which is the multiplier every quote review should restate first.
When should we license per Processor versus Named User Plus?
The list decides it: every Database line prices NUP at exactly one fiftieth of the Processor price, so Processor wins past 50 real users per Processor, and NUP below it, subject to the floors of 25 per Processor on EE and 10 per server on SE2. You license the higher of the floor and the real count.
How much is an Oracle discount point actually worth?
About $2.10 per dollar across a five year hold: support runs 22 percent of net license fees, so a dollar off net saves the dollar plus roughly five years of support it never generates. That multiplier makes license discount points more valuable than most concessions traded against them.
Can we reduce Oracle support costs by dropping part of the estate?
Often not: Matching Service Levels blocks de supporting part of a license set, and the repricing clause reprices the survivors at the smaller volume's discount with a floor, so dropping 37.5 percent of an estate can cut the bill by nothing.
The published reducers are Support Rewards, at 25 or 33 cents per OCI dollar, and leaving for third party support entirely.
Does Oracle publish discount levels or support caps?
Neither: no discount schedule exists, and no cap on the annual support increase is published. Discounts are negotiated deal by deal against benchmarks, and support caps exist only where buyers write them into ordering documents, which is precisely why both belong in every negotiation.
Why do middleware lines like WebLogic surprise estates?
They enter through architecture rather than procurement: HA topologies requiring full use WebLogic, integration layers pulling SOA Suite, none of it passing a purchasing review until an audit prices it at list, $45,000 and $57,500 per Processor respectively.
Mapping the middleware lines to the running architecture is the prevention.
