Contents
Key takeawaysHow Coherence is countedEditions and list pricesWhere Suite coverage stopsHow sizing inflates the billWhat we have seenCutting a committed billTalking to OracleWhat to do nextFAQCoherence is licensed per processor on every host running a cluster member, including storage disabled application servers and proxies. WebLogic Suite covers only Enterprise Edition on Suite processors, and one Grid Edition feature reprices the whole cluster.
- Every cluster member is licensable. Storage disabled application servers and Extend proxies count alongside the cache servers in a Standard or Enterprise Edition cluster, so a cache server only inventory understates the grid.
- Suite grants Enterprise Edition only. WebLogic Suite includes Coherence Enterprise Edition, not Grid Edition, and only on the processors licensed for Suite.
- One cluster, one edition. A single TCMP cluster must run one edition throughout, so one Grid Edition requirement puts every storage enabled server and proxy in it on Grid Edition.
- List prices per processor. Coherence Enterprise Edition is $11,500, Grid Edition $25,000 and the Management Pack for Oracle Coherence $3,500.
- Federation and real time clients cost extra. Cross site federated caching and .NET or C++ real time clients are Grid Edition features that often run on a Suite entitlement that does not cover them.
- The cloud doubles the count. The core factor does not apply in an authorized cloud, so a grid counted as 16 processors on premises becomes 32 on AWS, Azure or Google Cloud.
Oracle Coherence is licensed per processor on every server where a member of the cluster runs, and few organizations can say how many members they have. The bill covers the whole grid. The entitlement most buyers rely on, the Coherence that ships inside WebLogic Suite, is narrower than the way they use it.
This guide is written for the person who has to stand behind a Coherence number in a renewal or an audit. Read it alongside our WebLogic support tiers guide, since most Coherence rights come from the Suite entitlement, and the WebLogic cloud licensing guide if the grid is moving off your own hardware.
How is Oracle Coherence licensed, and what gets counted?
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 sets out the editions on the Coherence editions page.
Cluster membership decides it. If a Java process joins the cluster, it is a node, and the host it runs on is licensable. That set is wider than most inventories record.
Which processes count as a Coherence node
- Storage enabled cache servers. These hold the data and appear in every inventory.
- Storage disabled members. Application servers that join the cluster to read and write the cache store no data, but they run Coherence, so in a Standard or Enterprise Edition cluster their processors count.
- Extend proxy servers. The proxy tier that serves remote clients is a cluster member like any other.
- Management and monitoring nodes. A process running the Coherence management host or a JMX bridge counts.
- Non production grids. Development, test, staging and disaster recovery clusters are licensable unless your contract says otherwise in writing.
The storage disabled members change the total more than anything else. In a typical WebLogic deployment the application tier has more processors than the cache tier, so counting only the cache servers can understate the grid by more than half.
How to build a node list that holds up in an audit
Ask the cluster itself. Coherence reports its own membership, and that report is the same evidence Oracle's data collection will produce.
- Export the member list from each cluster, with the host and role of every member. Each member prints a MasterMemberSet block in its log when it joins, listing every member it can see, and the Coherence:type=Node MBeans expose each member's machine and role name over JMX.
- On releases that include Management over REST, the /management/coherence/cluster/members endpoint returns the same list in one call, which is easier to archive as evidence.
- Map each host to its physical processor model and core count, or to its cloud instance shape.
- Mark each member as storage enabled, storage disabled, proxy or management.
- Reconcile that host list to the processors licensed for WebLogic Suite. Every host missing from that list needs its own answer.
Run the export at peak and again during a quiet period. Grids that scale out add members under load, and an export taken only in a quiet hour will miss them.
How the core factor changes the count on premises and in the cloud
On your own hardware, 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. Our core factor guide covers the less common chips.
In an Authorized Cloud Environment the core factor does not apply, and two vCPUs count as one processor where hyperthreading is on. Oracle sets that rule in its cloud licensing policy.
The 32 cores that counted as 16 processors on premises are presented as 64 vCPUs on AWS, Azure or Google Cloud and count as 32 processors. A lift and shift with no change to the application doubles the Coherence bill.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
Which Coherence edition do you need, and what does each cost?
Most WebLogic shops need Enterprise Edition, and the price gap to Grid Edition is where the money sits. Coherence ships in three server editions. Enterprise Edition is what WebLogic Suite grants, and Grid Edition is what a surprising number of deployments actually use.
The prices below come from the Oracle Technology Global Price List, the only version of the number worth negotiating from. Confirm the current edition of that document before you build a business case on it.
| 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, real time Extend clients in any language, Elastic Data, HotCache |
| Coherence Grid Edition | $25,000 | Cross site and WAN data management, federated caching, cross platform real time clients in Java, .NET and C++, Elastic Data, GoldenGate HotCache | Nothing above it; this is the top edition |
| Management Pack for Oracle Coherence | $3,500 | Enterprise Manager monitoring and diagnostics for the grid | Not part of any Coherence edition; included with WebLogic Suite only on Suite processors |
What Enterprise Edition covers
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 deployments that is 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.
What pulls a cluster into Grid Edition
Grid Edition is about reach, across data centers and across languages. Each trigger below is a design decision rather than a capacity decision, which is why it tends to arrive unpriced.
- Federated caching or any WAN topology. Replicating a cache between two sites for resilience or locality is a Grid Edition capability.
- Real time clients over Coherence*Extend. The full client, with near caching, continuous query and event notifications, is Grid Edition. The thinner Data Client works with any server edition.
- Non Java clients in real time mode. The .NET and C++ client libraries used as real time clients require Grid Edition on the server side.
- Elastic Data and GoldenGate HotCache. Oracle's licensing documentation places both in Grid Edition. HotCache is set up alongside a GoldenGate feed, so ask the database and integration teams as well as the platform team.
Why one Grid Edition feature reprices the whole cluster
Every member of a single TCMP cluster must run the same edition. Different editions can talk to each other only across a Coherence*Extend boundary, never inside one cluster.
So one .NET real time client, or one federation link to a second site, does not upgrade a single node. It puts every storage enabled server and proxy in that cluster on Grid Edition instead of Enterprise Edition, at $13,500 per processor of extra list.
On 24 processors of cache servers and proxies that is $324,000 of license and about $71,000 a year of support, triggered by a design choice that was never priced. We see this more often than any other Coherence error.
One rule works in your favor. Under Oracle's Coherence licensing documentation, storage disabled Java members of a Grid Edition cluster can run as Real Time Cluster Member Clients, which every Grid Edition license includes without limit. Confirm that treatment in writing for your release before you price an upgrade, since it can take the application tier out of the count.
Where does the WebLogic Suite Coherence entitlement stop?
It stops at Enterprise Edition features, on the processors licensed for WebLogic Suite, inside the WebLogic deployment. Step past any one of those limits and you need a Coherence license of your own.
What WebLogic Suite grants
WebLogic Suite bundles Coherence Enterprise Edition with WebLogic Server Enterprise Edition, and Oracle's licensing manual also lists the Enterprise Manager pack for Coherence among Suite's contents. Suite lists at $45,000 per processor against $25,000 for WebLogic Server Enterprise Edition.
That makes the Suite premium $20,000 per processor, while Coherence Enterprise Edition on its own lists at $11,500. Keep that gap in view at renewal. If Coherence is the main reason you are on Suite, and the grid is smaller than the WebLogic footprint, separate licenses can cost less across the whole deployment.
Five places the Suite grant runs out
- A Coherence node on a host not licensed for Suite. The entitlement follows the licensed processors, so a grid that spills onto cheaper hardware spills outside the grant.
- A standalone grid with no WebLogic. A cache cluster a development team built on plain Java virtual machines has no Suite entitlement behind it.
- Any Grid Edition feature. Federation, WAN topologies and non Java real time clients sit outside Enterprise Edition, and the single edition rule spreads the requirement to every server node in the cluster.
- Coherence serving a non WebLogic application. If the consumer of the cache is not the WebLogic deployment, the embedded use argument fails.
- The management pack on other hosts. The Suite copy of the pack covers Suite processors only. Monitoring a separate grid in Enterprise Manager needs the $3,500 per processor pack, unless those members share CPUs with WebLogic Server covered by the WebLogic Server Management Pack Enterprise Edition.
The standalone grid that was never ordered
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 meet is a microservice platform that adopted Coherence for shared state, on hosts with no link to the WebLogic Suite order. It stays invisible until an audit script lists the running Java processes.
Is the grid running the free Community Edition?
Check which build those teams use before you accept a finding. Coherence Community Edition is open source under the Universal Permissive License and ships under the com.oracle.coherence.ce Maven group. It carries no license fee, but it also lacks federation, Coherence*Web session management, Elastic Data and HotCache, so a team using any of those is on a commercial build.
Worked example: Suite against separate licenses
Say you run WebLogic on 40 processors of application servers and a dedicated cache tier of 8 processors. The only reason you bought Suite was Coherence. Three ways to license the same system, at list:
| Route | License calculation | License at list | Support per year at 22 percent |
|---|---|---|---|
| Route A: Suite on the application tier, Coherence EE on the cache hosts | 40 × $45,000 + 8 × $11,500 | $1,892,000 | $416,240 |
| Route B: WebLogic EE, Coherence EE on all 48 processors (application servers stay cluster members) | 40 × $25,000 + 48 × $11,500 | $1,552,000 | $341,440 |
| Route C: WebLogic EE, Coherence EE on the 8 cache processors, application tier connects as Extend Data Clients | 40 × $25,000 + 8 × $11,500 | $1,092,000 | $240,240 |
Route B saves $340,000 of license because $11,500 is less than the $20,000 Suite premium on each processor. It gives up what else Suite carries, including the Coherence management pack, Forms and Reports, and zero downtime patching, so price anything you use from that list back in.
Route C depends on architecture. Oracle's licensing documentation includes Data Client use with Standard and Enterprise Edition licenses, but Data Clients cannot use near caches, continuous query or event notifications. Applications that rely on those, or on Coherence*Web sessions, have to stay cluster members.
How does cluster sizing inflate the Coherence bill?
Grids are built for peak, for failure and for growth, and every node built for a rare condition is licensed at full price all year. Sizing is where recurring overspend accumulates.
Why peak sizing overcounts
A grid sized to lose a rack and still serve peak carries a lot of deliberate headroom. That is sound engineering. It is also a license line that costs 22 percent a year in support whether the headroom is used or not.
Keep the resilience. Size to sustained load, document and test a scale out plan, and buy the difference when you need it, so you are not paying support on it every year in between.
Non production, disaster recovery and the standby question
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 contract wording matters most. A standby grid that is installed and running is licensed, while a cold node, installed but never started, is treated differently. Confirm that difference in writing before you build, and read our guide to Oracle disaster recovery licensing in the cloud if the recovery site is on AWS or Azure.
| 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 grid lifted to an authorized cloud | 80 | 80 | $920,000 | $202,400 |
None of those rows is a price rise. Each is the same grid counted more completely, and the last row is that grid counted under a different rule.
The usual advice to buy Suite as cover, and why we disagree
The common advice is to buy WebLogic Suite so Coherence is covered and never needs thought again. We disagree, because Suite covers the part of the problem you already had under control. It grants Coherence Enterprise Edition only on processors you were going to declare anyway.
It does nothing for the standalone grid a development team built, the federation link between two data centers, or the .NET client a trading desk wrote. Each of those arrives as a finding with backdated support attached. Inventory 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.
What have we seen in recent Coherence negotiations?
Coherence is the Oracle middleware product buyers describe least accurately. That held across the roughly 15 to 25 Oracle middleware engagements I ran in 2024 and 2025, and three findings came up again and again.
- Undercounted nodes. The platform team's node inventory was a median 2.4 times smaller than the member list the cluster reported, because storage disabled members and proxies were left out.
- Grid Edition on a Suite grant. In about one organization in three, Grid Edition features were running on a WebLogic Suite entitlement. Federated caching between two data centers was the usual cause.
- Grids procurement never knew about. Where a development team had deployed Coherence standalone, procurement first heard of it when the audit data collection script found it.
The gap between Enterprise and Grid Edition, $13.5k per processor at list, is why the second finding costs so much. It applies to every storage enabled server and proxy in the affected cluster, including nodes that never touch the feature.
How do you cut a Coherence bill you have already committed to?
Shrink the counted grid, and make sure you pay Grid Edition prices only for clusters that need Grid Edition behavior. Four actions account for most of the recovery we see.
Split the cluster on the edition boundary
Because a cluster must run one edition, the way to avoid Grid Edition on every node is to keep the Grid Edition requirement out of the main cluster. Put the federated or non Java workload in its own smaller cluster and connect the two over Extend.
That is architecture work and needs the platform team in the room. On a large grid it is usually the highest value change available.
Retire the members you no longer need
- Storage disabled members on hosts that no longer use the cache. Removing the library from the application removes the node from the count.
- Idle proxies. Extend proxy tiers often outlive the remote clients they were built for.
- Abandoned test grids. The cheapest processor is the one that stops running.
- Duplicated caches. Two grids doing the same job for two applications are two license lines.
Before you drop licenses, ask how support will be recalculated. Oracle's support policies reprice a reduced license set, which can absorb much of the saving if the original discount was large.
Check whether Suite still earns its place
Compare two positions across the whole deployment: WebLogic Suite everywhere, against WebLogic Server 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, as the worked example above shows.
Run the same comparison on support, because support follows net license and the difference compounds every year. Our Oracle technology price list page carries current list positions for both routes, and the WebLogic Suite edition decision guide walks through the migration itself.
Get the counting basis agreed in writing
Whether a cold standby counts, whether a storage disabled member counts, and which conversion applies in the cloud each have a cheap answer and a costly one. Get the answer into the ordering document, because the account team that confirms it by email will probably have changed by the next audit.
Our Oracle Fusion Middleware licensing guide prices WebLogic, SOA and Coherence side by side if you need the wider picture.
How should you handle the Coherence conversation with Oracle?
Come with your own member list and a priced view of each option, and hold Oracle to written definitions. The account team's first lines are predictable, and each has a precise answer.
What the account team will say, and what to say back
- "Coherence is included with your WebLogic Suite, so you are covered." Ask them to confirm that in writing for the named hosts, and for the federation link and any .NET clients. Suite covers Enterprise Edition on Suite processors, and they will not confirm the rest.
- "Our scripts found Coherence on these hosts, so they need licenses." Ask for the member list behind the claim. Separate cluster members from Extend Data Clients, and check whether any grid is the open source Community Edition.
- "The simplest fix is to move the whole cluster to Grid Edition." Ask them to price a separate small cluster for the Grid Edition workload instead, and to quote the WebLogic Coherence Grid Edition Option that Oracle's licensing manual lists. If the whole cluster does move, ask which storage disabled members they will treat as Real Time Cluster Member Clients.
- "Moving to AWS does not change what you need." It changes the count. Model the vCPU conversion before migration and pick instance shapes with that rule in mind.
Contract wording to ask for
- A written counting basis. State how storage disabled members, Extend Data Clients and management nodes are treated, so the next audit uses the same rules.
- Cold standby treatment. Name the disaster recovery hosts and record that installed but never started nodes carry no license until they run.
- The cloud conversion. Write the vCPU to processor rule for your chosen provider into the order, so a later policy change does not reprice what you already bought.
- A price hold for Grid Edition. Fix the per processor price to upgrade a named cluster, or to add processors, for the length of the agreement.
- Support treatment on reduction. Ask how support will be recalculated if you terminate part of the license set, and get the answer before you sign.
Coherence rarely travels alone. If WebCenter or another Fusion Middleware product runs on the same domains, the WebCenter licensing guide and the Oracle middleware licensing guide cover the rest of the stack.
What to do next
- Export every member list. Pull the member list from every Coherence cluster you can find, including the ones the platform team calls temporary, and record host, role and storage setting for each member.
- Map hosts to processors. Tie every host to a processor model and core count, or to a cloud instance shape, and apply the correct rule to each.
- Reconcile to Suite. Compare the host list with your WebLogic Suite licensed processors. Every host outside that list is an open question with a price attached.
- Test for Grid Edition triggers. Look for federation between sites, WAN topologies, HotCache, and .NET or C++ real time clients. Any one of them prices the whole cluster at Grid Edition.
- Isolate the Grid Edition workload. Where the architecture allows, move it into its own cluster that connects to the main one over Extend.
- Price the alternatives. Compare WebLogic Suite with Enterprise Edition plus standalone Coherence across the whole deployment, on license and three years of support.
- Settle standby and test rights. Confirm the non production and disaster recovery position in writing before the next renewal, while you still have something to trade.
- Bring the corrected number yourself. A gap you disclose becomes a negotiation. A gap Oracle finds becomes a settlement with backdated support.
Holding an Oracle quote or renewal? Our Oracle contract negotiation team works only for buyers, for a fixed fee or 25 percent of what we save you.
Frequently asked questions
How is Oracle Coherence licensed?
Per processor, on every server where a Coherence cluster member runs, whether it holds data or not. Cache servers, application servers that join the cluster, proxies and management nodes all count, and the rule is the same for development, test and disaster recovery grids unless your contract carves them out.
Is Coherence included with WebLogic Suite?
Partly. Suite includes Coherence Enterprise Edition and the Enterprise Manager pack for Coherence, but only on the processors licensed for Suite. Grid Edition features, Coherence members on other hosts and a standalone grid without WebLogic all need separate Coherence licenses.
What is the difference between Coherence Enterprise Edition and Grid Edition?
Enterprise Edition is a single site data grid with write behind caching, session management and clustered management. Grid Edition adds federation and WAN replication between sites, real time clients in Java, .NET and C++, Elastic Data and HotCache, at $25,000 per processor against $11,500.
Can I run different Coherence editions in the same cluster?
No. Oracle does not allow editions to be mixed inside one TCMP cluster. A Standard or Enterprise Edition cluster can connect to a Grid Edition cluster only as an Extend client, which is why splitting a Grid Edition workload into its own cluster is the usual way to contain the cost.
Do storage disabled Coherence nodes need licenses?
In a Standard or Enterprise Edition cluster, yes. A storage disabled member holds no cache data but joins the cluster, so its host is licensable. In a Grid Edition cluster the same Java process can run as a Real Time Cluster Member Client, which Grid Edition includes without limit, and an application that only needs get, put and query calls can reconnect as a free Extend Data Client.
Does the Oracle core factor apply to Coherence?
On your own hardware it does, and most x86 cores carry a factor of 0.5. On AWS, Azure or Google Cloud the factor does not apply and two vCPUs with hyperthreading count as one processor, so the same grid needs roughly twice as many licenses after a migration.
Are development, test and disaster recovery Coherence grids licensable?
Normally yes. Coherence has no free non production entitlement, so any running test or staging grid is licensed like production. A disaster recovery grid that is started is licensed too, and a cold node that is installed but never started is the one case to get confirmed in your contract.
How much does Coherence support cost each year?
Oracle charges 22 percent of the net license fee each year, rising by the uplift in your support terms. A 40 processor Enterprise Edition grid at list carries roughly $101,000 a year, payable on every licensed processor however lightly the grid is used.