SAP Analytics Cloud license cost: user or capacity pricing. Measure concurrency before you choose.

SAP Analytics Cloud offers a user based and a capacity based model. The right choice depends on your concurrency profile, whichever one the account team leads with.

What are the SAP Analytics Cloud licensing models?

SAP Analytics Cloud offers a user based model, priced per named user, and a capacity based model, priced on consumption and concurrent activity. The two are not interchangeable, and the right one depends on how your audience actually uses the tool.

SAP describes the product on its SAP Analytics Cloud product pages, which sit within the wider SAP Business Technology Platform. The prices and metrics that bind you are in the order form, and that is where the model decision gets locked in for the term.

The user based model

• Priced per named user. Every person assigned a license carries a cost, whether they log in daily or twice a year.
• Split by license type. SAC tenants assign Business Intelligence, Planning Standard and Planning Professional licenses to users, and each type carries its own price.
• Easy to budget. When the population is stable, the invoice is simple to forecast.
• Hard on casual audiences. A seat opened once a month costs the same as a power user's seat.

The capacity based options

Capacity pricing in SAC deals shows up in two forms, and they behave differently. Check which one your quote or current contract actually contains before you compare it with a named user price.

• Concurrent session licenses for BI. You hold a number of simultaneous Business Intelligence sessions, sized to peak activity. SAP now describes these as legacy licenses and sells new SAC subscriptions per named user, but tenants that already carry sessions can still assign BI users to them.
• Capacity units in SAP Business Data Cloud. You buy a pool of capacity units, and each SAC user type draws a set number of units per month. Users are still counted, but the rate falls as volume rises.
• Planning stays named. SAP's own guidance is that every planning role consumes a named user license, and only Business Intelligence licenses can be concurrent.

If your contract still carries concurrent sessions, treat them as the most valuable line in it. If they lapse at a renewal, expect SAP to quote named users or BDC capacity units in their place.

Where is the break even between SAC user and capacity pricing?

The break even sits at the ratio of total named users to peak concurrent users, read against the price of a session relative to a named user. When the ratio is high, with a large audience and few people in the tool at once, capacity pricing wins. When it is low, user pricing wins.

Headcount on its own tells you little. A 2,000 person audience with 150 peak concurrent users behaves very differently from 2,000 daily active analysts, and the two belong on different models. The SAP Analytics Cloud documentation sets out how consumption is measured under the capacity model.

How to compute the break even

1. Count named users. Everyone who would need access, grouped by license type.
2. Measure peak concurrency. The most users active in one window, taken over a period that includes month end and quarter close.
3. Add headroom. Size sessions above the measured peak so a busy morning does not lock people out.
4. Price both quotes. Ask SAP to price the same user population under each model, on the same term and the same discount basis.

A worked example with hypothetical prices

Say you have 1,200 SAC users: 200 analysts who build stories most days and 1,000 viewers who open a dashboard a few times a month. Your contract carries concurrent sessions, and at renewal SAP proposes named users for everyone. Assume $500 per named BI user and $2,000 per session, each per year, as placeholders for your own quote.

Your viewers peak at 120 at once, and you add 20 percent headroom, which gives 144 sessions, rounded to 150. Your analysts peak at 160 of 200 during the working day.

At these prices, one session costs as much as four named users. Once you add 20 percent headroom, sessions win for any group where fewer than about 21 percent of its members are online at the busiest moment. Here the $200,000 gap is what keeping the sessions is worth when SAP proposes the conversion.

How are SAC licenses priced inside SAP Business Data Cloud?

Inside SAP Business Data Cloud, you pay for SAC users with capacity units, and each user type consumes a fixed number of units per month. The per user rate drops in tiers as your user count grows, which changes the break even for large audiences.

SAP's own April 2026 pricing overview for the public SAC option in BDC Core sets the Business Intelligence rates below. Planning Standard runs from 72.85 units per user per month at 10 to 200 users down to 41.57 at 1,001 users or more.

Two points follow for your quote. The unit tables tell you consumption, while the price you pay per capacity unit is set in your contract, so negotiate that rate as its own number. And because the pool is shared with Datasphere and other BDC services, see our Datasphere licensing guide before you size it.

How does your concurrency profile drive the SAC decision?

Your concurrency profile is the share of your named audience that is active at the busiest moment. A low share favors capacity pricing, because concurrent sessions are sized to the busiest moment only. A high share favors user pricing, because the peak approaches the headcount anyway.

Most reporting heavy user bases have far lower concurrency than their owners assume. That is why capacity pricing is so often the cheaper answer for a broad audience, and so often overlooked. SAP product updates on the SAP Analytics Cloud news channel change feature scope, so revisit the model as the product evolves.

What to measure first

• Active window. When usage actually peaks during the day and across the month.
• Peak share. Concurrent users as a fraction of named users, for each group.
• Audience type. Analysts and planners who build content versus viewers who only consume it.
• Dormant seats. Named users with no login in the last 90 days, who should come off the count before either quote.

How to check your own usage in SAC

You can measure this from the tenant itself. The System Overview shows how many licenses of each type are assigned and in use. The Administration Cockpit reports user activity and content usage over time, which is where you find your real peak.

For the user list, export users from the Security area. The export carries an IS_CONCURRENT field that shows which BI users already sit on concurrent sessions. If single sign on runs through your identity provider, its sign in logs give a second, independent count of who logs in and when.

Why we would not default to named users for easy budgeting

The account team usually advises named users because the invoice is simple to budget. We disagree for broad audiences. In roughly 15 to 25 SAC decisions we advised across 2024 and 2025, groups with a large casual audience and peak concurrency under 20 percent were materially cheaper on capacity, often by 30 to 50 percent.

The user model charges the same for a daily analyst and a monthly viewer, which penalizes exactly the broad reporting audiences SAC is sold to serve. Measure real concurrency first, price your users under both models, and choose on the evidence instead of the simpler invoice.

What have we seen in recent SAP Analytics Cloud decisions?

Across roughly 15 to 25 SAP Analytics Cloud licensing decisions that Morten Andersen and the team advised on in 2024 to 2025, the model choice moved total cost more than the discount did. Three patterns came up again and again.

• Named users by default. Buyers chose user based pricing even when peak concurrency was below 20 percent of the named population, and left the capacity savings unclaimed.
• Viewers licensed as full users. Casual and read only audiences were licensed as full named users, which inflated the cost of the user model by 30 to 50 percent.
• Unit cost hidden in bundles. When SAC was bundled into a larger SAP agreement, its standalone unit cost was invisible in 4 out of 5 of the agreements we reviewed.

On SAP Analytics Cloud, the simpler invoice and the cheaper invoice are rarely the same one.

How do you cut SAP Analytics Cloud cost in a larger SAP deal?

Get SAC priced as its own line, with license type, quantity and unit price shown separately, and compare that line with a standalone quote for the same users on both models. Then negotiate SAC on its own metric, even when the rest of the deal is priced as a package.

When SAC rides inside a RISE, BDC or wider SAP agreement, its per user cost is folded into a blended total. You then have nothing to compare at renewal and no clean way to cut quantities, and viewers stay licensed on the same terms as analysts.

What the account team will say, and what to say back

• "Named users keep it simple." Reply that simple is fine once you have seen the capacity price for the same users, and ask for both quotes on the same term.
• "Analytics is already discounted inside the bundle." Ask for the SAC unit price and user count as separate order form lines, so the discount can be checked against a standalone quote.
• "Concurrent sessions are legacy, so we will move you to named users." Ask SAP to price the conversion so total SAC spend does not rise, or to renew your current session quantity at the current rate. Bring your own version of the worked example to that meeting.
• "Capacity units give you flexibility across BDC." Agree, then ask for the unit price per capacity unit to be fixed for the full term, since flexibility is worth little if the rate can rise.

Contract terms to ask for

• A separate SAC line. License type, quantity and unit price shown on their own, so the next renewal starts from a visible number.
• Your existing sessions, in writing. If you hold concurrent BI sessions, state their quantity and renewal price in the order form, so a renewal cannot drop them by default.
• A price hold by license type. Fixed unit prices for BI, Planning Standard and Planning Professional through the term, plus a cap on the renewal uplift.
• A reduction right. The ability to cut quantities at renewal when adoption falls short of the plan.
• A fixed capacity unit rate. For BDC deals, a contracted price per unit and a written consumption table for SAC user types.

For the wider negotiation, our SAP Analytics Cloud negotiation guide covers pricing benchmarks and timing.

When should you revisit your SAC licensing model?

Revisit it at every renewal. Concurrency profiles drift as adoption grows, so the model that fit at first signature may not fit when the term ends. Measuring concurrency again each cycle keeps the model matched to real use.

Common mistakes that raise the SAC bill

• Measuring in a quiet month. A sample outside close periods understates the peak, and the shortfall appears as lockouts or a mid term top up.
• Giving viewers planning roles. Any planning role consumes a named user license, so a stray role assignment turns a session user into a named one.
• Comparing quotes on different terms. A capacity quote on three years and a user quote on one year are not comparable, whatever the headline.
• Treating BDC capacity units like sessions. In Business Data Cloud each counted SAC user draws units every month, whether or not they are online at the peak, so a low concurrency share does not shrink that bill. Clear dormant users out before the count is set.

What to do next

1. Measure first. Record peak concurrent usage and total named users across a representative period before choosing a model.
2. Ask for two quotes. Request both a user based and a capacity based quote from SAP for the identical user population.
3. Compute the break even. Work from the ratio of named users to peak concurrency, not from headcount alone.
4. Unbundle. Take SAP Analytics Cloud out of any larger bundle so its standalone unit cost is visible.
5. Match model to audience. License broad casual audiences on capacity and focused analyst teams on the user model where that fits.
6. Negotiate on the chosen metric. Agree the price on the model's own metric and refuse a blended bundle price.
7. Measure again at renewal. Adoption drift can flip which model is cheaper, so repeat the count each cycle.

Frequently asked questions