Salesforce Experience Cloud Pricing, Explained

Experience Cloud (formerly Community Cloud) is Salesforce’s answer to giving partners, customers, and other external users a portal without handing them full internal seats. It’s usually cheaper than a Sales or Service Cloud license — but “cheaper per user” and “cheap at scale” aren’t the same thing, and the licensing model trips people up. Here’s how it actually works.

The two Experience Cloud licensing models

Salesforce sells Experience Cloud access two ways, and which one applies depends on the edition and use case:

Login-based licenses

You buy a pool of logins and each authenticated session draws from it. This fits low-frequency users well — someone who logs in twice a month costs a lot less than someone in the portal daily. Salesforce has publicly listed login-based Experience Cloud pricing in the roughly $2–$10 per login range depending on the license type and edition (check current Salesforce pricing for your org, since these figures move).

Member-based licenses

You pay a flat rate per named external user regardless of how often they log in — closer to a traditional per-seat model, just at a lower rate than an internal seat. This suits people who use the portal regularly, since a login-based license would rack up charges fast for a daily user.

Where the cost still adds up

Both models are cheaper per person than a full internal seat, but both still scale with the number of external users or logins you have. A partner program with a few dozen partners is inexpensive; one with a few hundred partners, plus their staff, plus your customers, starts to look like a real, growing line item — because it’s still fundamentally a per-user (or per-login) meter.

Option	Typical published pricing	Scales with users?
Full Sales/Service Cloud seat	~$150–$165/user/mo	Yes
Experience Cloud (login-based)	~$2–$10 per login	Yes — per login
Experience Cloud (member-based)	Flat rate per named user, below internal-seat pricing	Yes — per user
Custom portal	One flat monthly fee	No

Prices are publicly listed ranges as of this writing, not quotes — confirm current pricing with Salesforce.

When Experience Cloud is the right call

If your external-user population is small, relatively stable, and you want to stay entirely inside declarative Salesforce tooling, Experience Cloud is a reasonable, supported option — it’s built for this and integrates natively. The tradeoff is that you’re still on a per-user (or per-login) meter, and Experience Cloud’s page layouts and components are built for general-purpose portals, not necessarily your exact workflow.

When a custom portal wins

Once the external-user population is large, growing, or needs a workflow Experience Cloud’s component set doesn’t fit well, a custom portal — synced live to Salesforce through its API — breaks the link between cost and user count entirely. It’s one flat monthly fee whether you have 50 partners or 5,000, and it’s built around your exact process rather than a general community template. We cover the full head-to-head, including the “when each wins” cases, in our Experience Cloud vs. custom portal comparison.

For the broader picture on cutting CRM costs beyond just external users, see how to cut CRM licensing costs. And if you haven’t audited your internal seats yet, start with our Salesforce license audit checklist — internal seat waste is usually the bigger number.

Frequently asked questions

Is Experience Cloud the same as a customer portal?

It’s Salesforce’s product for building one. “Experience Cloud” is the platform; the actual site or portal you build on it (customer portal, partner portal, help center) is the “experience.”

Do login-based or member-based licenses cost less?

It depends entirely on usage frequency. Infrequent users cost less on login-based pricing; daily users usually cost less on member-based pricing. Model both against your actual usage pattern before committing to one.

Can we replace Experience Cloud with a custom portal without losing Salesforce data?

Yes. A custom portal reads and writes the same Salesforce records through the API in real time — Salesforce stays the system of record either way. The difference is the front end and the pricing model, not the data.