Oracle MOSA vs MCA. The contract vehicles compared.

Oracle MOSA and MCA are two master agreements that govern different halves of the estate, on premises licensing under MOSA and cloud services under MCA, and most enterprises hold both.

This guide is for legal and procurement leaders untangling Oracle agreements in 2026. Read it with the cloud licensing policy guide and the Oracle Practice page so the contract structure and the licensing rules line up.

What are the two Oracle master agreements?

Oracle places enterprise buying under master agreements that set standing terms. Two masters cover most estates, one for licensing and one for cloud.

What does the MOSA govern?

The Master Oracle Software and Hardware Agreement governs on premises programs, hardware, and support. Every traditional license order sits beneath it as an ordering document.

• Licenses: perpetual and term programs on premises.
• Hardware: engineered systems and servers.
• Support: the technical support tied to those licenses.

What does the MCA govern?

The Master Cloud Agreement governs Oracle cloud services. Its terms cover consumption metrics, service levels, and data handling that the on premises master does not address. Oracle publishes both under its contracts library.

How do MOSA and MCA differ in practice?

The split is by estate, not by vendor. What you are buying decides which master applies, and many deals touch both.

Why do enterprises hold both?

Because most run both estates. On premises database and middleware sit under MOSA while OCI and SaaS sit under MCA, so a single enterprise carries orders under each.

What happens in a combined renewal?

A bundled deal splits. The license lines fall under MOSA and the cloud lines under MCA, so read both masters before signing a combined renewal.

How do you negotiate the master terms?

The master is where the leverage is highest, because it governs years of future orders. The standing terms are negotiable for enterprise buyers.

Which terms matter most?

Audit, assignment, and termination language matter most. They decide your exposure long after the signing meeting, so settle them at the master, not at the order.

What to do next

1. Identify which master governs each Oracle agreement you hold.
2. Map every order document to its parent master.
3. Read the audit and assignment terms in each master.
4. Split any combined renewal into its MOSA and MCA lines.
5. Negotiate standing terms before the next order, not after.
6. Keep a single register of masters, orders, and terms.

Frequently asked questions

What is the difference between Oracle MOSA and MCA?

MOSA is the master agreement that governs on premises software and hardware licensing, while MCA is the master agreement that governs Oracle cloud services. They cover different parts of the estate, and most enterprises that run both on premises and cloud hold both agreements at once.

What does the Oracle MOSA cover?

The Master Oracle Software and Hardware Agreement covers perpetual and term licenses for on premises programs, hardware, and the technical support that sits on them. It is the umbrella under which ordering documents for traditional Oracle licensing are placed.

What does the Oracle MCA cover?

The Master Cloud Agreement covers Oracle cloud services, including OCI consumption and SaaS subscriptions. Its terms address service levels, data handling, and consumption metrics that do not appear in the on premises MOSA.

Do you need both MOSA and MCA?

If you run both on premises Oracle and Oracle cloud, then yes, you typically hold both. The agreement that applies depends on what you are buying, so a single enterprise often has ordering documents under each master at the same time.

Which agreement governs an Oracle cloud commitment?

The MCA governs Oracle cloud commitments. When a renewal bundles cloud with on premises licensing, the cloud lines fall under the MCA terms and the license lines under the MOSA, so read both before signing a combined deal.

Can you negotiate the master agreement terms?

Yes. Both masters contain terms that are negotiable for enterprise buyers, including audit, assignment, and termination language. The master sets the defaults for every future order, so the time to negotiate it is before the first order, not after.