Differences Between Developing Apps on Data 360 and the Salesforce Platform

Data 360 Developer Guide, mirrored from developer.salesforce.com: Check out the tools and APIs that are available for custom app development in Data 360, and compare them to those available in the Salesforce Platform.

markdownreferencev1DB2A-72FJguide: data-cloud-devstage: referencetrust: officialsource: developer.salesforce.comservice: data360interface: restinterface: sqlDifferences Between Developing Apps on Data 360 and the Salesforce PlatformData 360Data CloudData 360 Developer Guide

Created 23 Oct 2026 · Modified 23 Oct 2026 · 1 version

Mirror of <https://developer.salesforce.com/docs/data/data-cloud-dev/guide/app-dev-comparison.html> (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers.

Differences Between Developing Apps on Data 360 and the Salesforce Platform

Check out the tools and APIs that are available for custom app development in Data 360, and compare them to those available in the Salesforce Platform.

TaskData 360Salesforce Platform
Customer developers: Migrate metadata from one org to anotherUse one of these packaging features or APIs. Unmanaged packages Second generation managed packages Data kits DevOps Center Data 360 Metadata API Salesforce Metadata APIUse one of these features or APIs. Unlocked packages Unmanaged packages DevOps Center Scratch Orgs * Salesforce Metadata API
Salesforce partners: Distribute apps to customers Data kits Managed packages* Managed packages
Environments for custom app development and testingSandbox org with Data 360 (beta). Altenatively, customer developers use a second org for development and testing. Salesforce partners use a Partner Business org.Sandbox org for customer developers. Scratch orgs or sandboxes for Salesforce partners.
Managed Package GenerationFirst-generation and second-generation managed packages with data kits.First-generation managed packages and second-generation managed packages.
API AuthenticationWhen using Data 360 API, requests are authorized via OAuth with a Salesforce access token, which is exchanged for a Data 360 access token. The requests reach the Data 360 tenant-specific endpoint. When using Connect API, the same OAuth authorization path as the Salesforce Platform APIs is used.When using Salesforce Platform APIs, requests are authorized for the org’s MyDomain endpoint via a Salesforce access token.
SOQL QueriesTo query records in Data 360, you can use a subset of SOQL. For more information about what’s supported and the limitations, see Data 360 Query Profile Parameters in the _REST API Developer Guide_.To query records in Salesforce, you can use SOQL. For more information, see SOQL and SOSL Reference.

See Also

Read this document as markdown — the same bytes an agent receives.