Short answer: Oracle Fusion analytics licensing is sold per Hosted Named User per month, in tiers tied to the size of your Fusion Cloud subscription. The price bundles a prebuilt Autonomous Data Warehouse and Oracle Analytics Cloud instance — but only for Oracle's packaged content. Custom data and ad-hoc querying consume extra OCI credits Oracle bills separately.

Oracle Fusion Analytics Warehouse (FAW) — rebranded by Oracle as Oracle Fusion Data Intelligence — is a packaged analytics application that sits on top of your Fusion Cloud ERP, HCM, SCM, and CX data. It ships with prebuilt data pipelines, a curated data model, and ready-made dashboards. Because Oracle markets it as "included infrastructure," buyers routinely underestimate what Fusion analytics licensing actually costs once real usage starts. The list rate is only one of three cost layers, and the other two are where audit exposure and budget overruns appear.

This guide draws on buyer-side advisory work across enterprise Fusion deployments and gives you the forensic, evidence-based view Oracle's sales team will not volunteer: how the metric is defined, where the included capacity ends, and what an achievable negotiated price looks like in 2026.

Key Takeaways

  1. Fusion Analytics Warehouse is licensed per Hosted Named User per month, sold in user-count tiers — not per query, per dashboard, or per CPU.
  2. List pricing typically runs $90–$175 per user per month; negotiated enterprise rates commonly land at $35–$80 for committed multi-year volume.
  3. The bundled Autonomous Data Warehouse and Oracle Analytics Cloud capacity covers only Oracle's prebuilt content — custom subject areas and external data sources burn extra Universal Credits.
  4. Across buyer-side Fusion engagements, roughly 1 in 3 Fusion Analytics deployments exceeds its included OCI capacity within 18 months, triggering an unplanned credit true-up (Oracle Licensing Experts, 2026).
  5. Oracle measures active users and OCI consumption through cloud telemetry, so over-deployment surfaces automatically at renewal as a back-charge.
  6. The single biggest cost lever is right-sizing the user tier before signature; Oracle's default proposal over-counts full analytics users versus casual viewers.

What is Oracle Fusion Analytics Warehouse?

Oracle Fusion Analytics Warehouse is a prebuilt, subscription analytics application that extracts data from Fusion Cloud applications into a managed Autonomous Data Warehouse and exposes it through Oracle Analytics Cloud dashboards. In plain terms: it is Oracle's "analytics-in-a-box" for Fusion, where Oracle owns the data pipeline, the warehouse schema, and the starter content. You consume it; you do not build the plumbing.

This matters for licensing because the product blends three things Oracle normally sells separately — the analytics application (FAW/FDI), the warehouse (Autonomous Data Warehouse), and the BI engine (Oracle Analytics Cloud). The subscription bundles them, which is convenient until you outgrow the bundle and the components start metering independently.

How is Oracle Fusion analytics licensing metered?

Oracle Fusion analytics licensing is metered per Hosted Named User per month. A Hosted Named User is a uniquely identified individual authorized to access the Fusion Analytics service, regardless of how often they log in. Oracle sells these users in pillar-specific packages — ERP Analytics, HCM Analytics, SCM Analytics, and CX Analytics — and in volume tiers, so the per-user rate drops as committed user counts rise.

Crucially, the metric counts authorized users, not concurrent users. If you provision 800 employees with access "just in case," you owe for 800 — even if only 120 ever open a dashboard. This is the same trap buyers hit with Fusion application user metrics, and it is the first place a forensic review finds savings. For the broader picture of how Oracle counts hosted users versus employee metrics, see our breakdown of Oracle Fusion user metrics.

Hosted Named User vs. consumption metrics

A persistent point of confusion: the application layer (FAW user subscriptions) is licensed per named user, but the infrastructure layer (the underlying ADW and OAC capacity) meters on consumption when you exceed the bundle. So a single deployment can be simultaneously over-licensed on users and over-consuming on credits. Treating these as one number is how organizations lose control of the bill.

How much does Oracle Fusion Analytics cost in 2026?

List pricing for Fusion Analytics generally falls between $90 and $175 per Hosted Named User per month before discount, varying by pillar and tier. ERP and SCM analytics sit at the top of the range; HCM and lighter "viewer" tiers sit lower. After negotiation, committed multi-year enterprise deals commonly land between $35 and $80 per user per month. The table below reflects benchmarked ranges from buyer-side Fusion engagements.

Oracle Fusion Analytics indicative pricing by pillar (2026)
Analytics PillarUser TypeList / User / MonthTypical Negotiated
ERP AnalyticsFull analyst$140–$175$60–$85
SCM AnalyticsFull analyst$140–$175$60–$85
HCM AnalyticsFull analyst$110–$150$45–$75
CX AnalyticsFull analyst$110–$150$45–$75
Any pillarViewer / consumer$30–$60$12–$30

The viewer tier is the most underused lever in the entire model. Most organizations need a small core of analysts who build and a large population who only consume. Mapping that pyramid before signature — rather than buying full users for everyone — routinely cuts Fusion analytics licensing by 30–50% against Oracle's opening proposal.

Fusion Analytics Benchmark Review

Oracle's first Fusion Analytics quote almost always over-provisions full users and under-discloses the OCI credit exposure. Our advisors benchmark your proposed or live contract against what comparable enterprises actually pay — and show you the achievable number.

Get a Pricing Benchmark →

Does Fusion Analytics include OAC and ADW for free?

Partly — and this is the most expensive misunderstanding in Fusion analytics licensing. The subscription bundles a defined slice of Autonomous Data Warehouse storage and Oracle Analytics Cloud capacity sized for Oracle's prebuilt content. That included envelope is real, but narrow. The moment you add custom subject areas, ingest external (non-Fusion) data sources, build heavy custom semantic models, or run sustained ad-hoc querying, you consume OCI capacity beyond the bundle, and Oracle bills the overage in Universal Credits on top of your per-user subscription.

This is the compliance gap that surprises buyers at renewal. Across our Fusion engagements, roughly one in three deployments exceeds its included OCI capacity within 18 months (Oracle Licensing Experts, 2026), and because Oracle tracks consumption through cloud telemetry, the overage is already documented when the true-up conversation begins.

The hidden cost stack

Cost layers in a Fusion Analytics deployment
Cost LayerWhat It CoversBilling Basis
FAW user subscriptionApplication access, prebuilt contentPer Hosted Named User / month
Included OCI envelopeADW + OAC capacity for packaged contentBundled (capped)
Overage / custom workloadsExternal data, custom models, ad-hoc loadUniversal Credits (consumption)
Oracle Integration CloudNon-standard data ingestion pipelinesSeparate subscription
Annual escalationStandard contractual uplift3–5% per year unless capped

Fusion Analytics vs. OBIEE vs. Oracle Analytics Cloud

Buyers frequently conflate these three, and Oracle's sales motion does little to clarify the distinction. OBIEE (Oracle Business Intelligence Enterprise Edition) is on-premises analytics licensed per processor or Named User Plus. Oracle Analytics Cloud (OAC) is a general-purpose cloud BI platform you build on yourself, licensed per user or per OCPU. Fusion Analytics Warehouse is a packaged SaaS application that runs on OAC and ADW but ships Oracle-built data models specifically for Fusion. Different products, different metrics, different negotiation levers. If you are weighing OAC as an alternative, our analysis of Oracle Analytics Cloud licensing covers that path in detail.

Can Oracle audit your Fusion Analytics usage?

Yes — and the mechanism differs from a classic on-premises audit. Oracle does not need LMS scripts here; the SaaS platform reports active-user counts and OCI consumption automatically. If your active Hosted Named Users exceed your contracted tier, or your credit burn outruns your entitlement, Oracle has the evidence ready and raises it at renewal as a true-up. The defense is proactive: monitor active users against entitlement monthly, track credit consumption against the included envelope, and reconcile before Oracle does. For the wider compliance discipline this sits inside, our Oracle audit guide walks through building an evidence-based internal position.

How to negotiate Fusion analytics licensing

Treat Fusion Analytics as a line item with its own leverage, not a rounding error bundled into the Fusion suite deal. The highest-value tactics buyers achieve in 2026:

  • Right-size user tiers — split analysts from viewers and refuse to pay full-user rates for a consumer population.
  • Cap annual escalation at 0–2% in exchange for a multi-year term, instead of Oracle's standard 3–5%.
  • Lock the OCI envelope — negotiate a defined included credit pool in writing and a known overage rate, so consumption surprises are bounded.
  • Ramp pricing — defer full user counts until rollout actually reaches each business unit, rather than paying for day-one over-provisioning.
  • Renewal protection — secure renewal price caps and data-export rights so you are not held hostage at the term boundary.

For end-to-end help structuring these terms, our Oracle contract negotiation service runs the Fusion analytics line alongside the broader suite deal. You can also see a real outcome in our client case studies, where right-sizing and escalation caps cut a Fusion subscription materially below Oracle's opening number.

For the full Fusion Cloud picture this article connects to, start with our pillar Oracle Fusion Cloud licensing guide, and return to the Oracle Licensing Experts home page for the full library of buyer-side resources.

Frequently Asked Questions

How is Oracle Fusion Analytics Warehouse licensed?

Oracle Fusion Analytics Warehouse (now branded Oracle Fusion Data Intelligence) is licensed per Hosted Named User per month, sold in user-count tiers tied to the size of your underlying Fusion Cloud subscription. The license bundles a prebuilt Autonomous Data Warehouse and Oracle Analytics Cloud instance, so you do not separately buy those components for the packaged content.

Does Fusion Analytics include OAC and ADW for free?

The bundled Autonomous Data Warehouse and Oracle Analytics Cloud capacity is included only for Oracle's prebuilt content. The moment you add custom subject areas, external data sources, or heavy ad-hoc querying, you consume OCI capacity beyond the bundle and Oracle charges Universal Credits on top of the per-user subscription.

Is Fusion Analytics the same as OBIEE or OAC?

No. OBIEE is on-premises analytics, Oracle Analytics Cloud is a general-purpose cloud BI platform licensed per user or OCPU, and Fusion Analytics Warehouse is a packaged SaaS application that runs on OAC and ADW with Oracle-built data models for ERP, HCM, SCM, and CX. The three are licensed and priced differently.

How much does Oracle Fusion Analytics cost per user?

List pricing typically runs $90 to $175 per Hosted Named User per month before discount, depending on the pillar and tier. Negotiated enterprise rates commonly land between $35 and $80 per user per month for committed multi-year volume, and dedicated viewer tiers fall well below that.

Can Oracle audit Fusion Analytics usage?

Yes. Oracle measures active Fusion Analytics users and OCI consumption through cloud telemetry, not LMS scripts. Exceeding your contracted user tier or Universal Credit pool triggers true-up charges at renewal, so monitoring active-user counts and credit burn against your entitlement is essential to avoid back-charges.

What is the biggest hidden cost in Fusion analytics licensing?

OCI consumption overage. The included infrastructure envelope only covers Oracle's prebuilt content; custom models and external data sources burn Universal Credits separately. Negotiate a defined included credit pool and a fixed overage rate in the contract to keep this layer bounded.

By Daniel Mercer — former Oracle LMS Consultant, 20+ years in Oracle licensing and cloud subscription analysis. Reviewed by Sarah Whitfield, Oracle Licensing Advisor. We are independent, buyer-side advisors. About our team →
25+ years expertise 600+ engagements $1.8B Oracle spend advised 38% avg cost reduction 100% buyer-side Former Oracle insiders

Oracle Licensing Experts is not affiliated with Oracle Corporation. All pricing data is based on independent advisory experience and benchmarked enterprise engagements.