Salesforce · Experience Cloud · 2026 Pricing
Salesforce Experience Cloud. Pricing decoded for the 2026 renewal cycle.
Member vs login vs External Apps, the hidden costs, and the buyer side moves across the Salesforce Experience Cloud renewal.
Member vs login vs External Apps, the hidden costs, and the buyer side moves across the Salesforce Experience Cloud renewal.
Salesforce Experience Cloud, formerly Community Cloud, prices on a member license and a login basis. The member model looks generous. The login model is where the bill grows.
Salesforce Experience Cloud is the publisher's portal product. Customer communities, partner portals, employee self service, and increasingly the front end of Agentforce sit on this platform. Salesforce sets out the offering on its Experience Cloud pricing page.
The 2026 posture introduced firmer discount floors, a tighter login conversion ratio, and a sharper push toward External Apps for partner volume. The combination moved the renewal math.
Read the related Salesforce knowledge hub, the Salesforce advisory practice, and the Salesforce renewal playbook for the wider negotiation framework.
Experience Cloud is the umbrella for any external facing Salesforce site. Customer portals, partner portals, learning sites, and the Agentforce front end all run on the platform.
It is technically a layer on top of Sales Cloud, Service Cloud, or both. The community sits over the same data model the core licenses use.
Member licenses are an annual seat. Each named member counts whether they log in or not. The metric is stable but expensive for sporadic users.
Login licenses are a monthly pool. Each login consumes one credit. The metric flexes, but the pool runs out fast on a high traffic site.
External Apps is a newer SKU. It targets very large partner or customer populations on a transaction or platform basis, documented in the Salesforce documentation.
Pricing varies by workload shape. The 2026 list price is higher than the legacy partner SKUs, but the per user effective rate is materially lower at scale.
Experience Cloud license types vs use case
| License type | Metric | Best fit | Risk |
|---|---|---|---|
| Member | Per named seat per year | Stable, high engagement audience | Pays for inactive users |
| Login | Per login from monthly pool | Sporadic, large audience | Overage at retail |
| External Apps | Per platform plus transactions | Very large customer or partner base | Governance complexity |
| Channel Account | Aggregate channel population | Multi tier partner programs | Edition lock at scale |
| Customer Plus | Per member with write access | Partner like external users | Role hierarchy sprawl |
Member licenses win on stable, predictable audiences with high engagement.
Pricing the member SKU only makes sense above roughly two and a half logins per user per month. Below that, the login pool is cheaper.
Login licenses win on sporadic audiences. Customer support portals, learning sites, and infrequent partner check ins all suit the login model.
The pool must be sized to handle the peak. Overage on logins is billed at retail, often double the in pool effective rate.
External Apps wins at scale. Once the audience crosses tens of thousands of monthly active users, the per user math collapses and External Apps becomes the cheapest path.
The trade off is governance overhead. External Apps needs more deliberate identity and data architecture.
The standard Salesforce account team pitch is that member licenses are the safe default and login pools are a niche option for low traffic sites. We disagree. In roughly 3 of 5 Experience Cloud estates we have rebuilt, a large block of named members logged in less than twice a month, so the member commitment paid for access nobody used. The buyer side move is to meter actual logins for one quarter, convert the idle members to a right sized login pool, and hold External Apps in reserve as the scale fallback. Members feel safe. The bill says otherwise.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Member licenses look generous on paper. Login licenses look risky on paper. The actual answer is almost always a hybrid, with quarterly conversion as the operating gate.
Each Experience Cloud edition includes an API call allocation. The allocation is per org, not per community.
High traffic portals burn through the allocation. The overage is billed at retail. The move is to inventory API usage before renewal and negotiate a top up SKU at a non retail rate.
Experience Cloud development needs Full or Partial sandboxes for any serious testing. Developer sandboxes lack the data volume to test community throughput.
The sandbox tier upgrade is rarely included in the base community license. It is a separate line on the order form.
Any analytics overlay on Experience Cloud traffic goes through Data Cloud. Data Cloud is its own SKU with its own credit model, as covered in the Salesforce newsroom.
Read the related Salesforce renewal playbook for the Data Cloud renewal framework.
Most of the value sits in the mid term operating discipline, not the renewal night negotiation. The 2026 commercial posture is reflected in Salesforce investor disclosures.
A quarterly audit of member usage, login pool draw, API call volumes, and edition mapping is the operating gate that keeps everything else honest.
Experience Cloud is the rebranded Community Cloud, the Salesforce platform for customer, partner, and employee portals. It runs on top of the core Sales or Service Cloud data model, so it shares the same records and security model.
Three principal license types set the price. Member is per named seat per year. Login is per login from a monthly pool. External Apps is a transaction based platform model aimed at very large audiences.
Below roughly two and a half logins per user per month, the login pool is cheaper. Above that, member is usually cheaper. The breakeven shifts with the edition you choose.
External Apps is a newer transaction based SKU for very large external audiences. The per user effective rate is materially lower at scale, with a higher governance and identity overhead.
Yes. API call overage, sandbox tier upgrades, and the Data Cloud overlay for analytics are separate lines that rarely sit in the base community quote. Confirm each before signing.
Yes. Discount floors tightened, the login conversion ratio moved, and Salesforce is steering partner volume toward External Apps. The renewal math has moved with it, so old benchmarks understate the gap.
Run a usage inventory, classify each segment by metric, model the External Apps fallback at scale, then benchmark the effective rate against reference rates. Meter actual logins for one quarter before you commit.
Often no. Members who log in less than twice a month usually cost less on a right sized login pool. Audit login frequency before renewing the member block.
Salesforce renewal posture, edition consolidation moves, Agentforce framework, and the buyer side moves across the full Salesforce estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
We had two thousand Experience Cloud members who logged in once a quarter. Redress converted them to a login pool, retired the sandbox tier we did not need, and capped the renewal escalator. The renewal landed twenty four percent under our model.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Experience Cloud math, Agentforce moves, edition consolidation framework, and the wider Salesforce leverage signals across the practice.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
