Oracle Verrazzano Enterprise Container Platform is Oracle's integrated, multi-cloud container management solution. Its processor-based subscription licensing model is critical to understand for effective IT asset management. This independent guide covers the licensing model, cost structure per CPU pair, mandatory Oracle Linux support, WebLogic Suite entitlements, virtual environment compliance, and practical optimisation strategies.
Treat Oracle Verrazzano as you would any Oracle middleware product. It may leverage open-source components, but usage in an enterprise setting requires careful licence compliance if you plan to receive Oracle's support services. For a broader view of Oracle container licensing, see Licensing Oracle in Docker and Kubernetes Containers.
Oracle Verrazzano is an enterprise container platform for deploying and managing containerised applications across on-premises, hybrid, and multi-cloud Kubernetes clusters. Built on open-source cloud-native technologies including Kubernetes, Istio, Prometheus, and Grafana, it simplifies application lifecycle management for both microservices and traditional Java EE applications.
| Capability | Description |
|---|---|
| Unified management | A single platform to deploy, secure, and monitor microservices alongside traditional WebLogic or Coherence workloads. |
| Multi-environment support | Consistent operations across private data centres and public clouds including Oracle Cloud, AWS, and Azure. |
| Built-in security and observability | Integrated Istio service mesh for traffic encryption and policy enforcement, plus Prometheus, Grafana, and OpenSearch for logging and monitoring. |
| Open-source core with enterprise support | Verrazzano's core is open source under Apache 2.0 licence. Oracle provides enterprise-grade support via subscription. Licensing comes into play when you seek official support and updates for production use. |
Oracle Verrazzano licensing is based on processor count, specifically the physical CPUs in the Kubernetes cluster nodes where Verrazzano is deployed. Unlike some Oracle products that offer Named User or per-core metrics, Verrazzano uses a subscription model per CPU pair.
| Licensing Aspect | How It Works | ITAM Impact |
|---|---|---|
| Processor-based subscription | You must licence every processor across all nodes of all Kubernetes clusters where Verrazzano components or images are running. | Maintain an accurate inventory of all Kubernetes nodes where Verrazzano is installed, including any cluster scaling or infrastructure changes. |
| Physical CPU pair metric | Each subscription covers 2 physical CPU sockets. This is the minimum granularity. Even a single-CPU system requires a subscription for a 2-CPU pair. | You cannot buy half a licence. Budget at the CPU-pair level and track socket counts across all environments. |
| Oracle-approved partitioning | In virtual environments, Oracle's Partitioning Policy determines CPU count. Oracle-approved hard partitioning (Oracle Linux KVM with CPU pinning) allows counting only allocated vCPUs. | If using VMware or other soft partitioning, Oracle may require licensing all physical cores in the host. See Oracle Technology Price List: How to Calculate Pricing. |
| Soft partitioning (VMware) | Oracle generally requires licensing all physical cores in the host if the partitioning method is not Oracle-approved. A Kubernetes node as a VMware VM on a 16-core host means Oracle considers all 16 cores as licensable. | Align with Oracle's partitioning policy to avoid compliance gaps. For VMware-specific guidance, see Oracle Licensing on VMware. |
| Admin cluster exemption | A dedicated Verrazzano administration cluster running only admin components and no business application workloads does not require a Verrazzano licence for its processors. | Design an isolated admin cluster to minimise licensing costs. Oracle explicitly recommends this and it is a straightforward cost saver. |
A company uses a small 2-node cluster for Verrazzano's admin console and operators, and a separate large 10-node cluster for actual applications. Only the 10-node application cluster's CPUs need licensing. The admin cluster's CPUs are exempt. If each node has 2 CPUs, this saves 2 CPU-pair subscriptions ($53,000 per year in list-price terms). Always utilise an isolated admin cluster to minimise licensing costs.
Virtual environment compliance is the number one source of unintentional non-compliance in Oracle Verrazzano licensing. Miscounting virtual CPUs, particularly when using VMware or public cloud instances, can result in significant audit exposure. Always apply Oracle's core factor and partitioning rules. When in doubt, err on the side of over-counting or use Oracle's own virtualisation tools (Oracle Linux KVM, Oracle VM) for hard partitioning. See Oracle Licensing on Hyper-V for additional virtualisation guidance.
Oracle positions Verrazzano as a subscription-based product. You pay annually for the right to use the software and receive support. The pricing structure is primarily driven by two factors: the number of CPU pairs required for licensing and the level of support needed.
| Deployment Scenario | Subscriptions Required | Annual Licence Cost (List) | Oracle Linux Support |
|---|---|---|---|
| Small deployment (2 CPUs total) | 1 subscription (covers 2 CPUs) | ~$26,500 | ~$1,399 |
| Medium cluster (8 CPUs total) | 4 subscriptions | ~$106,000 | ~$5,596 |
| Large cluster (16 CPUs total) | 8 subscriptions | ~$212,000 | ~$11,192 |
| Admin-only clusters | Excluded from CPU count if no workloads | Cost savings by exclusion | Still required for those nodes, but no Verrazzano fee |
The standard list price for an Oracle Verrazzano Premier Support subscription is approximately $26,500 per year for each physical CPU pair. This includes the right-to-use licence plus Oracle's Software Update Licence and Support for that year. Costs scale linearly with no volume discount built into the metric. However, enterprises can negotiate with Oracle for discounts, especially for large deployments or multi-year commitments.
One often overlooked cost driver is the mandatory Oracle Linux support prerequisite. Oracle Verrazzano is only supported on Oracle Linux as the host OS, and Oracle requires that you also maintain Oracle Linux Premier Support at approximately $1,399 per 2-CPU system per year for each system running Verrazzano. For 10 two-CPU servers, this adds approximately $13,990 per year on top of Verrazzano licence fees.
The $26,500 per CPU pair is a starting point. Enterprises should engage procurement early to explore volume discounting or broader Oracle agreements such as an Oracle ULA or cloud credit deals that may significantly reduce the effective per-CPU cost. From an ITAM perspective, always model the 3 to 5 year total cost of ownership including both Verrazzano and Oracle Linux support, and factor in potential cluster growth. See Oracle Contract Negotiation Service.
Every Oracle Verrazzano licence is tied to an Oracle Premier Support subscription. Oracle enforces mandatory support coverage on all licences. This is not optional.
| Support Requirement | Detail | ITAM Impact |
|---|---|---|
| Premier Support: not optional | When you purchase Verrazzano, support is bundled and required from day one. All licensed CPUs must be under continuous support. There is no licence-only unsupported price. | Budget for ongoing annual subscription cost. This is OPEX, not CAPEX. |
| No partial support | If you have five subscriptions, all five must be under active support contracts. You cannot drop support on some while keeping others. | Support costs scale 1:1 with licence count. No partial reduction possible. |
| Lapsed support equals non-compliance | Running Verrazzano without a current support subscription is non-compliant. Oracle can audit and back-charge for periods where support was not maintained. No grace period exists. | Set calendar reminders for renewal dates. Never allow subscriptions to lapse unintentionally. See Oracle Audit Defence. |
| Subscription model: no perpetual licence | If you choose not to renew, your right to use the software ends. You must de-install or stop using Verrazzano. | Unlike perpetual Oracle Database licences, there is no option to stop paying support and continue using. Plan exit strategy if not renewing. |
| Oracle Linux Support: prerequisite | Not bundled with Verrazzano. Every server running Verrazzano must have a separate Oracle Linux Premier Support contract. Oracle will consider Verrazzano unsupported without the underlying OS support. | Track Oracle Linux support contracts separately. Ensure coverage matches Verrazzano node count. |
| Included entitlements | 24/7 Oracle support, software updates, security patches, upgrades. Also covers integrated open-source components (Helidon, Coherence CE, Micronaut) as part of the Verrazzano stack. | Verify which components are covered before assuming separate licensing is required. |
| Premier Support end date | Oracle announced Premier Support for Verrazzano ends January 31, 2025. After that date, it enters Sustaining Support with no new patches, features, or enhancements. Only access to existing fixes. | Plan migration to Oracle Cloud Native Environment (OCNE) or alternative container platform. Sustaining Support may also be a negotiation point for better pricing. |
With Premier Support ending January 2025, Verrazzano enters Sustaining Support. No new features, no new security patches, no enhancements. Only access to existing fixes. Enterprises should evaluate whether to continue on Sustaining Support, migrate to Oracle Cloud Native Environment, or consider alternative container platforms. This may also become a negotiation point. Oracle may be more flexible in pricing knowing the product's future development is limited. See Third-Party Support Transition Service and Oracle Support Costs 2026.
| # | Recommendation | Detail |
|---|---|---|
| 1 | Inventory and map your clusters | Maintain an up-to-date inventory of all Kubernetes clusters and nodes where Verrazzano is deployed. Map the physical CPU count of each environment to know your exact licensing needs at all times. Use Oracle Assessment Tools to maintain continuous inventory. |
| 2 | Isolate the control plane | Use a dedicated admin cluster for Verrazzano's system components. By not co-locating user workloads, you exclude those nodes from licensing. This is a straightforward cost saver that Oracle explicitly recommends. |
| 3 | Right-size your Kubernetes deployment | Work with engineering teams to optimise cluster size. Prefer scaling within a node (pods per node) rather than adding nodes. Every CPU eliminated saves approximately $13,000 per year in subscription fees. |
| 4 | Verify virtualisation compliance | If using VMware, Hyper-V, or cloud VMs, consult Oracle's Partitioning Policy and verify CPU counting is correct. Use Oracle Linux KVM or Oracle VM for hard partitioning when possible. See Oracle Licensing on VMware. |
| 5 | Leverage WebLogic Suite entitlements | If you already licence Oracle WebLogic Suite, you likely have entitlements to use Verrazzano Enterprise Edition at no extra licence cost for managing WebLogic workloads on Kubernetes. Verify scope with Oracle and obtain written confirmation. |
| 6 | Do not skimp on Oracle Linux Support | Ensure every Verrazzano server has Oracle Linux Premier Support. This is both a compliance requirement and essential for receiving OS patches and security fixes. |
| 7 | Plan for peaks: licences are not elastic | Unlike cloud-native pricing, Oracle requires licensing for the maximum CPU capacity. If your cluster auto-scales by adding nodes, those CPUs must be licensed. Set an upper limit on cluster size and do not exceed it without additional subscriptions. |
| 8 | Leverage existing Oracle agreements | Check if Verrazzano can be included in broader Oracle negotiations including ULAs, enterprise agreements, or Oracle cloud credit deals. Volume discounting and bundling can significantly reduce effective per-CPU cost. See Contract Negotiation Service. |
| 9 | Monitor product lifecycle | With Premier Support ending, Oracle may shift focus to OCNE or other container tools. This could become a negotiation point for better pricing, or trigger a platform migration strategy. Stay informed. |
| 10 | Keep proof of compliance | Maintain documentation of all clusters, purchase records, renewal dates, Oracle Linux contracts, architectural diagrams showing admin-only clusters, and any Oracle communications about special entitlements. This is critical during Oracle audits. |
| Step | Action | Detail |
|---|---|---|
| 1 | Audit your current deployment | Identify all deployments of Oracle Verrazzano. Note cluster names, locations (on-premises or cloud), number of nodes, and CPUs per node. Confirm none are running without proper licensing. See Conducting Internal Oracle Licence Audits. |
| 2 | Calculate licence needs | Using CPU count data, determine the number of CPU-pair subscriptions required. Exclude pure admin clusters. Apply Oracle's core factor and partitioning rules for VMs. Document the calculation for each environment. |
| 3 | Verify support coverage | Cross-check that you have active Verrazzano Premier Support subscriptions equal to the number of CPU pairs calculated. Verify that each Verrazzano host has Oracle Linux Premier Support. If there are gaps, purchase the needed support or migrate the workload. |
| 4 | Implement architecture changes | If your audit reveals inefficiencies such as mixed admin and workload clusters, low-utilisation nodes, or unfavourable VM hosting, plan changes: separate the Verrazzano control plane into a dedicated cluster, consolidate applications to fewer nodes, or adjust VM hosting arrangements. |
| 5 | Engage Oracle or a licensing advisor | Before your next renewal or expansion, review your findings with a trusted independent licensing advisor. Discuss optimisations (WebLogic Suite entitlements, volume discounts). Ensure special arrangements are noted in contracts. |
Oracle Verrazzano is licensed via an annual subscription model based on physical CPU sockets. You purchase Verrazzano Premier Support subscriptions, each covering a pair of physical CPUs (2 sockets) in your Kubernetes cluster nodes. You need enough subscriptions to cover all processors where Verrazzano is running. Example: 4 CPUs equals 2 subscriptions, 8 CPUs equals 4 subscriptions. The subscription includes the right to use the software and receive support for one year. There is no perpetual licence option.
You must licence every node where Verrazzano components or managed workloads run. If a node pulls a Verrazzano container (the platform operator or a Verrazzano-managed application), its CPU resources must be accounted for. Completely separate clusters or nodes that do not run any Verrazzano software do not need licensing. Additionally, Oracle provides an exemption for dedicated admin clusters. Nodes running only Verrazzano infrastructure and no user applications can be excluded. Segregate admin functions to avoid unnecessary licensing. See Licensing Oracle in Docker and Kubernetes.
The same basic rule applies: licence all CPUs where Verrazzano runs. But you determine the count according to Oracle's Partitioning Policy. Oracle-approved hard partitioning (Oracle VM, Oracle Linux KVM with CPU pinning) allows licensing only allocated CPUs. Common hypervisors like VMware are considered soft partitioning, meaning Oracle typically requires licensing the full physical host's CPUs. In public clouds (AWS, Azure), Oracle generally treats every 2 vCPUs as equivalent to one physical core. Miscounting virtual CPUs is the top source of unintentional non-compliance. See Oracle Technology Price List: How to Calculate Pricing.
The core components are open source and available on GitHub, but enterprise use of Oracle Verrazzano Enterprise platform is not free if you want Oracle's support and certification. Oracle monetises Verrazzano through the support subscription, which is effectively the licence. You could deploy the open-source components without paying Oracle, but you would have no vendor support, no rights to Oracle's enterprise distribution, and no coverage for included Oracle-branded components. Most enterprises take the supported route for stability and vendor support in production environments.
Your right to use Oracle Verrazzano Enterprise Edition technically ends. Oracle's subscription terms require you to discontinue use and uninstall the software. Running it without a valid subscription puts you in non-compliant territory. You lose access to patches, security updates, and Oracle support. Reinstating lapsed support later usually incurs back-support fees or penalties. Either maintain continuous support or plan a transition off Verrazzano before your subscription expires.
Yes, several options exist. If you have WebLogic Suite licences under support, you may have rights to deploy Verrazzano for managing WebLogic workloads without separate subscriptions. Confirm details with Oracle and obtain written confirmation. Oracle sometimes bundles services for OCI customers, so ask about credits or discounts. If licensing 10+ CPU pairs, negotiate for better per-unit pricing. Many enterprises secure significant discounts through multi-year commitments or by leveraging their overall Oracle spend. Use Oracle's fiscal year timing or quarter-end pressure to get the best deals. See Contract Negotiation Service.
Oracle's processor-based subscription model, combined with virtualisation rules, partitioning policies, and mandatory Oracle Linux support, creates significant compliance complexity. Our independent advisory helps ITAM teams audit their Kubernetes environments, validate CPU counts, and ensure full compliance before Oracle does it for them.
Oracle Advisory ServicesDeployment inventory, CPU counting, virtualisation compliance, and Oracle Linux support validation. Fixed-fee engagements. No Oracle conflicts.