WebCenter Content, Portal and Sites are separate products from separate acquisitions, priced from $100,000 to $172,500 per processor. How each one licenses, and where buyers pay for the module they never deployed.
Oracle WebCenter is not one product. It is three unrelated products under one brand, bought from three different companies, licensed separately and priced between $100,000 and $172,500 per processor. Most WebCenter overspend starts with a buyer who did not know that.
This guide is for the estate owner and the procurement lead who have to agree one WebCenter number. Read it with the Oracle middleware licensing guide and the Oracle practice page, and with the WebLogic support tiers guide for the layer underneath.
WebCenter is a brand applied to three products with different jobs, different origins and different prices. A license for one of them confers no right to run the others.
That history is not trivia. It explains why the three carry different metrics, different minimums and prices that do not line up, and why an enterprise agreement written around one of them says nothing useful about the others.
Several smaller products sit around the three main ones and are licensed separately. They are the usual source of a surprise line on a quotation.
The brand on the login page is not evidence. Three checks settle it quickly, and all three produce artifacts you can put in front of an auditor.
Run all three and reconcile them. Where the three disagree, the disagreement itself is the finding, and it is better discovered by you than declared by an audit script.
The classic sequence is that finance buys Content for records management, the marketing team later needs a public website, and someone installs Sites because it is in the same download and carries the same brand. Nothing in the installer stops them.
Twelve months later the estate is running a product it never licensed, at $100,000 per processor list, and the discovery usually happens during an audit rather than during a budget round.
Each WebCenter product is licensed on Processor or on Named User Plus, and the Named User Plus minimum is 25 per processor. That minimum is the number that decides which metric is even available to you.
Oracle WebCenter list prices and the Named User Plus floor
| Product | List per processor | List per Named User Plus | Minimum users per processor | What it does |
|---|---|---|---|---|
| WebCenter Content | $172,500 | $3,450 | 25 | Document and records management repository |
| WebCenter Portal | $125,000 | $2,500 | 25 | Portal and composite application framework |
| WebCenter Sites | $100,000 | $2,000 | 25 | Web experience and marketing site management |
| WebCenter Sites Satellite Server | $25,000 | $500 | 25 | Caching and delivery tier for Sites |
| WebCenter Imaging | $57,500 | $1,150 | 25 | Invoice and document imaging |
Check the figures against the current Oracle Technology Global Price List before you build a case on them. Oracle revises that document, and the version you were quoted from matters.
Every WebCenter product prices a Named User Plus at one fiftieth of a Processor. That single ratio gives you the break even without a spreadsheet: 50 named users per processor.
Work an example. Four processors of WebCenter Content is $690,000 at list. The same four processors on Named User Plus with the 100 user minimum is $345,000, and the two positions meet at exactly 200 named users.
On your own hardware, licensable processors are physical cores multiplied by the factor for your chip in Oracle's Processor Core Factor Table. Most x86 cores carry 0.5.
In an Authorized Cloud Environment the core factor does not apply and two vCPUs count as one processor. At $172,500 per processor, that difference is not a rounding error, and it is worth modeling before any WebCenter workload moves.
It includes a restricted use WebLogic Server license that may run WebCenter and nothing else. That grant is not a general application server entitlement, and it does not travel to other workloads.
Three things break it: deploying a second application into the WebCenter domain, folding the WebCenter domain into a shared cluster, and reusing the WebCenter build as a golden image. Each converts a bundled right into a full use WebLogic requirement on the affected processors, priced from the WebLogic editions upward.
It costs the license on the counted processors, plus 22 percent of that net figure every year, plus the same again for every module you hold but do not run. The third term is the one that goes unmeasured.
Eight processors of WebCenter, three positions, list prices over three years
| Position | License at list | Support per year | Three year total |
|---|---|---|---|
| Content only, the module actually running | $1,380,000 | $303,600 | $2,290,800 |
| Content plus Portal, one of them idle | $2,380,000 | $523,600 | $3,950,800 |
| Content, Portal and Sites, two idle | $3,180,000 | $699,600 | $5,278,800 |
The idle modules in rows two and three cost $1.66M and $2.99M over three years. Nothing is being used, nothing is being upgraded, and the support line renews on schedule.
White Paper · Oracle Middleware
Oracle Fusion Middleware Licensing
WebLogic, SOA and Coherence, priced. Read it free.
Oracle does not accept most virtualization as a licensing boundary, so it may count the cores in the wider cluster rather than the cores assigned to the WebCenter virtual machines. At $172,500 per processor that position is expensive to lose.
Oracle's partitioning policy treats most hypervisor level controls as soft partitioning, which it does not accept as limiting. Only the methods it lists as hard partitioning cap the count.
The Oracle virtualization licensing guide covers the current position across VMware, Nutanix and the rest. Read it before you agree a WebCenter count on virtual infrastructure.
You defend it with a component map and a host map, both dated and both produced before the audit letter arrives. The component map names every WebCenter module running and the hosts it runs on. The host map names the cores and how they are contained.
Your Oracle ordering documents define the grant you are evidencing against. Read the actual order, not the sales summary, because the module names on the order are the only ones that count.
WebCenter runs on the Fusion Middleware clock, and Fusion Middleware 12c leaves Premier Support in December 2026 and Extended Support in December 2027. Oracle publishes both dates on its Fusion Middleware end of support page.
Extended Support here is one year, not the three the Lifetime Support Policy describes as typical. A WebCenter estate that plans a two year upgrade program is planning to spend part of it on Sustaining Support.
Sustaining Support costs the same as Premier and delivers no new fixes, no new security alerts and no new certifications. For a content repository holding regulated records, that combination is a control failure waiting to be written up.
Older WebCenter Portal releases are already there. The 11g line left Extended Support years ago, so any 11g Portal instance still running is on Sustaining Support today, at full price.
Not every Fusion Middleware 12c product carries forward into every later release at the same pace. WebCenter Content has a 14.1.2 release. Ask Oracle in writing whether your specific module and version do, before you fund an upgrade project.
The answer changes the plan entirely. An upgrade is a project. A product without a forward release is a migration, and migrations need a different budget, a different timeline and a different negotiating posture.
Align every license line to a module that is actually running on a host you can name, then challenge the count on everything else. On WebCenter list prices, one corrected processor is worth more than most discount negotiations.
The standard pitch is that a WebCenter suite or multi module position is the efficient buy, because Content, Portal and Sites work better together and the bundle discount is generous. We disagree, and the numbers above are why. In roughly 3 of every 5 WebCenter estates we benchmarked, only one module ever ran in production, so the bundle added 40 to 55 percent shelfware and then charged 22 percent a year on it. A bundle discount on a module you never deploy is not a saving, it is a subscription to an idea. The buyer side move is to license the module you deploy, negotiate the others as priced options with a fixed price and a defined window, and exercise them only when a project is funded and scheduled. Integration is a deployment decision. It is not a reason to carry two products you cannot point at in production.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
WebCenter is rarely one product on one server. It is three unrelated products with separate prices, running on a restricted use application server, on hardware with a core factor. Price each layer, not the brochure.
If Coherence caches sit behind the WebCenter tier, the Coherence licensing guide covers how those nodes are counted. It is the other product in this stack that is routinely deployed without a line on an order.
Each WebCenter product is licensed separately, on either the Processor metric or Named User Plus, with a minimum of 25 Named User Plus per processor. Processor counts are physical cores multiplied by the Oracle core factor on your own hardware, and vCPUs divided by two in an Authorized Cloud Environment.
WebCenter Content for document and records management, WebCenter Portal for portals and composite applications, and WebCenter Sites for marketing and web experience management. They came into Oracle through separate acquisitions, they are priced separately, and owning one grants no right to run another.
At list, WebCenter Content is $172,500 per processor, WebCenter Portal is $125,000 and WebCenter Sites is $100,000, with Sites Satellite Server at $25,000 and WebCenter Imaging at $57,500. Support adds 22 percent of the net license fee every year, uplifted annually. Verify the figures against the current Oracle Technology Global Price List before you model them.
Below 50 named users per processor, because every WebCenter product prices a Named User Plus at one fiftieth of a Processor. The 25 per processor minimum sets the floor, so the metric is genuinely advantageous between 25 and 50 users per processor. Above 50, or for anything reachable by the public, Processor is the only sensible answer.
It includes a restricted use WebLogic Server license that may run WebCenter and nothing else. Deploying another application into that domain, folding it into a shared cluster, or reusing the build as a golden image all require full use WebLogic licenses for the affected processors.
Yes. Oracle's partitioning policy treats most hypervisor controls as soft partitioning and does not accept them as limiting, so Oracle may count the wider cluster rather than the virtual machines running WebCenter. Only the specific hard partitioning methods named in the policy cap the count, and you need dated evidence that they were configured as described.
WebCenter follows the Fusion Middleware lifecycle, and Fusion Middleware 12c leaves Premier Support in December 2026 and Extended Support in December 2027. That is one year of Extended cover rather than the usual three. Older 11g WebCenter Portal releases are already on Sustaining Support, which costs the same as Premier and delivers no new fixes or security alerts.
Match every licensed module to a module actually running on a named host, then terminate support on the rest after modeling the residual invoice. Recount processors from the deployment rather than the cluster.
Then test each module against the 50 users per processor break even. On WebCenter list prices, one corrected processor is usually worth more than the discount you were arguing about.
The middleware layer is licensed like the database, per processor with the core factor, but the bundles pull you up to the $120,000 Suite. The edition ladder and how to license to need.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
WebCenter is rarely one product on one server. It is three products with separate metrics, running on WebLogic, on hardware with a core factor.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle renewal moves, middleware licensing, ULA posture, and the buyer side moves we are running in client engagements.
