Oracle Alloy Licensing Guide:
What It Means for ISVs, Partners & Enterprises

What Oracle Alloy Is — and Why It Changes Licensing Fundamentally

Oracle Alloy is Oracle's infrastructure platform that allows authorised partners — typically large telcos, national cloud providers, and system integrators — to run Oracle Cloud Infrastructure (OCI) services on their own hardware, in their own data centres or sovereign cloud environments. Partners who deploy Oracle Alloy become "Oracle Cloud Operators" and can offer OCI-compatible cloud services to their own customers. Oracle Alloy became generally available in late 2022 and has since been adopted by a growing number of national and regional cloud providers globally.

The licensing implications of Alloy are significant for three distinct groups: ISVs who build and sell software on OCI and now need to understand how Alloy-based deployments affect their licence terms; enterprises whose cloud service providers have migrated to Alloy-based infrastructure; and enterprises evaluating whether to use an Alloy-based cloud versus OCI direct. Our Oracle advisory team addresses all three scenarios, and the full Oracle cloud landscape is covered in our Oracle Knowledge Hub.

How Alloy Changes BYOL Rules for Enterprise Software

Oracle's standard Bring Your Own Licence (BYOL) rules allow customers to use existing on-premises Oracle Database, Middleware, and application licences on OCI without additional cloud licence fees. These BYOL benefits apply specifically to OCI — Oracle's own cloud — and the key question Alloy creates is whether BYOL benefits extend to Alloy-based operator clouds.

Oracle's official position is that BYOL benefits apply to Alloy-based cloud services when the Alloy operator has specifically obtained authorisation from Oracle to offer BYOL-compatible services. Not all Alloy operators have done so, and the terms vary. Enterprises planning to use their existing Oracle Database Enterprise Edition licences on an Alloy-based cloud must verify the BYOL status of that specific Alloy operator before migration — and obtain written confirmation. Verbal assurances from the Alloy operator's sales team are not sufficient. For 23ai-specific BYOL considerations, see our Oracle 23ai licensing guide.

ISV Licensing Economics on Alloy

For ISVs building and distributing Oracle-based software, Alloy creates a new dimension of licensing complexity. When an ISV's customers run the ISV's application on an Alloy-based cloud, the Oracle Database or Middleware licences that underpin the ISV's application need to be accounted for correctly — either through the ISV's existing licence terms, the Alloy operator's licence terms, or the end customer's own Oracle licences.

Oracle's ISV programme rules distinguish between ISVs that embed Oracle technology in their applications (typically governed by Oracle Application Specific Full Use or ASFU licences) and ISVs that simply recommend Oracle as a supported platform. The Alloy environment adds a third party — the Alloy operator — to this chain, and the contractual clarity around where the Oracle licence obligation sits between ISV, Alloy operator, and end customer is frequently inadequate in early-stage Alloy deployments. ISVs who have not updated their terms of service to address Alloy-based customer deployments carry meaningful compliance risk.

What Enterprises Running on Alloy-Based Infrastructure Need to Know

For enterprises whose cloud service providers have adopted Oracle Alloy, the licensing considerations are practical and immediate. The most important questions to resolve are: Does the Alloy operator's service agreement include Oracle licence coverage for the Oracle components you are using, or are you expected to BYOL? If BYOL, does the operator's Alloy deployment qualify for Oracle's BYOL benefit, and can they provide Oracle-signed documentation confirming this? What are the audit rights — specifically, if Oracle conducts a licence audit, is the Alloy operator the audit target or is the enterprise?

Enterprises operating in regulated industries — financial services, healthcare, government — often have data sovereignty requirements that make Alloy-based national cloud providers attractive. These organisations should ensure that the data sovereignty benefit of the Alloy deployment is not undermined by licence compliance ambiguity. For related Oracle commercial topics, our Oracle NetSuite pricing guide covers Oracle's SaaS estate, while our ULA guide addresses how Alloy deployments interact with ULA certification. To discuss your specific Alloy situation, book a confidential advisory call.