What BYOL means.
Bring Your Own License is the Oracle commercial model that permits a buyer with existing on premise Oracle licenses to redeploy those licenses on a public cloud platform without purchasing new licenses. The available cloud destinations include Oracle Cloud Infrastructure, Amazon Web Services, Microsoft Azure, and Google Cloud Platform. Each cloud destination has its own conversion rules, supported product list, and metering methodology.
BYOL is different from a cloud first deal where the buyer purchases Oracle Database Cloud Service or similar product directly from Oracle on a subscription basis. BYOL preserves the perpetual license model on the buyer side and uses the cloud as an infrastructure platform. The license cost has already been paid. The cloud cost is incremental compute and storage.
Why BYOL matters.
For a buyer that already owns Oracle licenses, BYOL is the lowest cost path to running Oracle workloads in the cloud. The license cost is sunk. The annual support cost continues. The cloud cost is the marginal compute and storage rate for the chosen platform. The total cost of ownership is materially lower than a fresh cloud subscription purchase.
BYOL also preserves optionality. Licenses redeployed under BYOL can be redeployed back to on premise infrastructure if the cloud strategy changes. Licenses purchased through a cloud subscription cannot. This optionality has commercial value that is not always recognised at the deal negotiation stage.
Conversion ratios.
The conversion from on premise license to cloud entitlement varies by cloud destination and by product family. For Oracle Database deployed on OCI, the standard conversion is one processor license to two OCI OCPUs for Enterprise Edition. For Oracle Database deployed on AWS or Azure, the conversion under the cloud licensing policy is one processor license to two virtual cores. The conversion under the older AMC policy can differ for legacy contracts.
These conversion ratios are policy and not contract. Oracle reserves the right to change the conversion ratios with notice. The ratios in effect at the time of deployment are the ratios that apply. Buyers entering a multi year cloud strategy should consider negotiating contract terms that lock the conversion ratio for the duration of the engagement.
The support question.
BYOL preserves the on premise support contract. The annual support fee continues to be billed against the original perpetual license. The cloud platform support, including OCPU availability, storage performance, and network reliability, is provided by the cloud platform operator. Oracle product support remains an Oracle responsibility through the existing support contract.
When a license is redeployed from on premise to cloud, the support cost does not decrease. This is a common buyer misperception. The support cost is calculated against the license inventory, not against the deployment location. The cloud cost is therefore an addition to the existing on premise support cost, not a substitution for it.
Common BYOL pitfalls.
The first common pitfall is assuming that a ULA grants automatic BYOL rights to cloud deployments. The default ULA contract language does not extend deployment rights to OCI, AWS, or Azure. Cloud BYOL rights inside a ULA require explicit contract language that must be negotiated at the ULA entry stage. Buyers that try to add cloud rights mid term face very poor leverage.
The second common pitfall is mis counting cloud deployments at audit. Oracle license management services has specific methodology for counting OCPUs, virtual cores, and hyperthreaded environments in cloud destinations. A buyer that applies on premise counting rules to a cloud deployment will under report the entitlement consumption and face an audit finding.
The third common pitfall is failing to negotiate the audit access terms. The default cloud contract permits Oracle to request deployment evidence from the cloud platform operator. The buyer should negotiate the audit methodology to require sampling against buyer maintained records, not full disclosure from the cloud operator. This is a process protection that has commercial implications.
The fourth common pitfall is ignoring the egress cost. Buyers that move from one cloud platform to another, or back to on premise, face egress fees that can be substantial. The egress fee structure should be evaluated at the BYOL entry stage and should influence the choice of cloud destination.
What we do.
Our BYOL engagements cover the contract terms, the conversion ratio negotiation, the support cost analysis, the cloud platform selection guidance, and the audit defence positioning. We do not provide cloud architecture or implementation advice. The technical implementation of the cloud platform is the responsibility of the buyer system integrator or internal team. Our scope is the commercial structure and the contract language that supports it.
BYOL engagements typically run six to ten weeks. The discovery phase covers the current license inventory and the planned cloud deployment topography. The negotiation phase covers the contract amendment that grants BYOL rights with the desired commercial terms. The handover phase covers documentation of the negotiated terms and a thirty day question and answer period after signature.
Related resources.
- Cloud Migration Advisory service covers the broader cloud strategy and contract work.
- OCI Universal Credits for the alternative cloud subscription path.
- Oracle Database product page for Database specific BYOL considerations.
- The Negotiation Playbook 58 page white paper.
- Cloud Negotiation blog cluster with tactical articles.