Understanding Oracle Verrazzano

Oracle Verrazzano Enterprise Container Platform was designed as a multicloud Kubernetes management solution for enterprises deploying and managing containerized applications across on-premises infrastructure, Oracle Cloud Infrastructure (OCI), and other public cloud environments. The platform provided a unified management experience for containerized workloads, attempting to simplify the operational complexity of managing multiple Kubernetes clusters in hybrid and multicloud scenarios.

Verrazzano combined open-source technologies with Oracle's commercial support and management layers, positioning itself as an alternative to solutions like Red Hat OpenShift and VMware Tanzu. The platform was marketed primarily to enterprises already invested in the Oracle ecosystem, particularly those running WebLogic Server and other Oracle middleware.

The core value proposition centered on reducing operational overhead for organizations managing distributed Kubernetes clusters, providing visibility across clusters, application lifecycle management, and integration with monitoring and security tools. However, adoption remained limited, and Oracle's commitment to the platform diminished over time.

The End of Premier Support Timeline

Oracle Verrazzano reached the end of premier support on January 31, 2025. This milestone represents far more than a routine support transition. On February 2, 2025, Oracle archived the entire Verrazzano GitHub organization, signaling complete cessation of active development.

Under sustaining support, Oracle will continue accepting support calls and providing access to existing knowledge articles, but this is purely reactive support. No new code will be produced. No security patches will be released. No bug fixes will be issued. No enhancements will be developed. The platform is, for all practical purposes, frozen in time.

This differs materially from extended support offerings on other Oracle products. Organizations cannot expect proactive security bulletins, patches for newly discovered vulnerabilities, or fixes for bugs identified in existing deployments. The burden shifts entirely to customers to maintain and secure their environments without vendor assistance.

What Sustaining Support Actually Means

Many enterprises misunderstand what sustaining support entails. It is not a continuation of premier support with a reduced feature set. Instead, it represents the absolute minimum vendor obligation to acknowledge your support contract exists.

Under sustaining support terms, Oracle support engineers may be available to answer questions and provide access to previously published documentation. If you encounter a bug that Oracle previously fixed in a different context, support may provide guidance or workarounds based on existing knowledge. However, no resources are allocated to investigating new issues, developing patches, or validating fixes for your specific environment.

For security vulnerabilities, sustaining support provides no proactive protection. If a vulnerability is discovered in Verrazzano, you will not receive a patch. You will not receive a security advisory. You will not receive a workaround. Organizations must independently identify vulnerabilities and implement mitigations or accept the risk of unpatched systems.

"Organizations cannot expect proactive security bulletins, patches for newly discovered vulnerabilities, or fixes for bugs identified in existing deployments when a product enters sustaining support."

Verrazzano Licensing Model Explained

Oracle Verrazzano was sold as a subscription product rather than a perpetual license. The Oracle Verrazzano Premier Support subscription grants customers the right to use the software on servers—whether those servers are owned by the customer or third-party hosted—for internal business operations.

The subscription model is critical for cost planning. Unlike perpetual licenses with maintenance fees, subscriptions are renewable. Organizations must renew their Verrazzano subscriptions annually or lose the license to run the software. This creates continuous vendor dependency for organizations that continue deploying and managing Verrazzano applications.

Notably, Oracle does not use Oracle licence agreement for Verrazzano licensing. Instead, organizations manage Verrazzano licenses through individual agreements, Unlimited License Agreements (ULA), Perpetual Use and License Agreements (PULA), Oracle Cloud Services (OCS), or Cloud Services Initiatives (CSI). This fragmented licensing approach means there is no single standardized way organizations acquire and renew Verrazzano rights.

For organizations in a ULA or similar agreement structure, verify whether Verrazzano is included in the existing agreement or requires a separate subscription. This distinction carries significant cost implications.

The WebLogic Suite Entitlement Advantage

Here is a critical point that many enterprises have overlooked: organizations holding active Oracle WebLogic Suite licenses under support may have rights to deploy Verrazzano Enterprise Edition without a separate Verrazzano subscription.

This entitlement is not widely publicized by Oracle, and many WebLogic Suite customers are unaware they can run Verrazzano at no additional licensing cost. If your organization holds current WebLogic Suite licenses, you must audit whether Verrazzano deployment rights are included in your agreement.

WebLogic Suite is a mature product with widespread enterprise adoption, particularly in financial services, telecommunications, and government sectors. Organizations holding WebLogic Suite licenses under active support should conduct a licensing audit immediately to determine if they can migrate their Verrazzano infrastructure without triggering new subscription obligations.

However, this entitlement provides only the right to deploy Verrazzano Enterprise Edition. Transitioning from Verrazzano to other solutions is still necessary given the end of premier support. The WebLogic Suite entitlement merely removes one financial barrier to maintaining existing Verrazzano deployments during a transition period.

The Real Cost of Staying on Verrazzano

Organizations continuing to pay Verrazzano subscription fees face escalating annual costs with no new development, no new features, and no security improvements. Oracle's standard support fee increase of 8% per year compounds annually.

A $100,000 annual Verrazzano subscription becomes $108,000 in year two, $116,640 in year three, and continues compounding indefinitely. Over a five-year period, a six-figure subscription nearly doubles, even as the underlying product receives zero enhancements or security patches.

This financial model creates perverse incentives. Organizations are paying more each year for a product that provides less value over time. As upstream Kubernetes versions advance, the Verrazzano platform falls further behind. Zero-day vulnerabilities will never be patched. Operational burdens increase as the technology drifts further from current Kubernetes standards.

The economic case for remaining on Verrazzano beyond a short transitional period is indefensible for most organizations. Even a modestly expensive migration is often less expensive than three years of escalating Verrazzano subscription fees.

Security Risk Profile of Unsupported Platforms

Running an unsupported container management platform introduces substantial security risk. As Kubernetes evolves and new attack vectors emerge, Verrazzano cannot respond. Vulnerabilities discovered in Kubernetes components or dependencies will not be fixed in Verrazzano.

Container platforms are attractive targets for adversaries because they control deployment of critical workloads and manage sensitive data at scale. Vulnerabilities in a container platform can facilitate lateral movement, supply chain attacks, and compromise of protected assets.

Compliance frameworks increasingly require timely remediation of known vulnerabilities. Organizations running Verrazzano may be unable to demonstrate compliance with PCI-DSS, HIPAA, SOC 2, or industry-specific security standards that require prompt vulnerability patching. Security and compliance teams should evaluate whether unsupported Verrazzano deployments create unacceptable compliance risk.

Insurance and cyber liability policies may also exclude or limit coverage for losses resulting from known unpatched vulnerabilities. Running unsupported software potentially invalidates security insurance protection.

Technology Drift and Kubernetes Evolution

Kubernetes is a rapidly evolving platform. The upstream Kubernetes project releases a new minor version approximately every four months. Each release introduces security patches, performance improvements, new APIs, and behavioral changes.

Verrazzano, frozen as of February 2025, cannot incorporate these upstream advances. Organizations running Verrazzano will find themselves unable to deploy newer Kubernetes versions, unable to leverage recent security improvements, and unable to adopt emerging patterns and technologies in the Kubernetes ecosystem.

Applications developed against current Kubernetes versions may not be compatible with the version of Kubernetes bundled with Verrazzano. Developer productivity decreases when tools and practices diverge from industry standards. Recruiting and retaining talent becomes more difficult when your organization uses outdated container platforms.

Over time, technology drift becomes a significant operational burden. Staying on an unsupported platform means perpetually swimming against the current of industry innovation.

Migration Paths: Oracle OKE and Open-Source Alternatives

Oracle has explicitly positioned Oracle Container Engine for Kubernetes (OKE) as the cloud-based migration path for Verrazzano customers. OKE is a managed Kubernetes service on OCI that benefits from continuous updates, active development, and full Oracle support.

For organizations committed to the Oracle ecosystem, OKE represents the natural migration target. The transition from Verrazzano to OKE requires re-architecting deployments to run on managed Kubernetes, but this aligns workloads with Oracle's long-term platform strategy.

For on-premises Kubernetes management, open-source and vendor-supported alternatives exist. Red Hat OpenShift is a production-hardened Kubernetes distribution backed by enterprise support. VMware Tanzu provides multicloud Kubernetes management with VMware's support model. SUSE Rancher offers lightweight Kubernetes lifecycle management with commercial support.

Each alternative has distinct operational models, licensing, and cost structures. Organizations should evaluate migration paths based on infrastructure strategy, support requirements, and long-term vendor commitments rather than minimizing short-term transition costs.

"The economic case for remaining on Verrazzano beyond a short transitional period is indefensible for most organizations. Even a modestly expensive migration is often less expensive than three years of escalating Verrazzano subscription fees."

Bringing WebLogic Suite Licenses to OCI

If your organization is migrating from Verrazzano to OCI-based container management, you can bring existing WebLogic Suite licenses to OCI under Bring Your Own License (BYOL) terms. This capability is critical for cost management during migration.

WebLogic Suite licenses held under active support can be redeployed on OCI without additional licensing costs, subject to Oracle's licensing terms. Organizations can potentially reduce cloud costs by applying existing license investments to OCI infrastructure.

Furthermore, Oracle Support Rewards applies to ULA customers. If your organization holds an Unlimited License Agreement including WebLogic Suite, you receive $0.33 in OCI credits per dollar spent on ULA maintenance. This credit mechanism can offset cloud infrastructure costs and improve the financial case for cloud migration.

Work closely with Oracle License Management Services to ensure that migration to OCI is structured to maximize license portability and support rewards eligibility.

Contract Review and Negotiation Strategy

Organizations on Verrazzano subscriptions should conduct a comprehensive contract review before the next subscription renewal date. Key questions to address include:

  • What are the termination rights and notice periods in your Verrazzano subscription agreement?
  • Can you terminate the subscription early without penalty, or are you locked into a multi-year commitment?
  • What are the renewal terms, and is there an opportunity to negotiate different terms before renewal?
  • Can you convert your Verrazzano subscription to OKE or other Oracle cloud services as part of a transition plan?
  • Are there cost-sharing opportunities or migration discounts available from Oracle?

Organizations often accept unfavorable renewal terms without negotiation. However, Oracle is incentivized to work with customers on transition plans. The alternative is losing the contract entirely. Engage Oracle before the renewal date to discuss your migration timeline and explore whether discounted transition terms are available.

Comprehensive Migration Recommendations

Organizations running Verrazzano should execute the following migration planning steps immediately:

1. Conduct a Verrazzano Deployment Audit. Identify all systems running Verrazzano, document deployed applications, validate current version, and understand integration dependencies. Many organizations discover that Verrazzano is running in production but no longer actively managed.

2. Verify WebLogic Suite Entitlements. Review your Oracle agreement portfolio to determine whether WebLogic Suite licenses provide Verrazzano deployment rights. Engage Oracle License Management Services to formalize your licensing position.

3. Evaluate Migration Platforms. Assess OKE, OpenShift, Tanzu, and Rancher against your operational requirements, support preferences, and budget constraints. The cheapest platform is not necessarily the best choice if it creates operational complexity.

4. Develop a Migration Timeline. Plan your migration to complete well before sustaining support becomes operationally burdensome. A 12 to 18-month transition window is reasonable for most organizations.

5. Engage Oracle Before Renewal. Initiate conversations with your Oracle account team at least 90 days before your subscription renewal date. Discuss your migration strategy and explore whether Oracle can provide credits, discounted OKE migration services, or extended terms to support your transition.

6. Plan Security Transitions. Ensure that security scanning, vulnerability management, and compliance monitoring transition smoothly as you migrate off Verrazzano. Document your post-migration security architecture.

7. Document Lessons Learned. As you migrate off Verrazzano, capture insights about what was learned regarding platform selection, vendor diversification, and long-term support considerations.

Conclusion: Moving Forward

Oracle Verrazzano reached end of premier support on January 31, 2025, and development ceased entirely when Oracle archived the GitHub organization in February 2025. The platform will receive no new releases, no security patches, no bug fixes, and no feature development.

Organizations running Verrazzano face a critical business decision: maintain escalating subscription costs for an unsupported platform, or invest in migration to a supported alternative. For most enterprises, the economic and security case for migration is compelling.

The migration path is clear. Oracle has positioned OKE as the cloud-native continuation. Open-source and third-party alternatives provide on-premises options. The barriers to migration are primarily organizational and operational rather than technical.

Start your migration planning now. Conduct licensing audits to understand your WebLogic Suite entitlements. Evaluate platform alternatives. Develop a realistic transition timeline. Engage Oracle before subscription renewal to explore transition options. The sooner you initiate this process, the more control you maintain over your migration pace and costs.

Verrazzano's end of support does not represent a crisis requiring immediate action, but it does represent a deadline that will become increasingly consequential with each passing month. Organizations that defer decision-making will eventually face compressed timelines, escalated costs, and reduced negotiating leverage.