Coherence is licensed per processor on every node that joins the cluster, including storage disabled members and proxies. The editions, the grid counting, and where the WebLogic Suite entitlement stops.
Oracle Coherence is licensed per processor on every node that runs it, and most estates do not know how many nodes that is. The bill is the whole grid, and the entitlement most buyers think they have, the Coherence inside WebLogic Suite, is narrower than the way they use it.
This guide is for the person who has to defend a Coherence number, not for the person who tunes the cache. Read it with the WebLogic support tiers guide, because the Suite entitlement is where most Coherence rights come from, and with the WebLogic cloud licensing guide if the grid is moving.
Coherence is licensed on the Processor metric, and the count covers every processor on which a Coherence cluster member runs. Oracle describes the product on its Coherence product page and lists the editions on the Coherence editions page.
If the process joins the cluster, it is a node, and the processor it runs on is licensable. That is a wider set than most inventories contain.
The storage disabled members are the line item that moves the number. In a typical WebLogic estate the application tier has more processors than the cache tier, so counting only the cache servers can understate the grid by more than half.
Ask the cluster, not the architects. Coherence reports its own membership, and that report is the same evidence Oracle's data collection will produce.
On premises, licensable processors are physical cores multiplied by the factor in Oracle's Processor Core Factor Table. Most x86 cores carry 0.5, so a 32 core grid is 16 processors.
In an Authorized Cloud Environment the core factor is expressly not applicable, and two vCPUs count as one processor where hyperthreading is on. Oracle sets that rule in its cloud licensing policy.
Work it through on the same hardware. The 32 cores that counted as 16 processors on premises are presented as 64 vCPUs in the cloud and count as 32 processors, which doubles the Coherence bill on a lift and shift with no change to the application.
Coherence ships in three server editions, and the boundary between Enterprise Edition and Grid Edition is where the money is. Enterprise Edition is what WebLogic Suite grants. Grid Edition is what a surprising number of deployments actually use.
The list prices below come from the Oracle Technology Global Price List, which is the only version of the number worth arguing from. Confirm the current edition of that document before you build a business case on it.
Coherence editions: capability and list price per processor
| Edition | List per processor | What it adds | What it will not do |
|---|---|---|---|
| Coherence Standard Edition | Entry level, well below Enterprise | Local, near and continuous query caches, replicated and partitioned data, read through and write through | Write behind caching, HTTP session management, clustered JMX, WAN |
| Coherence Enterprise Edition | $11,500 | Write behind caching, HTTP session management, clustered JMX, parallel invocation and query, resource adapter | Cross site federation, WAN, non Java real time clients |
| Coherence Grid Edition | $25,000 | Cross site and WAN data management, federated caching, cross platform real time clients in Java, .NET and C++ | Nothing above it, so this is the ceiling |
| Management Pack for Oracle Coherence | $3,500 | Enterprise Manager monitoring and diagnostics for the grid | Not included in any Coherence edition, and not included in WebLogic Suite |
Enterprise Edition is a full application data grid for a single site. It covers write behind caching, HTTP session management for application servers, clustered JMX management, parallel invocation and query, and the resource adapter integration.
For most WebLogic estates that is genuinely enough. A cache in front of a database, shared session state across a cluster, and a management view of the grid all sit inside it.
Grid Edition is about reach: across data centers and across languages. Three requirements pull a deployment into it, and each one is a design decision rather than a capacity decision.
Members of a single Coherence cluster must all run the same edition. Different editions can interoperate only across a Coherence*Extend boundary, never inside one cluster.
Follow that through. One requirement for a .NET real time client, or one federation link to a second site, does not upgrade one node. It upgrades every node in that cluster from Enterprise Edition to Grid Edition, at $13,500 per processor of extra list.
On a 24 processor grid that is $324,000 of license and about $71,000 a year of support, triggered by a design choice that was never priced. This is the single most common way a Coherence position goes wrong.
It stops at Enterprise Edition features, on the processors licensed for WebLogic Suite, inside the WebLogic deployment. Step past any one of those three and you need a Coherence license of your own.
WebLogic Suite bundles Oracle Coherence Enterprise Edition alongside WebLogic Server Enterprise Edition. At $45,000 per processor against $25,000 for Enterprise Edition, the Suite premium is $20,000, and Coherence Enterprise Edition alone lists at $11,500.
That comparison is worth holding on to at renewal. If Coherence is the only reason you are on Suite, and the grid is smaller than the WebLogic footprint, licensing Enterprise Edition plus standalone Coherence on the grid nodes can cost less than Suite across the whole estate.
Coherence is easy to start. A developer can add the library, start a cache server and have a working grid in an afternoon, and nothing in that process asks about entitlement.
The pattern we see is a microservice platform that adopted Coherence for shared state, running on hosts that have no relationship to the WebLogic Suite order. It is invisible until an audit script enumerates the running Java processes.
Grids are built for peak, for failure and for growth, and every node built for a condition that rarely occurs is licensed at full price all year. Sizing is where the recurring overspend lives.
A grid sized so it can lose a rack and still serve peak carries substantial deliberate headroom. That is sound engineering. It is also a license line that runs at 22 percent a year whether the headroom is used or not.
The buyer side answer is not to remove the resilience. It is to size to sustained load with a documented, tested scale out plan, and to hold the difference as capacity you can buy when you need it rather than capacity you rent forever.
Oracle offers no free development or test entitlement for Coherence. A test grid is licensable on the same metric as production unless your contract contains a specific right.
Disaster recovery is where the contract language matters most. A standby grid that is installed and running is licensed. A genuinely cold node, installed but never started, is treated differently, and the difference is worth confirming in writing before you build.
One grid, four ways to get the number wrong, Coherence Enterprise Edition at list
| What was counted | Cores | Processors after core factor | License at list | Support per year |
|---|---|---|---|---|
| Cache servers only, as first declared | 32 | 16 | $184,000 | $40,480 |
| Plus storage disabled application members | 64 | 32 | $368,000 | $80,960 |
| Plus extend proxies and the test grid | 80 | 40 | $460,000 | $101,200 |
| Same estate lifted to an authorized cloud | 80 | 80 | $920,000 | $202,400 |
Nothing in that table is a price rise. Every row is the same grid, counted more completely, and the last row is the same grid counted under a different rule.
The common advice is to buy WebLogic Suite so that Coherence is covered and you never have to think about it again. We disagree, and the reason is that Suite covers the wrong half of the problem. Suite grants Coherence Enterprise Edition on the processors you licensed for Suite, which is precisely the set of processors you were already going to declare. It does nothing for the standalone grid a development team built, nothing for the federation link between your two data centers, and nothing for the .NET client the trading desk wrote, and each of those is the kind of finding that arrives with backdated support attached. The better move is to inventory the cluster membership first, decide which grids need Grid Edition features, and license those explicitly. Buying Suite as insurance against a Coherence question you have not asked yet is paying a premium for the wrong policy.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
You cut it by shrinking the counted grid and by making sure you are not paying Grid Edition prices for Enterprise Edition behavior, or the reverse. Four moves account for most of the recovery.
Because a cluster must be homogeneous, the way to avoid paying Grid Edition on every node is to stop putting the Grid Edition requirement in the main cluster. Separate the federated or non Java workload into its own smaller cluster and connect the two over an extend boundary.
That is architecture work, not paperwork, and it needs the platform team in the room. On a large grid it is usually the highest value action available.
Compare two positions across the whole estate: WebLogic Suite everywhere, against WebLogic Enterprise Edition everywhere plus standalone Coherence on the grid nodes only. Where the grid is smaller than the WebLogic footprint, the second position is often cheaper.
Run the same comparison on support, because support follows net license and the difference compounds every year. The Oracle technology price list page carries the current list positions for both routes.
Whether a cold standby counts, whether a storage disabled member counts, and which conversion applies in the cloud are all questions with a defensible answer and a costly one. Ask for the answer in the ordering document rather than in an email from an account team that will have changed by the next audit.
White Paper · Oracle Middleware
Oracle Fusion Middleware Licensing
WebLogic, SOA and Coherence, priced. Read it free.
Coherence rarely travels alone. If WebCenter or another Fusion Middleware product sits on the same domains, the WebCenter licensing guide and the Oracle middleware licensing guide cover the rest of the stack.
Coherence is licensed on the Processor metric, and every processor running a Coherence cluster member must be licensed. That includes storage enabled cache servers, storage disabled application members, extend proxy servers and management nodes, across production and non production alike.
Coherence Enterprise Edition is included with WebLogic Suite, on the processors licensed for Suite. It does not cover Grid Edition features, it does not cover Coherence nodes on hosts that are not licensed for Suite, and it does not cover a standalone Coherence grid running without WebLogic.
Enterprise Edition is a single site application data grid with write behind caching, HTTP session management and clustered management. Grid Edition adds cross site and WAN data management, federated caching, and cross platform real time clients in Java, .NET and C++. Grid Edition lists at $25,000 per processor against $11,500 for Enterprise Edition.
No. All members of a single Coherence cluster must run the same edition, and different editions can interoperate only across a Coherence*Extend boundary. That rule is why one Grid Edition requirement prices every node in that cluster at Grid Edition.
Yes. A storage disabled member holds no cache data but still runs Coherence and still joins the cluster, so its processors are licensable. In most WebLogic estates the storage disabled application tier is larger than the cache tier, which is why counting only cache servers understates the grid so badly.
On your own hardware, yes: licensable processors are physical cores multiplied by the factor in the Processor Core Factor Table, which is 0.5 for most x86 cores. In an Authorized Cloud Environment such as AWS, Azure or Google Cloud the core factor does not apply and two vCPUs count as one processor, so the same grid counts roughly twice.
Normally yes. Oracle provides no free development or test entitlement for Coherence, so a running non production grid is licensed on the same metric as production. A standby grid that is installed and started is licensed, and only a genuinely cold, never started node is treated differently, so confirm your position in writing.
Support runs at 22 percent of the net license fee, uplifted annually by the percentage in your support contract. On a 40 processor grid at Coherence Enterprise Edition list that is roughly $101,000 a year, and the figure is charged on the processors you licensed regardless of how heavily the grid is used.
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.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →A small per node price hides a large cluster total. The grid is the bill.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Oracle Database benchmarks, ULA exit patterns, Java audit posture, and OCI commitment math from every Oracle engagement we run on the buyer side.
