Do all seven layers have to be MuleSoft?

No. The gateway and the pipes do. Memory can be a graph you already run. The runtime can be Agentforce, or not. We will not force a store into Anypoint to look complete.

What if the broker flags a memory fetch as an attack?

Tighten the cards and the policy. Memory is not prompt injection. If the platform cannot tell, that is a finding, not a reason to turn the gateway off.

MuleSoft agent architecture

Seven layers. One governed path.

Slack, a browser, or a schedule can start the work. The gateway is the front door for every tool call and model call.

Get the written assessment Agent Fabric

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

Architecture

How a request should travel.

The gold layer is the gateway. It is not optional.

01
Interaction
Slack · Email · Web · Scheduled
02
Agent runtime
Agentforce · Other runtimes on the same desk
03
Orchestration
Broker · Hooks · Deterministic routers
04
Tool calls
MCP servers · Knowledge · Search · Internal APIs
05
MuleSoft gateway
Client identity · Access control · MCP mapping · Rate limits · LLM proxy · A2A lane
06
Memory
Session · Graph · Decision traces
07
Systems of record
Salesforce · ERP · Policy-gated stores

Public reference architecture for digital labor on MuleSoft. Interaction to runtime to orchestration to MCP to gateway to memory to systems of record. The gateway is the control point.

Mermaid source

flowchart TD
  L1["1 Interaction: Slack, email, web, scheduled"] --> L2["2 Agent runtime: Agentforce and other runtimes"]
  L2 --> L3["3 Orchestration: broker, hooks, routers"]
  L3 --> L4["4 Tool calls: MCP servers"]
  L4 --> L5["5 MuleSoft gateway: identity, policy, LLM proxy, A2A"]
  L5 --> L6["6 Memory: session, graph, traces"]
  L6 --> L7["7 Systems of record: Salesforce, ERP, files"]

What to demand

What must already work before you scale.

If these are missing, you do not have a fabric. You have a demo.

How far

Govern the edge first. Front stores only when proven.

Moving a graph or a warehouse behind a new owner is a one-way door. Front first.

First
Govern the edges
Ingestion, gateway and MCP hosting. Data planes stay where they run.
When calls are traced
Front the planes
Connectors govern and audit the calls. The store still lives elsewhere.
When throughput is real
Move extraction
Document jobs move behind MuleSoft once review queues are proven.

Who this is for

Two estates drawing the path.

Typical first moves. The edges first, the stores later.

Example
Platform owner, Riyadh retail group
Today: The team wants to move the product catalogue graph behind MuleSoft before a single call is traced.
After: Govern the edges first. The graph stays where it runs until traced calls show it should move.
Retail and e-commerce
Example
Head of digital, Dubai property developer
Today: Agents started from Slack reach Salesforce and the document store by different routes.
After: Every tool call and model call takes one path through the gateway, traced from Slack to the record.
Real estate

Examples of the work, not case studies. Roles and cities are typical of the desks we see.

Questions

What we actually say.

Do all seven layers have to be MuleSoft?: No. The gateway and the pipes do. Memory can be a graph you already run. The runtime can be Agentforce, or not. We will not force a store into Anypoint to look complete.
What if the broker flags a memory fetch as an attack?: Tighten the cards and the policy. Memory is not prompt injection. If the platform cannot tell, that is a finding, not a reason to turn the gateway off.

The brief · one email

Draw the path you have today.

We will mark which hops have no gateway, and which should. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.