Oracle Java SE vs Amazon Corretto is the Java distribution decision where Oracle's Employee Metric Universal Subscription is the cost trap, Corretto is the no-cost OpenJDK alternative that runs the same workloads, and the buyer-side path is a clean migration that closes the Oracle audit exposure.

What Oracle Java SE and Corretto are

Oracle Java SE Universal Subscription. Oracle's commercial Java SE distribution, sold under the Employee Metric model since January 2023. The Universal Subscription provides Oracle JDK binaries, Java Management Service (JMS) for fleet visibility, GraalVM Enterprise Edition, and Oracle's commercial Java support (quarterly Critical Patch Updates, premier and extended support, 24/7 support entitlement). The Employee Metric counts every employee, full-time contractor, agent, consultant, and temporary worker — regardless of whether they use Java. A 10,000-employee organisation with 50 Java developers pays the same as a 10,000-employee organisation where every employee uses Java.

Amazon Corretto. Amazon's no-cost, production-ready, multi-platform OpenJDK distribution. Released as open-source under GPL v2 with Classpath Exception (the same licence as upstream OpenJDK). Amazon ships Corretto for Java 8, 11, 17, 21, 23, and onward LTS versions, with binaries for Linux (Amazon Linux 2, RHEL, Debian, Ubuntu, Alpine), macOS (Intel and ARM), and Windows (x86_64). Corretto is the default JDK on Amazon Linux 2, Amazon Linux 2023, and Amazon EMR. Corretto runs in production at AWS at scale — including AWS internal services — which is what underwrites the production-grade claim.

The two products are binary-compatible at the same JDK major version. Code compiled against Oracle JDK 17 runs unmodified on Corretto 17. The JVM behaviour, garbage collectors (G1, ZGC, Parallel), JIT compilers (C1, C2), and standard library APIs are functionally identical because both descend from the same OpenJDK upstream. The differences are commercial and operational, not technical.

Licensing models compared

Oracle Java SE Universal Subscription pricing (per employee per month, tiered).

The Universal Subscription includes Oracle JDK binaries (versions 8 onward), GraalVM Enterprise, Java Management Service, and commercial Java support. The Employee Metric is unforgiving — the count is total employees plus contractors plus consultants, not just Java users. Discounts of 10 to 25 percent are achievable for multi-year commitments and competitive bake-offs against migration alternatives, but the Employee Metric base is not negotiable downward.

Amazon Corretto licensing. Amazon Corretto is licensed under GPL v2 with Classpath Exception. Commercial use is permitted at no cost, including in production, including in shipped commercial products. Amazon makes Corretto available free of charge as a strategic AWS asset — the AWS thesis is that no AWS customer should feel commercially captive to Oracle's Java terms while running on AWS infrastructure. There is no licence count, no Employee Metric, no audit exposure, no Oracle Master Agreement, no Java SE Universal Subscription order form.

The licensing differential between Oracle Java SE Universal Subscription and Amazon Corretto is the entire commercial story. For most enterprise workloads, the technical capability and operational support of Corretto is sufficient — and the licensing cost is zero.

Support model and patch cadence

Oracle Java SE support. Oracle provides commercial Java support as part of the Universal Subscription, including quarterly Critical Patch Updates (CPUs) on the third Tuesday of January, April, July, October (aligned to Oracle's broader CPU cadence). Oracle support entitles customers to 24/7 ticketing, severity-1 response within 1 hour, premier support through the active product lifecycle, and extended support for legacy LTS versions (e.g., Java 8 extended support through December 2030 for paying customers).

Amazon Corretto support. Amazon provides Corretto with quarterly security patches and bug fixes aligned to the same OpenJDK upstream cadence as Oracle's CPUs. Patches are released within 1 to 7 days of the OpenJDK upstream release and posted to GitHub, Docker Hub, and AWS-managed Yum/Apt repositories. Support for Corretto running on AWS infrastructure (EC2, ECS, EKS, Lambda, Beanstalk, EMR, AWS Workspaces) is included in standard AWS Support Plans — AWS support engineers are trained to triage Corretto issues, and AWS publishes Corretto-specific incident response guidance.

Patch cadence comparison:

For organisations that need vendor-backed 24/7 Java-specific support with indemnification, the choice is not Corretto-versus-Oracle but Corretto-plus-third-party-support versus Oracle. Azul Systems (Zulu Enterprise), BellSoft (Liberica), IBM Semeru Runtime, Red Hat OpenJDK, and SAP Machine all offer commercial OpenJDK distributions with 24/7 support at a fraction of Oracle's Employee Metric pricing.

Compatibility and performance

Compatibility. Amazon Corretto is binary-compatible with Oracle JDK at the same major version. Java applications, JAR files, WAR files, application server deployments, and JVM tuning parameters that work on Oracle JDK 17 work on Corretto 17 without code or configuration changes. Both products pass the TCK (Technology Compatibility Kit) for Java SE and are functionally indistinguishable from an application-runtime perspective.

Performance. The JVM internals — JIT compilers (C1 client compiler, C2 server compiler), garbage collectors (Serial, Parallel, G1, ZGC, Shenandoah), class loaders, JFR (Java Flight Recorder), JMX — are identical to upstream OpenJDK. AWS publishes performance benchmarks showing Corretto running at parity with Oracle JDK across SPECjbb, SPECjvm, and real-world workloads. Where Oracle Java SE has any performance advantage, it is from GraalVM Enterprise (the commercial GraalVM with extra optimisations) which is bundled with Universal Subscription. For applications that need GraalVM's specific advantages (native image, polyglot runtime, ahead-of-time compilation), GraalVM Community Edition is freely available and ships separately; for most server-side Java workloads, the C2 JIT in Corretto delivers comparable production performance.

Tooling compatibility. JConsole, VisualVM, Java Mission Control, Java Flight Recorder, jcmd, jstat, jmap, jstack, jhsdb all work on Corretto identically to Oracle JDK. Build tools (Maven, Gradle, Ant), CI/CD platforms (Jenkins, GitLab CI, GitHub Actions), application servers (Tomcat, Jetty, WildFly, WebLogic, WebSphere), and APM tools (Datadog, New Relic, Dynatrace, AppDynamics) support Corretto without modification.

Areas to watch in migration.

• Java Web Start — Oracle deprecated and removed Web Start in Java 11. If applications rely on Web Start, the deprecation issue is independent of the Oracle-versus-Corretto decision; both have removed it.
• Applets — Java applets are deprecated and removed; no JDK distribution supports them in JDK 17+.
• Oracle-specific Java add-ons — Oracle WebLogic-on-Java, Oracle Coherence-on-Java, Oracle JRockit-derived flight recording (now in OpenJDK as JFR) — these are typically supported on Corretto with the same configuration as Oracle JDK.
• Commercial features in older JDKs — Pre-JDK-11, "Java SE Advanced" features (Flight Recorder, Mission Control, Application Class-Data Sharing) required commercial flags on Oracle JDK. These features are now open-source in OpenJDK and ship with Corretto by default.

Migration path — drop-in replacement

The technical migration from Oracle JDK to Amazon Corretto is intentionally straightforward. For each affected system:

1. Inventory. Identify all systems running Oracle JDK. Use Java Management Service (JMS) if already deployed, or use OS-level inventory tools (find / -name java, dpkg -l | grep -i jdk, rpm -qa | grep jdk, choco list | findstr java on Windows). Forensic inventory is the prerequisite to a clean migration.
2. Version match. For each Oracle JDK installation, install the matching Corretto major version. Java 8 → Corretto 8, Java 11 → Corretto 11, Java 17 → Corretto 17, Java 21 → Corretto 21.
3. Install. Amazon publishes Corretto installers as DEB, RPM, MSI, PKG, and Docker images. On AWS Linux instances, Corretto is the default and only needs a package install. On Windows, the MSI installer handles registry updates and PATH/JAVA_HOME automatically.
4. Replace. Either install Corretto alongside Oracle JDK and switch JAVA_HOME / PATH / update-alternatives, or remove Oracle JDK after Corretto verification. The replacement is reversible.
5. Verify. Run application smoke tests. The JVM behaviour is identical so functional verification is typically 1 to 4 hours per application. JVM tuning flags carry over without modification.
6. Decommission Oracle. Uninstall Oracle JDK from the system. Document the removal with a timestamped log entry. This is the audit-defence evidence.
7. Exit the Universal Subscription. Notify Oracle in writing of non-renewal at the contractual notice window (typically 30 to 90 days before renewal). Confirm the exit in Oracle's contract management system.

A typical enterprise Corretto migration for a 5,000-employee organisation with 200 to 500 Java application footprints completes in 4 to 8 weeks of project time. The dependencies are: forensic inventory (1 to 2 weeks), pilot migration on non-production (1 week), production rollout in waves (2 to 4 weeks), Oracle JDK decommissioning and Universal Subscription exit (1 week).

The buyer-side defence on the migration:

• Document the migration timestamp on every system. This is the audit defence — proving the Oracle JDK was removed before the audit window.
• Keep the Oracle JDK MSI / RPM in a quarantined archive with a written justification. Do not redistribute. Some Oracle JDK binaries carry licence terms that prohibit redistribution; archival for audit-defence-evidence purposes is generally defensible.
• Maintain a Java fleet inventory artefact (a CSV or asset-management record) showing the as-built state at Universal Subscription exit. This is the buyer-side defence if Oracle later challenges the exit.
• Exit the Universal Subscription cleanly with written confirmation from Oracle's contract management. Verbal assurances from the account team are not enforceable.

Worked savings: 10,000-employee enterprise

Scenario: A 10,000-employee enterprise has been using Oracle JDK across approximately 350 server-side applications since 2019. Oracle has issued a Java audit notice in March, followed by a Universal Subscription proposal at the 10,000+ employee tier of $8.25 per employee per month. The customer is evaluating the Corretto migration.

For this profile, the 3-year savings from the Corretto migration land at $2.66M. The 5-year saving (assuming same growth) extends to roughly $5.1M including a hypothetical 7 percent annual Universal Subscription uplift. Even with the migration project cost and optional third-party Java support included, the economics are decisively in Corretto's favour. The decision is not commercial — it is purely operational: is Corretto's quarterly patch cadence and AWS-led support model acceptable for the customer's Java production workloads?

In our buyer-side practice, the answer is yes for over 90 percent of enterprise Java estates. The exceptions are: (a) customers running Oracle-specific commercial features at JDK 8 or earlier where the migration path requires JDK version upgrade first; (b) customers with regulatory requirements that mandate Oracle-branded Java support; (c) customers with niche third-party libraries that explicitly require Oracle JDK certification. For everyone else, Corretto is the right answer.

Audit exposure and the clean exit

Oracle's Java audit motion changed materially in 2023 with the Employee Metric model. Oracle LMS, GLAS, and Oracle's commercial Java team now actively scan for evidence of Oracle JDK consumption — typically through usage telemetry from Java Management Service (JMS) deployments at customer sites, through download records from Oracle.com when Java SE binaries are pulled from authenticated accounts, and through patch download evidence when customers apply Oracle's CPUs.

The typical audit motion: Oracle issues a "Java software usage review" letter citing evidence of Oracle JDK consumption, requests inventory of Java installations, and follows with a back-licence settlement proposal at full Employee Metric pricing for the audit period — typically 2 to 3 years. Settlement proposals at the 10,000-employee tier commonly run $2M to $5M.

The buyer-side defence playbook:

1. Do not respond to the Oracle letter without expert advisory. Initial customer responses establish the framing for the rest of the audit. Acknowledging Oracle JDK use without challenge accepts the Employee Metric pricing as the baseline.
2. Forensically inventory Java usage. Buyer-side defence is built on evidence. Identify every Oracle JDK installation, the install date, the patch level, the application footprint, the actual users.
3. Challenge Oracle's evidence. Oracle's audit claims rely on telemetry that the customer may not have authorised. Forensic challenge of the evidence chain often weakens Oracle's settlement position.
4. Migrate to Corretto before settlement. Document the migration timeline. The Corretto migration is the buyer-side leverage that resets Oracle's settlement math — once Java is removed, the back-licence claim has a defined ceiling (the period during which Oracle JDK was demonstrably installed).
5. Negotiate the settlement. Oracle's opening position rarely survives forensic challenge. We have defended Java audits where Oracle's initial $4M+ settlement proposal landed at $0 to $200k after migration, evidence challenge, and structured negotiation. 100 percent Java audit defence record in our practice.
6. Exit the Universal Subscription with written confirmation. Once migration is complete and settlement is closed, ensure the Universal Subscription is contractually terminated with Oracle confirmation. Verbal assurances do not protect against re-engagement.

Decision framework

Migrate to Amazon Corretto when:

• The organisation runs server-side Java workloads on AWS, on-premises Linux, or Windows — the standard case.
• The Employee Metric Universal Subscription cost is disproportionate to the actual Java footprint (most enterprises pay 50 to 200x more under the Employee Metric than they would under the legacy Named User Plus model for the same workloads).
• The application footprint is standard (Spring, Spring Boot, Tomcat, Jetty, WildFly, Quarkus, Vert.x, Kafka, Elasticsearch, Apache services). All of these run identically on Corretto.
• The customer has been served a Java audit letter — migration is the buyer-side leverage that resets the settlement math.
• The customer has heavy AWS estate — Corretto is the default Java distribution on Amazon Linux and is supported under standard AWS Support Plans at no additional cost.

Stay on Oracle Java SE when:

• Regulatory or contractual requirements mandate Oracle-branded Java support and the audit-evidence chain requires Oracle's commercial backing.
• The application footprint uses Oracle-specific Java commercial features at JDK 8 or earlier that require a JDK major version upgrade before any migration.
• The Employee Metric pricing has been negotiated to a level where the Universal Subscription is genuinely competitive against the migration cost plus third-party support (rare, but achievable in specific enterprise negotiations where Oracle is defending a high-value account).
• The customer has heavy Oracle Database, Oracle Cloud, or Oracle Fusion estate where the Universal Subscription is bundled at attractive cross-product pricing.

In our buyer-side practice across 600+ engagements, the right answer for over 90 percent of enterprise Java estates is the Corretto migration. The Employee Metric is structurally too punitive for organisations whose actual Java footprint does not justify it. We have defended 40+ ULAs and have a 100 percent Java audit defence record — the consistent pattern is that the migration plus structured audit defence eliminates the Java commercial exposure. For non-AWS estates, the platform-aligned alternatives are the Red Hat build of OpenJDK for RHEL/OpenShift, Microsoft Build for Azure, and the BellSoft Liberica distribution for JavaFX desktop estates or Spring Boot estates aligned to VMware Tanzu. All close the same Oracle Employee Metric exposure — the choice is operational fit. Bring the modelled cost to the Java migration ROI calculator to size the buyer-side opportunity.

Buyer-side negotiation moves

1. Inventory before any conversation with Oracle. Forensic Java inventory is the buyer-side prerequisite. Once Oracle issues an audit letter or Universal Subscription proposal, time is short. Do the inventory first.
2. Migrate before negotiating the settlement. The Corletto migration is the buyer-side leverage that resets Oracle's settlement math. A 5-week migration that eliminates Java consumption changes the negotiating dynamics fundamentally.
3. Challenge Oracle's evidence chain. Oracle's audit claims often rely on telemetry that the customer did not knowingly authorise or that is technically weak. Forensic challenge produces material settlement reductions.
4. Do not sign a Universal Subscription "to settle the audit" — settle the audit and exit Java separately. Oracle frequently positions the Universal Subscription as the audit settlement mechanism. This is a trap: the Universal Subscription locks in 3 years of Employee Metric billing in exchange for closing a back-licence claim that is often defensible. Separate the two negotiations.
5. If you do sign a Universal Subscription, cap the renewal uplift and negotiate the exit clauses. 3 percent annual cap or CPI-linked, written notice window for exit, no auto-renewal, written confirmation of contractual termination.
6. For organisations under 1,000 employees — Oracle's NFTC (No-Fee Terms and Conditions) JDK may be sufficient. Oracle ships a free JDK under the NFTC licence which allows production use under specific conditions (development, internal business operations, but no redistribution). Evaluate whether NFTC fits the use case before adopting any commercial Java distribution.
7. Document everything. The Corretto migration, the Universal Subscription exit, the audit defence evidence — all of it. This is the buyer-side insurance against Oracle re-engagement.

FAQ — Oracle Java SE vs Amazon Corretto

What is Amazon Corretto?

Amazon Corretto is Amazon's no-cost, production-ready, multi-platform distribution of OpenJDK. Available for Java 8, 11, 17, 21, 23, and onward LTS releases. Amazon commits to long-term support (LTS) with quarterly security patches: Corretto 8 supported through May 2026, Corretto 11 through October 2027, Corretto 17 through October 2029, Corretto 21 through October 2030. Corretto is binary-compatible with Oracle Java SE — applications compiled against Oracle JDK run on Corretto without recompilation. Amazon provides Corretto free of charge with no per-user licence, no Employee Metric, no audit exposure.

Is Amazon Corretto really free for commercial use?

Yes. Amazon Corretto is licensed under GPL v2 with Classpath Exception, the same licence as OpenJDK upstream. Commercial use is permitted at no cost, including in production, including in enterprise applications, including in shipped products. No Oracle Master Agreement, no Java SE Universal Subscription, no Employee Metric. Amazon provides Corretto as a strategic AWS asset to ensure no AWS customer feels locked into Oracle's Java commercial terms. Many large enterprises (financial services, retail, manufacturing, public sector) have migrated production workloads to Corretto with zero ongoing Java commercial cost.

What support does Amazon offer for Corretto?

Amazon provides Corretto with quarterly security patches and bug fixes aligned to the OpenJDK upstream cadence. Patches are released on the same schedule as Oracle's Critical Patch Updates (CPUs). Support for AWS customers running Corretto on AWS infrastructure is covered under standard AWS Support Plans (Business and Enterprise) at no additional cost — AWS support engineers are trained on Corretto issues. For non-AWS deployments, Amazon publishes the patches on GitHub and Docker Hub but does not provide a dedicated Java commercial support line. Customers needing 24/7 Java-specific support on Corretto typically procure third-party Java support from Azul Systems, BellSoft, or another commercial OpenJDK distributor.

Should we migrate from Oracle Java to Amazon Corretto?

Yes, for most workloads, particularly when (a) the customer has received an Oracle Java audit letter or sees an Employee Metric renewal proposal, (b) the customer's workloads run on AWS infrastructure where Corretto is the natural choice, (c) the customer has standard server-side Java workloads (Spring, Tomcat, Jetty, application servers) that are not coupled to Oracle-specific Java features. The migration is technically straightforward — Corretto is a drop-in replacement for Oracle JDK at the same version. The buyer-side mechanics matter more than the technical migration: ensure the Oracle Java Universal Subscription contract has been properly exited with no compliance gap, and document the migration evidence for any future Oracle audit defence.

How long does a Corretto migration take?

For a typical enterprise of 5,000 employees with 200 to 500 Java application footprints, the Corretto migration runs 4 to 8 weeks. The dependencies are: forensic Java inventory (1 to 2 weeks), pilot migration on non-production estate (1 week), production rollout in waves (2 to 4 weeks), Oracle JDK decommissioning and Universal Subscription exit (1 week). For organisations with more complex Java estates (proprietary Oracle JDK features, complex application server estates, multi-vendor legacy footprints), the timeline extends to 12 to 16 weeks.

What if Oracle sends a Java audit letter after migration?

The Corretto migration is the buyer-side defence against the back-licence claim. Once the Oracle JDK is removed from all systems, the audit defence becomes evidence-driven: Oracle must prove Oracle JDK was in commercial production use, the customer can demonstrate the migration timeline with system-level evidence, and the back-licence claim has a defined ceiling. We have defended over a hundred Java audits with a 100 percent successful resolution rate. The forensic audit defence, the Corretto migration, and the Universal Subscription exit work together as a single buyer-side strategy. For broader context on Oracle's Java audit mechanics, see our piece on Oracle Java Licensing Guide.

Independence statement: Oracle Licensing Experts is an independent buyer-side advisory firm. Not affiliated with Oracle Corporation. We have no commercial relationship with Amazon or AWS. All numbers above reflect published list pricing for Oracle Java SE Universal Subscription and benchmark migration economics as observed in buyer-side engagements.

Related guides