Architecture centre
Interactive reference architectures for Salesforce CRM, Marketing Cloud, Data 360, Braze, Agentforce, MCP and integration. Each diagram shows what every component is responsible for, how data moves, where trust boundaries sit and what happens when something fails, and says whether it is a reference design or a tested build.
Architecture centre list
Salesforce CRM Reference Architecture
How Sales Cloud, Service Cloud, Experience Cloud, the Salesforce Platform, identity and integrations fit together in one CRM estate, with failure handling and …
Read more
Data 360 Reference Architecture
How data moves through Data 360, from sources and data streams to unified profiles, insights, segments and activation, plus an integration path to Braze throug…
Read more
Customer 360 Architecture: Clouds, Data and Ownership
How Salesforce clouds, Data 360, Agentforce, analytics and an integration layer fit together, and how to decide which system owns each piece of customer data.
Read more
Marketing Cloud Engagement Reference Architecture
How Contact Builder, data extensions, Journey Builder, Automation Studio, Marketing Cloud Connect, sending, deliverability and CloudPages fit together.
Read more
Marketing Cloud Next Architecture on Salesforce and Data 360
A reference architecture for Marketing Cloud Next on the Salesforce Platform and Data 360, including consent, agents, personalisation and coexistence with Enga…
Read more
Salesforce and Braze Integration Architecture
How to connect Salesforce and Braze today with APIs and middleware: systems of record, identity, consent, channels, measurement and error handling.
Read more
Agentforce Reference Architecture
How Agentforce agents, Agent Script, the Atlas Reasoning Engine, the Einstein Trust Layer, Data 360 grounding, actions, MCP tools and human handoff fit togethe…
Read more
MCP Host, Client and Server Architecture
The MCP host, client and server roles as the specification defines them, both protocol revisions, and a reusable pattern with a policy gateway and approvals.
Read more
MCP Security and Tool Authorisation Architecture
How to secure an MCP server: OAuth 2.1, protected resource metadata, audience-bound tokens, least privilege, approvals, validation, limits, audit and prompt-in…
Read more
API-Led Integration Reference Architecture
How system, process and experience APIs fit together around Salesforce and other systems, with error handling, idempotency and monitoring, and where MuleSoft f…
Read more
Real-Time Personalisation Architecture on Salesforce
How events, Data 360, Salesforce Personalization, content and channels fit together, which paths are near real time, and how to measure lift with holdouts.
Read more
Identity and Consent Architecture for Salesforce
How to choose identifiers and match rules, keep one system of record for consent, and propagate opt-outs to Marketing Cloud and Braze with an audit trail.
Read moreTell us what you are trying to fix.
Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.
Talk to a Salesforce Expert