Oracle / Analytics
Oracle Analytics Cloud. The complete licensing guide.
Oracle Analytics Cloud bills by the OCPU hour or by named user. The meter runs whether anyone logs in or not. Read the model before the next universal credits true up.
Oracle Analytics Cloud bills by the OCPU hour or by named user. The meter runs whether anyone logs in or not. Read the model before the next universal credits true up.
Oracle Analytics Cloud bills by the OCPU hour or by named user. The OCPU meter runs while the instance is up, regardless of logins, which is where most overspend hides.
OAC offers two metrics. You pick one per instance.
The OCPU metric charges per Oracle Compute Unit per hour the instance runs, as defined in the Oracle Analytics Cloud documentation. It suits variable or large user populations where a per user count would be expensive.
The Named User metric charges per provisioned user per month. It suits small, stable analyst teams. Oracle lists both on the Oracle Analytics Cloud product page.
OAC comes in editions that gate features. Pick by capability, not by default.
Oracle Analytics Cloud metrics and editions in 2026
| Choice | Metric | Best for | Watch out for |
|---|---|---|---|
| Professional Edition | OCPU per hour | Core reporting and dashboards | Minimum OCPU floor |
| Enterprise Edition | OCPU per hour | Data modeling and advanced analytics | Higher per OCPU rate |
| Named User | Per user per month | Small fixed teams | Dormant accounts |
| Analytics Server | Per processor or NUP | On premises estates | Full option licensing |
Confirm edition features and current rates against the Oracle Cloud price list, which Oracle updates over time.
Oracle Analytics Server is the on premises build. It licenses per processor or Named User Plus, like a traditional Oracle product, and can be a better fit for fixed, steady workloads.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Because the OCPU meter runs on uptime, not usage. An idle instance still bills.
Non production instances rarely need to run overnight or at weekends. A stop schedule can cut development and test credit burn by more than half.
Auto scaling sizes the instance to current demand instead of a quarterly peak. Without it, you pay peak capacity every hour.
The common advice is to buy a generous annual universal credits commitment up front to lock in the best discount rate. We disagree. In roughly 6 out of 10 OAC estates we reviewed, the committed pool was larger than real consumption, so the discount was applied to credits that expired unused, which is a worse outcome than a smaller commit at a slightly higher rate. The buyer side move is to instrument actual OCPU hours for a full quarter first, apply stop schedules and auto scaling, and only then size the commitment to measured demand plus a modest buffer. A discount on credits you never burn is not a saving.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The OAC meter does not care whether anyone logs in. It cares whether the instance is running. Fix uptime before you negotiate the rate.
Yes, in defined cases. Bring your own license applies existing analytics entitlements to lower the cloud rate, under the Oracle Cloud pricing model.
Bring your own license can double count if the on premises deployment stays live. Retire the source workload, or you pay twice.
Oracle Analytics Cloud offers two metrics: OCPU per hour and Named User per month. You choose one per instance. OCPU suits large or variable audiences, while Named User suits small fixed analyst teams.
The OCPU meter charges for uptime, not logins. An instance left running overnight or at weekends still bills. Idle non production instances are the most common source of unexpected cost.
Yes. Apply a stop schedule to non production instances and turn on auto scaling. Together these often remove a third or more of credit consumption before any rate or edition change.
Oracle Analytics Cloud is the subscription service billed through universal credits. Oracle Analytics Server is the on premises equivalent, licensed per processor or Named User Plus. Steady fixed workloads sometimes fit the on premises model better.
Yes, in defined cases. Existing on premises analytics entitlements with active support can lower the cloud rate. The risk is double counting if the on premises deployment stays live, so retire the source workload.
Professional Edition covers core reporting and dashboards. Enterprise Edition adds data modeling and advanced analytics at a higher rate. Choose by the features you use, not by the default, and confirm rates on the Oracle Cloud price list.
Yes. The Named User metric charges per provisioned user per month regardless of activity. Leavers and dormant accounts keep consuming the metric until they are removed, so trim the list regularly.
Not before measuring consumption. A discount on credits that expire unused is worse than a smaller commitment at a slightly higher rate. Instrument actual usage for a quarter, then size the commitment to demand.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
