Analytics Legends logoAI & Analytics Legends Sign inSign up
Guide

SAP Business Data Cloud pricing: what is public and what is not

As of 2026-11-07

SAP does not publish a list price for Business Data Cloud, and any page quoting one is quoting a market estimate dressed as a tariff. What SAP does publish is the mechanism, and the mechanism is where the money goes: BDC is sized and billed in capacity units, a bundled measure of compute, memory, storage allotment and data-flow throughput sold in tenant-sized blocks. SAP's service description guide lists the capacity-unit value of each service, and SAP points buyers to its official capacity estimator in the SAP Discovery Center for sizing. The answerable question is not what it costs but what drives the number.

What is public, and what is not

Public: the unit of account and its composition, the capacity-unit values per service in SAP's service description guide, the workload types drawing against the pool, and the monitoring surface that reports consumption after go-live. That is enough to build a sizing model you can defend in front of a finance stakeholder.

Not public: the price of a capacity unit, the entry price of a tenant, the discount curve, the overflow rate past the storage allotment, and the pass-through rate for the embedded Databricks capacity. None of those are inferable from the mechanism, and every euro figure circulating for BDC is somebody's estimate — usually derived from a handful of deals and quoted without the workload profile that produced it.

This changes how a proposal should read. Quote a single number without the workload breakdown and you set up the worst version of the conversation a year later: a customer who never saw the build-up assumes they were oversold, while one who did can see which workload grew.

What one capacity unit buys

A capacity unit is an accounting unit, not a bundle of fixed resources. SAP's service description guide (v10-2026, § 2.3.5 and Table 2) gives each capacity service its own unit of measure and value: memory-optimised Datasphere compute is 0.570 capacity units per 16 GB of memory per hour, disk storage 0.004 per 16 GB per hour. Usage is measured at its highest point in the month, and unused units do not carry over.

Because each service has its own value, the same budget trades differently by workload: a memory-hungry, low-throughput planning model consumes in a different shape than a replication-heavy integration workload with modest memory needs. The practical consequence is that memory usually binds for in-memory analytics, not vCPU count — a sizing conversation anchored on processor cores prices the wrong variable and will under-provision a planning-heavy tenant.

On the entry point, SAP's documents differ. Its presentation of 16 April 2026 cites a minimum of 640 capacity units as the smallest viable implementation, an Analytics Cloud tenant with 25 business intelligence users at 25.60 units each. That figure is not in the service description guide v10-2026, whose clause 6.3.2 gives the Customer-Managed Data Products service an increase of 1,000 capacity units a month. Beyond that, SAP publishes no fixed tenant floor; size with the official capacity estimator in the SAP Discovery Center.

The six workloads competing for one pool

Live SAP Analytics Cloud queries running federated push-down spike hardest at peak business hours. Replication flows draw a sustained, predictable load. Analytic-model evaluation consumes at query time and scales with concurrent users. Joule grounding queries are individually cheap and multiply with active users. Knowledge Graph traversal is moderate per query and infrequent. Databricks-side cluster spin-up bills inside Databricks and still shows against the pool.

The line most sizing exercises miss hides inside the fourth: Joule agents consume capacity whenever they run, not only when a user asks a question, so a model that starts counting at the first question undercounts. Measure the agent load in a pilot rather than assume it.

One configuration trap looks like a capacity shortage and is not. Replication parallelism defaults to eight threads per flow; multiplied across dozens of concurrent flows it saturates the input/output allotment while compute still has headroom.

Decision table: average or peak

Batch-only overnight processing, nobody watching a screen during the spike. Average-based sizing is defensible — the queue costs nothing anyone experiences.

Any live, business-hours interaction: month-end close, a Friday planning cycle, an executive dashboard. Size to peak with a buffer. When a spike exceeds provisioned capacity the tenant queues rather than fails, which is worse for users than a clear error because it simply looks slow.

A peak the business watches while it runs. Size to peak and say so in writing; the credibility cost of a platform that slows exactly when it matters lands on whoever wrote the proposal.

A proposal under commercial pressure. Publish the peak alongside the average. Average-based sizing produces the more attractive figure and systematically under-provisions, because real enterprise usage is not smooth.

A worked example, and the gap it exposes

Use SAP's own rate card rather than an invented number. In the service description guide v9-2026, memory-optimised Datasphere compute is 0.570 capacity units per 16 GB of memory per hour. Four 16 GB blocks held for a 730-hour month are 4 × 0.570 × 730, about 1,664 capacity units, before storage, integration or any SAC user is added.

Read together, the conclusion is useful: compute held around the clock dominates a small tenant, and peak concurrency, not average use, decides how much compute must be held. Quoting a minimum package as sufficient for a business-hours peak is not a small optimism but a dated capacity crisis.

That is the argument for showing the derivation. A customer who sees the rate card, the compute held and the peak it serves understands why the quote is not the minimum, and procurement moves from "why is this above the minimum" to "which workload drives the peak", which both sides can act on.

The costs outside the capacity line

Federation first. Querying an external Snowflake warehouse, an Iceberg lake or an external Databricks workspace live consumes compute on the source platform, billed by that platform. A federation-heavy design can look cheap in the SAP model and expensive on the other invoice, and nothing in the capacity conversation surfaces it.

The same asymmetry runs the other way: every query a Databricks consumer runs against a shared SAP data product consumes reading-side compute. Pipeline elimination is a saving in engineering effort, not in run cost.

Then the labour. Provisioning source data as governed data products is the long pole on most implementations, especially on brownfield estates carrying years of custom fields and inconsistent master data. That is a project cost, not a platform cost, and it belongs in the same business case.

What to ask for in writing

The capacity block being quoted, and the workload breakdown behind it — which of the six consumers was assumed, at what volume. A quote without its derivation cannot be re-argued when the workload changes.

The monitoring and chargeback surface: consumption is reportable per space on a rolling thirty-day basis, which is what lets a platform team attribute cost rather than socialise it.

What happens at the ceiling — queue, throttle or burst, and on what terms. Elastic bursting has been signalled on the roadmap rather than settled commercially, so treat availability as a question to confirm rather than an assumption to price on.

And whether any element is a pass-through from a partner platform, since that portion behaves differently and may sit under a separate contract entirely.

SAP Business Data Cloud pricing 2026: the consultant cost around the capacity line

SAP publishes no capacity-unit price, but the people cost around it is observable. Our band-model median for a Business Data Cloud consultant is €760 a day for France at senior level, as of 19 October 2026, and our rates study forecasts 1.15 to 1.60 times the plain BW/SAC baseline, which is €1,093-1,520 in Germany. No survey measures that cell yet, so it is a forecast. On 13 August 2026 the live corpus held 127 Business Data Cloud postings out of 2,343, 55 of them in Germany. Provisioning source data as governed data products is a project cost, and it belongs in the same business case as the capacity block.

What we cannot assert

We state no price for Business Data Cloud, because SAP publishes none: no per-capacity-unit rate, no entry price, no discount curve, no overflow rate and no Databricks pass-through rate. Capacity-unit values come from SAP's service description guide v9-2026; SAP's April 2026 presentation (640 units) and guide v10-2026 (clause 6.3.2, 1,000 units) give different entry figures that we cannot reconcile, and sizing goes through its official capacity estimator.

Frequently asked

Is there a published price list for SAP Business Data Cloud?

No. SAP publishes the capacity-unit model and the tenant minimum, not a rate card. Any specific euro figure you find is a market estimate from a small number of deals, usually quoted without the workload profile that produced it — which is what makes it unusable for sizing your own tenant.

What is the smallest tenant I can buy?

SAP's documents differ. Its presentation of 16 April 2026 cites 640 capacity units as the smallest viable implementation, 25 business intelligence users at 25.60 units each. The service description guide v10-2026 does not contain that figure; its clause 6.3.2 gives the Customer-Managed Data Products service an increase of 1,000 units a month. For anything larger, SAP publishes no fixed floor; size with the official capacity estimator in the SAP Discovery Center.

Does the capacity price include the Databricks lakehouse?

In the packaged model the lakehouse is pre-provisioned and billed through SAP, so there is no separate Databricks contract for it. What SAP does not publish is the pass-through rate, so you cannot derive from the capacity model what that portion costs against a direct agreement.

Why is my quote larger than the minimum package?

Because a minimum package is not a sizing. Compute held around the clock dominates the bill: four 16 GB blocks of memory-optimised compute for a month are about 1,664 capacity units on SAP's rate card. Ask for the workload breakdown and the peak behind the block.

Can I see which team is consuming the capacity?

Yes. Consumption is reported per space on a rolling thirty-day window from the tenant monitor, which is the basis for internal chargeback. Setting it up before go-live is what stops a platform team owning a bill it cannot attribute.

SAP Business Data Cloud pricing: why is a quote above the minimum package normal?

Because the minimum package covers 25 business intelligence users and nothing else. Compute, storage, integration and peak concurrency all add capacity units at the values in SAP's service description guide. Ask for the workload breakdown behind the block.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

External sources

Read next

Alert me to new SAP Business Data Cloud missions

No account needed. We first ask you to confirm by e-mail; nothing is sent without that confirmation, and every alert has a one-click unsubscribe link. Privacy

Better answers on this site

Pages here that answer these searches more directly:

Open missions

56 live roles and contracts in SAP Business Data Cloud right now — see the SAP Business Data Cloud missions · freelance SAP contracts.