Expert Interview: Oracle SaaS and Cloud Services Usage

How Oracle SaaS Licensing Works

Fredrik Filipsson: Most enterprises still don't understand how Oracle SaaS licensing actually works. They think they're paying for cloud consumption. They're not. They're paying for named users or unique equipment identifiers, and the meter is often broken.

When you deploy Oracle Fusion Cloud, for example, you're buying subscriptions. But the way Oracle defines "subscription" is loose. They give you a user limit—say 500 named users—but the contract language is written so ambiguously that you end up paying for 600 because the definitions of what counts as a "user" have expanded.

Morten Andersen: The real trap is that Oracle doesn't tell you upfront what the usage baseline is. You migrate to Fusion Cloud thinking you'll save money on maintenance, and then Oracle audits you and says, "You have 5,000 monthly active users. Your contract covers 1,500. That's a $2.3M overage."

The overage isn't on the subscription price itself. It's on the ULA damages—the old unlimited licensing agreement penalty. Fusion Cloud subscriptions can be pulled into existing ULA true-ups, and enterprises end up paying 10-15 times the subscription rate for each additional user in the true-up.

The Fusion Cloud Compliance Trap

Fredrik: Fusion Cloud introduces a compliance problem that on-premise never had. When you run Oracle Applications on-premise, you have clear meter points: servers, CPUs, named users. SaaS is different.

Oracle doesn't give you real-time usage data. You don't see how many users accessed the system last month. You get a subscription bill, and if you breach the user limit, Oracle doesn't tell you—they wait for an audit, then charge you retroactively.

Morten: The worst part? Many enterprises are running Oracle Fusion in a way that causes massive overconsumption without knowing it. Common mistakes include:

• Provisioning every department member as a named user when they only need integration users (which cost 1/10th the price)
• Not using restricted users for temporary workers or contractors
• Sharing login credentials between departments (which violates the license but isn't metered)
• Running Fusion Cloud in sandbox/test environments and counting them as production users

Fredrik: The key is that Fusion Cloud consumption is not metered at runtime. You're not paying per transaction. You're paying per named user per month, and the definition of "usage" is binary: either someone has a login, or they don't.

The compliance risk comes from hidden users. Contractors end the engagement. Employees move departments. Shared accounts linger. And Oracle audits count everyone with a login, even if they haven't logged in in 18 months.

OCI and Universal Credits: The Hidden Cost Multiplier

Morten: OCI Universal Credits are one of Oracle's most aggressive upsell tactics. They position them as a way to get volume discounts on cloud infrastructure—CPU, storage, database, etc. In theory, it makes sense: buy $1M in credits, get a discount.

But here's the catch: Universal Credits commit you to a multi-year term (usually 3 years), and they don't carry over. They expire. If you buy $1M in year 1 and only use $600K, the $400K is gone.

Fredrik: And Oracle's pricing model for OCI makes it very easy to consume more than you expected. They charge per hour, per compute unit, per GB of storage. If you're not disciplined about shutting down development environments or optimizing queries, you can blow through $100K per month in OCI costs.

The real trap: enterprises buy Universal Credits thinking they'll get time to optimize. By month 18 of their 36-month commitment, they've realized they're not going to hit their credit target. Too late. They're locked in.

Morten: A more recent issue is that Oracle is pushing OCI subscriptions alongside Fusion Cloud subscriptions. They'll say, "Your Fusion Cloud license includes basic OCI storage. If you need more, add OCI Universal Credits." But the pricing of those add-ons isn't transparent, and enterprises often end up paying 2-3x what they expected.

Indirect Access: The Licensing Hole Nobody Talks About

Fredrik: This is the biggest compliance risk nobody is auditing for yet. Indirect access means accessing Oracle software through an intermediary system—a third-party app, a data integration platform, a reporting tool.

In the on-premise world, if you use Informatica to load data into Oracle Database, you need to license Informatica and all the Oracle database CPUs that Informatica touches, even if your users never directly access Oracle.

Morten: In the cloud, this gets murkier. If you integrate Fusion Cloud with Salesforce via an API gateway, are your Salesforce users "accessing" Oracle Fusion indirectly? Oracle's position: yes, and you need licenses for them.

Most enterprises don't audit for this. They'll get a surprise audit finding: "You have 2,000 Salesforce CRM users accessing Fusion Cloud via integration. License them." That's easily another $1.5M in damages.

Fredrik: The solution is transparency. Map every system that touches Oracle. Every data feed, every API call, every integration. Then work backwards from Oracle's licensing terms to figure out what you owe. It sounds tedious, but it's the only way to avoid a $3M audit bill.

Renewal Negotiation: When You Have Leverage

Morten: Oracle renewals are the only time you have real negotiating power. Not at license true-ups, not at audits—at renewal.

Here's the typical scenario: You have a Fusion Cloud subscription that expires in 90 days. Oracle sends a renewal notice at list price. Most enterprises just accept it. That's a mistake.

Fredrik: The leverage point is migration threat. If Oracle knows you could move to SAP S/4HANA, Workday, or NetSuite, they have to move on price. But you have to credibly position that threat.

Concretely: Get a competitor evaluation done before your renewal. Have quotes from SAP or Workday. Make sure Oracle knows about it (discreetly). Then enter renewal negotiations saying, "We love Fusion, but SAP is 40% cheaper and includes two years of free migration support."

Oracle will move. They don't want to lose customers to competitors. We've seen Oracle give 20-35% discounts just by credibly threatening to migrate.

Morten: The other leverage point is usage reduction. If you've over-provisioned users, show Oracle that you've audited your own user base and can cut 200 users from the license count. Now your renewal bill is lower. Oracle knows it's cheaper to retain you at a lower price than to audit you and fight over $500K in damages.

Fredrik: Bundled offerings are another angle. Oracle often gives better pricing if you combine Fusion Cloud with database subscriptions, NetSuite integration, or HCM modules. Negotiate for the bundle. Don't take the per-product pricing.

Governance: The Anti-Audit Framework

Morten: The best defense against Oracle audit findings is proactive governance. Here's what enterprise controls should look like:

1. Monthly License Reconciliation

Pull your active user list from Fusion Cloud each month. Compare it to your subscription limit. If you're trending toward a breach, you have 60 days to notify Oracle and request a "true-up light"—an interim license purchase—before the audit hammer falls.

2. Integration Mapping

Document every system that touches Oracle. For each integration, note whether it's using shared service accounts or named users. Build a compliance register. This is your defense in an audit.

3. Restricted User Classification

Don't license everyone as a named user. Fusion Cloud has restricted user licenses (much cheaper) for contractors, consultants, read-only access. Use them. It saves money and reduces your audit footprint.

4. Test Environment Separation

Oracle's contract language says you're licensed for "production use." If you have sandbox/dev environments, they shouldn't count toward your user limit. Set up separate Oracle accounts for non-production. Keep them separate.

Fredrik: The enterprises that never get audited are the ones with tight governance. They know their Oracle footprint. They're not surprised. And if Oracle does audit them, the evidence is clear: "Here's our monthly reconciliation. Here's our integration map. Here's our restricted user allocation." Oracle sees a well-run operation and backs off.

The Oracle SaaS Outlook: What to Expect in 2026

Morten: Oracle is pushing Fusion Cloud adoption aggressively. By 2026, they'll have fully deprecated on-premise Oracle ERP in most industries. The financial incentive is obvious: SaaS subscriptions are recurring revenue, and they're less transparent than on-premise licensing.

Fredrik: Expect three things:

• Tighter consumption tracking: Oracle is investing in better usage monitoring. They want to move from annual user reconciliation to real-time metering. This will reduce compliance surprises, but it will also mean more price increases as they catch hidden usage.
• Bundled pricing: Oracle will push more multi-module bundles (Fusion + Database + HCM) and penalize point-solution licensees. If you only want Fusion Cloud, you'll pay premium pricing. If you bundle, you get a discount.
• Audit escalation: Oracle is hiring more audit teams and expanding their audit criteria. Indirect access, integration risk, user classification—these will be standard audit findings by 2026. Enterprises need to be ready.

Morten: The good news: You can control this. Governance and transparency are your defense. Enterprises that own their Oracle footprint, know their integrations, and keep clean records will negotiate better terms and avoid audit surprise.

Fredrik: The takeaway is simple: Don't assume Oracle SaaS is simpler or cheaper than on-premise. It's different, and it requires different controls. Implement proper governance from day one. It will save you millions.