OS and database licensing in the cloud: the cost that isn't in the machine price
OS and database licensing in the cloud is the cost of licensing the operating system and the database, and it is almost never in the machine price the calculator shows.
Diego Aron Gomes
Direct answer
OS and database licensing in the cloud is the cost of licensing the operating system and the database, and it is almost never in the machine price the calculator shows. The server price, vCPU, memory and disk, is the visible part. The license for a Windows Server or a SQL Server comes after, often charged per core and in dollars, and it can double the monthly bill. There are two models: license included in the price, or BYOL, when you bring a license you already own. Knowing which one you pay for, and in which currency, is what separates a budget that holds from one that blows up.
Contents
OS and database licensing in the cloud: what goes into this cost
It is an airline ticket with a baggage fee. On the search page, the fare looks cheap. Then baggage, seat selection and taxes come in, and the final price is another number.
A cloud machine works the same way. What the calculator shows is the hardware: how many processor cores, how much memory, how much disk. That is the ticket price. The operating system license and the database license are the baggage and the fees. They do not appear in the big number on the shelf, but they land on the invoice.
So what? Because that second line is usually not small. A server with Windows Server and SQL Server can carry a license cost that rivals the hardware itself, sometimes more. If you budget only the machine, the number you closed in the meeting does not match the one on the bill.
Here is the point: the machine price is the visible part, licensing is the line that doubles the bill the next month. Treat the license as a detail and you find out late.
What costs a license and what is free
Not everything charges a license. Worth separating before you decide.
On the operating system:
-
Windows Server charges a license. It is proprietary software.
-
Open source Linux distributions do not charge a usage license. What can cost is an enterprise support subscription, when you choose to have one.
On the database:
-
SQL Server and Oracle charge a license, usually per core and per edition. This is where the bill grows the most.
-
PostgreSQL, MySQL and MariaDB are open source, with no usage license. They can also have a paid edition or enterprise support, if you opt in.
The practical read: you can cut the license line a lot by choosing open software, when the application allows it. When it requires a proprietary database or system, the license becomes part of the project, not an extra, and it has to enter the budget from the start.
Two models: included license vs BYOL
Once you contract the cloud, the proprietary license arrives in two ways.
Included license. The provider bundles the operating system and database licenses into the price. You pay a single number, with no separate license to buy, no compliance to track, and it scales with usage. The compute cost comes a bit higher because the license is inside, but it is predictable.
BYOL, short for bring your own license. You use licenses you already bought. The machine price drops, because you pay only for the hardware. In return, you have to own valid licenses, meet the license mobility rules, manage compliance and answer for audits. And every license left unused is money sitting idle.
Optidata works with the first model: OS and database licenses included in the fixed price in reais, with no separate line. If you already own your database license, you can bring it: at Optidata, the database is what comes in as BYOL. The operating system license stays included, so you use what you already paid for on the database without having to manage the system one.
When each model makes sense
Prefer an included license when
-
You want a predictable cost, a single number on the invoice.
-
The team is lean and does not want to manage license contracts and audits.
-
The workload grows or varies, and you want the license to follow without repurchasing.
-
You have no spare licenses of your own, or you are not sure they have mobility.
Prefer BYOL when
-
You already own valid licenses, with mobility rights up to date.
-
Someone is there to manage compliance and answer audits.
-
The workload is stable and known, so the purchased license does not sit idle.
Where the license weighs most
-
Proprietary databases in a high edition. SQL Server or Oracle Enterprise raise the bill fast, and per core.
-
Large machines. The license is per core, with a minimum charged per machine. On a small VM you pay that floor anyway. Above it, adding processor raises the license in the same proportion.
-
A license charged in dollars. Every time the currency climbs, the line goes up without you touching anything.
Included license vs BYOL: comparison table
| Criterion | Included license | BYOL (bring your own license) |
|---|---|---|
| How you pay | License built into the machine price | License you already bought, on the side |
| Compute price | Higher (the license is inside) | Lower (hardware only) |
| Predictable total cost | Yes, a single number | Depends, you add license plus compute |
| Currency exposure | Depends on the provider (at Optidata, priced in reais) | Depends on where and how you bought the license |
| Compliance and audit | On the provider | On you, with mobility rules |
| Idle license | Does not exist, you pay per use | Risk of paying for a license that sits idle |
| Best for | Whoever wants simplicity and predictability | Whoever already has a license with mobility and knows how to manage it |
Note: both models are legitimate. The choice depends on whether you already own licenses with mobility and how much energy you want to spend managing that.
How to read the bill before you sign
- Ask for the machine price and the license price separately. If they come as a single number, ask how much is license.
- Check the currency of each line. Compute and license can be in different currencies, and the license in dollars is the one that surprises.
- Check the database edition. Editions differ a lot in cost, and there are entry level options that are far cheaper for specific scenarios. See whether the application really uses the features of the expensive edition.
- Add up what surrounds the license: DBA hours, patching, support, traffic and IO. These are lines that come on the side with some providers.
- If it is BYOL, confirm mobility and compliance before, not after. An audit does not warn you.
Once that is done, compare by total cost, not by machine price. It is the only comparison that holds at the end of the month.
Pros and cons of each model
Included license
For: a single number, predictable, no separate purchase, no compliance to track, scales with usage. Against: you do not reuse a license you already have, and the license premium is built into the price.
BYOL
For: uses a license you already bought and lowers the compute price. Against: it requires mobility up to date, compliance management and audit risk, and you pay for an idle license.
Where the fixed price comes in
Licensing bundles two FinOps problems into one place: a line that was not in the machine price, and a currency you do not control.
An included license, on its own, does not solve it. Several providers offer that. What really changes the bill is what stays outside it: which currency the license is charged in and which fees run in parallel.
At Optidata, the operating system and database licenses go into the fixed price in reais, with no separate line, no charge for inbound and outbound traffic and no IO charge. That takes the license out of the dollar's swing and turns licensing into a predictable cost, locked in the contract. In the managed database, the MySQL, MariaDB, PostgreSQL, SQL Server and Oracle engines run with high availability, automatic backup and patching handled by the team.
In practice, add the license to the budget and it stops being next month's surprise.
FAQ
What is OS and database licensing in the cloud? It is the cost of licensing the operating system and the database that run on the server, separate from the hardware price (vCPU, memory, disk). Proprietary systems and databases, like Windows Server and SQL Server, require a license. That amount usually does not show in the machine calculator and lands on the bill later.
Do Linux and PostgreSQL have a license? Open source Linux distributions and databases like PostgreSQL, MySQL and MariaDB do not charge a usage license, they are open source. What can cost is an enterprise support subscription or a paid edition, when you opt in. You can cut the license line a lot by choosing open software, if the application allows it.
What is BYOL and is it worth it? BYOL is bringing a license you already own to run in the cloud, instead of paying for one included in the price. It pays off when you already have valid licenses, with mobility rights, and the discipline to manage compliance. The risk is audits, mobility rules and paying for a license that sits idle. At Optidata, BYOL applies to the database: if you already own the database license, you bring yours, and the operating system one stays included.
Why does licensing weigh so much on the bill? Because proprietary licenses are usually charged per core and per edition, with a minimum per machine, so scaling the server multiplies the license. If the charge is in dollars, the currency swing comes in too. Adding it all up, the license can approach the cost of the hardware itself or go past it.
Do SQL Server editions differ much in cost? Yes, the difference is large. Enterprise weighs far more than Standard, and there are entry level editions, cheaper, that fit specific scenarios. Before choosing, check whether the application really uses the features of the expensive edition. Many companies pay for Enterprise using only what a smaller edition would deliver.
How does Optidata charge for OS and database licenses? At Optidata, the operating system and database licenses come included in the fixed price in reais, with no separate line. There is no charge for inbound and outbound traffic and no IO charge. Licensing becomes a predictable cost, locked in the contract, with no extra line and no dollar swing.
Before you close a cloud budget, add the license, not just the machine. Optidata includes OS and database in the fixed price in reais, with no line on the side. Talk to an Optidata specialist.
About the author: [VALIDATE], [role] at Optidata. Works with cloud and database architecture for operations in Brazil.