Most Salesforce clouds are not separate products. Sales Cloud, Service Cloud and the industry clouds such as Health Cloud are licenses and features switched on inside one Salesforce org. That means one managed package can serve all of them. Marketing Cloud Engagement, B2C Commerce and Tableau are different. Each runs on its own platform with its own app model, so a vendor ships a second deliverable to reach them.
That split decides what a SaaS company builds when enterprise customers ask for a native Salesforce app. Your buyers will own different combinations of clouds, and the app has to install cleanly in all of their orgs. Appnigma's marketplace apps offering is built for this ("Your product, inside Salesforce or HubSpot."). It covers the native app, listing preparation and review support, built by ex-Salesforce engineers. If you are an admin choosing which clouds to buy, Salesforce's own products page is the better starting point.
Updated October 2026. Checked against the Salesforce DX scratch org features list, the ISVforce packaging pages, the Marketing Cloud Engagement and B2C Commerce developer guides and the Health Cloud object reference. The earlier version treated every cloud as one platform, described a Health Cloud object that doesn't exist, and used retired product names. This update sorts the clouds by where they run, and it shows how one package handles customers whose orgs have different clouds.
Which Salesforce clouds run inside the customer's org
The cleanest test is the Salesforce DX scratch org features list, the file a package is built against. Every cloud in the table below appears there as a feature flag of an ordinary org. Sales Cloud "Provides a license for Sales Cloud features," and Health Cloud "Enables use of Health Cloud." A cloud on that list is something your package can see, query and extend from inside the org.
| Cloud | Where it runs | Scratch org feature | What gates its objects | Learn more |
|---|---|---|---|---|
| Sales Cloud | Customer's Salesforce org | SalesUser | Sales Cloud license | Sales Cloud |
| Service Cloud | Customer's Salesforce org | ServiceCloud | Service Cloud license | Service Cloud |
| Experience Cloud | Customer's Salesforce org | Communities | Site licenses, configured as "Communities" | Experience Cloud |
| Health Cloud | Customer's Salesforce org | HealthCloudAddOn | Health Cloud permission set license | Health Cloud |
| Financial Services Cloud | Customer's Salesforce org | FinancialServicesUser | FSC permission set license | Financial Services Cloud |
| Nonprofit Cloud | Customer's Salesforce org | Fundraising | Nonprofit Cloud licenses | Nonprofit Cloud |
| Field Service | Customer's Salesforce org | FieldService | Field Service license | |
| Revenue Cloud | Customer's Salesforce org | CoreCpq | Revenue Cloud licenses | |
| B2B Commerce | Customer's Salesforce org | B2BCommerce | B2B Commerce license | Commerce Cloud |
| Data 360 (formerly Data Cloud) | Customer's Salesforce org | CustomerDataPlatform | Data 360 license | |
| Agentforce | Customer's Salesforce org | Einstein1AIPlatform | Agentforce and Einstein licenses |
Objects in the industry clouds are gated by license, not hidden in a separate system. Health Cloud's EngagementInteraction page states that "The Health Cloud permission set license is required to use this object." For a vendor this is the useful fact. Your package reads Account, Contact, Case and Opportunity in every org, but a Health Cloud object only exists where that license does.
Two data models trip vendors up. Health Cloud has no Patient object, because "Patients are modeled using Person Accounts," per the Health Cloud FHIR mapping. Financial Services Cloud can carry two layers in the same org. Package objects use the FinServ namespace, while newer standard objects "have the same API version as core Salesforce," according to the Financial Services Cloud Developer Guide. A vendor serving FSC customers has to decide which model to read, or detect both.
The clouds that run on their own platform
Marketing Cloud Engagement is the one most often mislabeled. Apps there are not managed packages. Salesforce says to "Create an installed package to create API integrations, install custom apps, or add custom Journey Builder components," in the Marketing Cloud Engagement install guide. API access needs "a client ID and secret, obtained from the Installed Packages page," per the Engagement API overview.
"Marketing Cloud" also now names three products. Salesforce's Marketing Cloud Next getting started page says Marketing Cloud Next, Marketing Cloud Engagement and Marketing Cloud Account Engagement "use different APIs that aren't compatible with each other." Before you scope a build, ask the customer which one they run. Appnigma's Marketing Cloud integration guide walks through each case.
B2C Commerce is separate as well. "Business functionality in B2C Commerce is organized in cartridges," per the B2C Commerce cartridges page, and each customer has its own B2C Commerce instance. B2B Commerce, by contrast, runs in the org on the B2BCommerce license.
The AppExchange listing types make the split official. Select an AgentExchange Listing Type offers separate types for a platform package, a B2C Commerce cartridge and a Tableau Accelerator. It also offers API listings for "Salesforce Platform API, Marketing Cloud Engagement API, or Headless Integration for B2C Commerce." The same page warns "You can't change the listing type after it's created," so pick the model before you build.
| Customer runs | What you ship | Listing type |
|---|---|---|
| Any core cloud (Sales, Service, industry clouds) | Managed package (2GP) | Packaged Solution |
| Marketing Cloud Engagement | Installed package or API integration | Marketing Cloud Engagement API |
| B2C Commerce | Cartridge or headless API integration | B2C Commerce Cartridge or Headless Integration |
| Tableau | Tableau Accelerator | Tableau Accelerator |
AppExchange itself has changed name. Salesforce's AgentExchange install guide says "We've unified AppExchange, AgentExchange, and Slack Marketplace into a single destination." The AgentExchange explainer covers what that means for a listing.
Can one AppExchange app work across all Salesforce clouds?
Across the core clouds, yes, if it is packaged for it. Across Marketing Cloud Engagement or B2C Commerce, no, because those need their own deliverable. The risk inside core is a hard dependency. Salesforce's dynamic Apex packaging page warns that a strongly typed reference to a feature the customer lacks "will cause the installation to fail."
The 1GP dependencies page puts the rule plainly. "An installer's organization must meet all dependency requirements listed on the Show Dependencies page or else the installation fails." Put a lookup to a Health Cloud object in your package, and every Sales Cloud only customer hits an install error before seeing your product.
Salesforce's own worked example shows a second cost. On the Work.com packaging page, adding those dependencies to a base package means "you also introduce a Workplace Command Center add-on license requirement for your base package users." A cloud reference can turn into a license your customer must buy just to install you, which slows the deal.
How to package one product for customers with different clouds
Start with the build definition. The 2GP scratch org definition page says the file passed to package version create specifies "the features, settings, or limits that your package requires." Every feature listed there becomes something your package may depend on, so keep the base definition to what every customer has.
Then pick one of the two documented patterns.
One package with dynamic Apex. "It's possible to create one managed package for all editions you plan to support without having to use extension packages," per the dynamic Apex packaging page, and "if your customer doesn't have a specific feature or object, your app will still function." The code checks whether the object exists before touching it.
// Read Health Cloud care plans only in orgs that have them
Schema.SObjectType carePlanType = Schema.getGlobalDescribe().get('CarePlan');
if (carePlanType != null && carePlanType.getDescribe().isAccessible()) {
List<SObject> plans = Database.query(
'SELECT Id, Name, Status FROM CarePlan WHERE ParticipantId = :accountId LIMIT 50'
);
}The object name lives in a string, so the package carries no hard reference to CarePlan, whose fields are listed in the Health Cloud object reference. The catch is declarative metadata. The Work.com page warns that "flows, reports, and triggers, without using Apex InvocableMethod annotation" still create hard dependencies.
A base package plus extension packages. The base holds what every customer gets. Each extension holds the cloud-specific parts and installs only where that cloud exists. "Any component that references the base-managed package automatically triggers this package to be an extension package," per the ISVforce extension package page, and "Upgrading a customer only requires installing the extension package." In 2GP you declare the base in sfdx-project.json, as the 2GP dependencies page describes.
| Situation | Better fit |
|---|---|
| Cloud features are a few reads and writes in Apex | One package with dynamic Apex |
| Cloud features need flows, page layouts, reports or custom fields on cloud objects | Base plus extension package |
| You want to price the cloud features as an add-on | Base plus extension package |
| Data 360 metadata is involved | Separate package with a data kit (required) |
Data 360 is not optional. "Starting in Winter '25, including both Data 360 metadata, and non-Data 360 metadata in a single package isn't allowed," per Salesforce's Packages and Data Kits page. The metadata goes into a data kit inside its own package.
This is the part where vendors lose weeks. Appnigma's integration infrastructure is built for "Different customers. Different requirements." Your engineers keep one integration and handle per-customer differences, such as which clouds an org has, without forking the code.
What the listing and security review say about clouds
The listing is where you tell buyers which clouds you need. The AgentExchange Listing Builder asks you to "Select any required Salesforce products that customers need and any compatible products." A package that works in any core org and adds Health Cloud features with an extension should list Health Cloud as compatible, not required.
Security review follows the solution, not the cloud. How the AgentExchange Security Review Works covers "managed packages, Salesforce Platform API solutions, or Marketing Cloud Engagement API solutions." So a managed package plus a Marketing Cloud Engagement integration is two solutions, each with its own review. One managed package serving five core clouds is one solution.
Mistakes that break a multi-cloud Salesforce app after install
- A lookup to an industry object in the base package. Every customer without that cloud gets an install failure.
- A flow or report on a cloud-specific object. Dynamic Apex in your classes doesn't help if declarative metadata still references the object.
- Querying a Patient object in Health Cloud. It doesn't exist. Patients are person accounts, which is its own org setting.
- Reading only FinServ objects in Financial Services Cloud. Newer orgs may use the standard objects instead.
- Treating Marketing Cloud as one product. Engagement, Next and Account Engagement have incompatible APIs.
- Mixing Data 360 metadata into the main package. It must ship in its own package through a data kit.
- Building on retired features. "Social Studio was retired on November 18, 2024," per the SocialEngagement class reference.
Frequently Asked Questions
How many Salesforce clouds are there?
Salesforce doesn't publish a fixed count, and its products page groups them by area and industry. For a vendor, the useful split is two groups. Most clouds, including Sales, Service and Health Cloud, run inside an org. A few are separate platforms, such as Marketing Cloud Engagement, B2C Commerce and Tableau.
Is Marketing Cloud on the same platform as Sales Cloud?
Marketing Cloud Engagement is not. It uses its own installed packages and API credentials. Marketing Cloud Next runs with org records, and Salesforce says the three Marketing Cloud products use APIs that aren't compatible with each other.
Does a managed package need every cloud the customer might own?
No. Build against a scratch org definition that lists only the features every customer has. Then reach cloud-specific objects with dynamic Apex or an extension package.
Is Community Cloud the same as Experience Cloud?
Yes. Experience Cloud is the current name, and its configuration still uses the term Communities, per the scratch org features list.
Can Appnigma build one Salesforce app that works across our customers' clouds?
Yes. Appnigma's marketplace apps offering delivers the managed package, listing preparation and security review support. For integrations, the done-for-you service ("Build your product. We'll build the integrations.") assigns a named engineer, which covers a second build for Marketing Cloud Engagement.
Related Articles
- What is a managed package in Salesforce
- Building a native Salesforce app
- Salesforce Marketing Cloud integration guide
- What is Salesforce AppExchange, now AgentExchange
- Governor limits in verified managed packages
Sources
- Salesforce Developers, Salesforce DX Developer Guide, Scratch Org Features
- Salesforce Developers, Health Cloud Object Reference, EngagementInteraction
- Salesforce Developers, Health Cloud Object Reference, Patient FHIR mapping
- Salesforce Developers, Health Cloud Object Reference, CarePlan
- Salesforce Developers, Financial Services Cloud Developer Guide, API Access and Usage
- Salesforce Developers, Marketing Cloud Engagement, Create and Install Packages
- Salesforce Developers, Marketing Cloud Engagement API References
- Salesforce Developers, Get Started with Marketing Cloud Next
- Salesforce Developers, B2C Commerce, Cartridges
- Salesforce Developers, ISVforce Guide, Select an AgentExchange Listing Type
- Salesforce Developers, What Is AgentExchange?
- Salesforce Developers, ISVforce Guide, Supporting Multiple Editions using Dynamic Apex
- Salesforce Developers, First-Generation Managed Packaging, Package Dependencies
- Salesforce Developers, Work.com Developer Guide, Package Your Work.com Solution
- Salesforce Developers, Second-Generation Managed Packaging, Scratch Org Definition Files vs Org Shape
- Salesforce Developers, ISVforce Guide, Supporting Multiple Editions Using an Extension Package
- Salesforce Developers, Second-Generation Managed Packaging, Create Dependencies Between 2GP Managed Packages
- Salesforce Developers, Data 360 Developer Guide, Packages and Data Kits
- Salesforce Developers, ISVforce Guide, Get To Know the AgentExchange Listing Builder
- Salesforce Developers, ISVforce Guide, How the AgentExchange Security Review Works
- Salesforce Developers, Apex Reference Guide, SocialEngagement Class
- Salesforce, Products