The meter under the subscription

The ownership page covered what Oracle’s managed analytics gives you. This one covers what it costs to run. The price is not one line: a subscription over a managed database and analytics service whose consumption you also pay, plus a second instance to customize.

RulePrice the whole meter: the subscription, the managed database and analytics consumption beneath it, and the second instance customization needs.

Neverbudget from the subscription line alone. The consumption underneath scales with use and cadence, and the customization instance is a separate bill.

The subscription is the line you see. The consumption underneath it, and the second instance to customize, are the ones you learn about later.

◆ The meter, not the licensewhat it costs to run, not what you own.

The ownership page covered what Oracle’s managed analytics gives you and does not. This one covers what it costs to run, because the price is not one line. It is a subscription sitting on a managed database and an analytics service whose consumption you also pay, and, the moment you customize, a second managed database beside the first.

That layering is why the bill surprises. The subscription is quotable; the consumption underneath scales with use and refresh cadence; and the customization instance is a cost most teams meet only after they have committed. Figures below are practitioner-reported, since Oracle does not publish a clean all-in price.

◆ The layers of the meterwhat each one bills for, and why it is hard to predict.

Layer	What drives it	Why it is hard to predict
The subscription	Licensed by users or pipeline. The visible, quotable line.	The only predictable layer; the rest are metered underneath it.
The managed database	Compute per hour and storage on the autonomous warehouse the product runs on.	Scales with data volume and query load; autoscaling makes the monthly figure a moving target.
The analytics service	The reporting layer’s own compute and user metrics.	Consumption you pay whether or not it is bundled clearly in the quote.
The customization instance	A second managed database required to extend the delivered content.	A cost that appears only when standard content stops being enough, which is most deployments.
Refresh and scaling	How often pipelines run, and the compute they burn doing it.	Cadence changes the compute bill, and the two are billed apart.

The pattern rhymes with the other cost pages this catalog documents: a headline price over a consumption meter the customer cannot easily read. Practitioner-reported throughout.

◆ The owned answer, and the trilogycommodity storage and compute, attributable to the query.

An owned warehouse meters two things you can read: storage and compute, each attributable to the query that spent it, on infrastructure you control and can right-size. There is no per-user layer, no separate instance to customize because customization is just more of your own model, and no headline price hiding a consumption bill underneath.

This completes the cost trilogy: the same managed-meter versus owned-warehouse comparison this catalog makes for SAP Datasphere and Workday Prism. Three vendors, three metered analytics products, one alternative that prices like the storage and compute it actually is. When the delivered content fits and the volume is modest, the managed product can be the right call; past that, the meter is the argument for owning it.

Use case

Problem

Fusion Data Intelligence is budgeted from its subscription, while the managed-database consumption and the customization instance beneath it surface as later, harder-to-predict bills.

What we build

The full meter mapped, practitioner-reported, then the owned warehouse that bills only attributable storage and compute you can right-size.

What you get

A cost you can read and predict, no per-user layer or second instance, and customization that is just more of a model you already own.

What is the whole meter under your analytics subscription?

We build the owned warehouse that prices like the storage and compute it is.

Talk to us

Terms on this page

SAP: The vendor of S/4HANA, whose Datasphere is the sibling cost page in the trilogy.
ERP: Enterprise resource planning, the source Fusion Data Intelligence reports on.
FDI: Fusion Data Intelligence, Oracle’s managed analytics warehouse for Fusion.
ADW: Autonomous Data Warehouse, the managed database the product runs on.
OAC: Oracle Analytics Cloud, the reporting service layer.
OCI: Oracle Cloud Infrastructure, where the compute and storage are metered.
subscription: The licensed, quotable line, over the metered consumption beneath it.
consumption: Compute and storage billed by use, apart from the subscription.
customization instance: A second managed database required to extend delivered content.