BYOL stands for “bring your own license.” Oracle BYOL allows our customers to apply licenses they currently own for on-premises software for equivalent, highly automated Oracle PaaS. Previously, Oracle BYOL could only be used for IaaS. With this program, customers can leverage their existing on-premises licenses with 100 percent workload compatibility and license mobility, helping you reach business value faster.
Learn more about Oracle BYOL, Universal Credits program, and license mapping rules (PDF).
Oracle’s current PaaS offering is license-included PaaS, which offers:
Oracle BYOL to PaaS includes:
Customers bring their on-premises license entitlement and get license support via their existing on-premises support contract. As customers leverage their existing on-premises license entitlement, they can move to the cloud at a lower cost.
Yes. You have complete license mobility between on-premises and the public cloud and Oracle Cloud@Customer.
The mapping rules are defined in the Oracle PaaS and IaaS Universal Credits Service Description document (PDF).
At a high level, one Oracle Processor License maps to two OCPUs. Refer to the above document for more details.
No. There are cloud-only services that have no on-premises analog. Some examples of this are: Oracle Mobile Cloud, Oracle API Platform Cloud Service, Oracle Internet of Things Cloud Service, and Oracle Visual Builder Cloud Service.
These services are only available as license-included PaaS, as there are no on-premises license entitlements to bring to the cloud.
The mapping rules are defined in the Oracle PaaS and IaaS Universal Credits Service Description document (PDF).
At a high level, one Oracle Processor License maps to two OCPUs. Refer to the above document for more details.
No. There are cloud-only services that have no on-premises analog. Some examples of this are: Oracle Mobile Cloud, Oracle API Platform Cloud Service, Oracle Internet of Things Cloud Service, and Oracle Visual Builder Cloud Service.
These services are only available as license-included PaaS, as there are no on-premises license entitlements to bring to the cloud.
Customers can use their credits to provision and burn down credits against license-included PaaS services or Oracle BYOL to PaaS services.
Yes.
Yes.
Yes. For more details, visit the Upgrade from Oracle Database Standard Edition to Oracle Autonomous Database page.
No, the two cannot be mixed in the same instance.
The same capability exists with one significant difference. With Oracle BYOL to PaaS, customers must bring a license entitlement from on-premises to the cloud. So if a customer has many unused licenses available on-premises, they can scale up or down to match demand, provided they have the appropriate number of BYOL entitlements.
It depends on the architecture. If the customer can scale horizontally by adding new instances, then they can start new instances with license-included PaaS.
However in many situations, they need to scale an instance vertically by adding more cores to the instance,—the database in particular. In this case, you can’t mix Oracle BYOL to PaaS with license-included PaaS in the same instance. They must either be all Oracle BYOL to PaaS cores, or all license-included cores.
Yes. When a customer brings an Oracle Database Enterprise Edition license entitlement to Oracle PaaS, they are granted the rights to use Diagnostics Pack, Tuning Pack, Data Masking and Subsetting Pack, and Real Application Testing without having on-premises license entitlements for those database options.
No, these entitlements are only granted to customers who use BYOL to PaaS.
No.
Plug your information into the Cost Estimator.